Skip to end of metadata
Go to start of metadata


I would like display content in a community, but the content would differ depending of the permission scheme of the community. For instance, not displaying information about community membership, and ability to join the community (ie the community is fully open, no need to be member to contribute/see content... acting like a common space for a fully open community actually).
Is it possible with any of the bubbles macro ?
If not, I was thinking of a parameter in the bubbles-show/hide macro based on the name of the permission scheme applied on the community. What do you think ?



  • No labels


  1. Unknown User (gfraser)

    I think this feature is already on our internal task list and will hopefully make it in to 1.6 or 1.7.

  2. Unknown User (skrebs)

    The milestone builds of the 1.6 release have a new param for the bubbles-show/hide macros: communityEnrolment

    Doco is here: 1.6 context check macro params

    This might do what your after. The permission scheme used when the community is created doesn't really apply after that, its only a template used for the initial setup.

    1. Unknown User (scayla)

      Thank you both for your answer.
      Apologies for not digging in the milestone release, I forgot about it when I wrote my question, just did a brief (really brief though) search before.
      Anyway, I guess the communityEnrolment parameter won't make it. With the same community type, I can have plenty of permission schemes defined with the Open enrolment type. This would make me create different types of communities to achieve my goal and then being able to use the communityEnrolment parameter.
      Correct me if I'm wrong.
      Shannon, you mean the permission scheme used is not saved anywhere after the creation is complete and then cannot be reused anywhere ?
      Having the ability to use the name of the permission scheme would have really helped me to target specific communities with specific permission scheme

      1. Unknown User (skrebs)

        You are correct, unfortunately. The permission scheme isn't saved after the community is created, its only used in the creation process to setup the initial values for the space permissions. A space admin can change the permissions around once a community is created any-ways, so the permissions may not match the original permission scheme.

        (Being able to sync the permissions scheme template and space permissions, would be a great feature, i.e. live templates, lot of work involved in that though.)

        1. Unknown User (scayla)

          Too bad for me then !
          Even with the ability to modify the space permission (such as comment for anonymous users as a simple example ^^), the initial permission scheme applied could be/would have been a great thing I think.

          Anyway, I'll try to find an other way which I'm really not sure of any chances of success.


          1. would the {builder-show:permission=...} parameter work for you ... it wont show you the permission scheme, but will show you the current state of the permissions on the page/space.

            1. Unknown User (scayla)

              Hehe, that's what I was thinking about (wink) (know more about Builder than Bubbles)
              I guess it will do the trick. I'll give a try tomorrow after sleep.
              Thanks for being involved Alain.

              1. heh ... I originally wrote bubbles too (wink)

                Poor Shannon had to take over with a mostly crufty codebase when it became aparent that I couldn't realistically develop both!

  3. Unknown User (scayla)

    I'll make it a different way eventually :

    • create as many community types as the number of permission schemes I have.
    • make them exactly the same way, with same portal, same layout, same everything
    • allow only one permission scheme for each community type
    • be able to target communities by the communityType
    • done (big grin)

    While creating a community, instead of not having the choice of the community type and then choosing the permission scheme between all the schemes, my users will do it the opposite way : choice between all the communities, one permission scheme.

    Much easier !

  4. Unknown User (gfraser)

    If you're using Theme Builder you can use builder-show macro and builder-hide macro to show/hide stuff based on user permissions.

    1. Unknown User (scayla)

      I was totally sure the communityType parameter was in the bubbles-show/hide macro in Bubbles 1.5 ... (sad) ... so bad so bad ! Misread, mixed the 1.6 and 1.5 docs in my head. My previous comment won't work until 1.6 :/
      I'm stuck then.
      Gonna have to make it with builder-show and builder-hide then, based on permissions, no choice.

      1. Unknown User (scayla)

        Hum sorry about all these useless comments finally. I forgot my brain at home I guess today.
        I'll create differents portals, some with information, some without.
        THIS is doable !