Skip to end of metadata
Go to start of metadata

My 2 use cases are below and I am having a hard time getting this to work properly.

1) Open model

  • Non members can view - these users will be in our confluence global user group
  • All members can view/edit - user group created dynamically as members are approved by admins
  • Space admin can view, edit, delete, export - user group created manually

2) More restricted

  • Non members can see community listed in dashboard but need to join to view - these users will be in our confluence global user group
  • Members can view only - user group created dynamically as members are approved by admins
  • Space admin can view, edit, delete, export - user group created manually

I am having trouble with non members not being able to see the More Restricted groups in their dashboard as well as trouble setting up the dynmiac user groups with the prefix. I've scoured the documentation and am probably overanalyzing, so I am hoping there is a simple way to solve this.

Thanks!

  • No labels

3 Comments

  1. Users can either view the space or they cant ... for them to be able to see the community in the dashboard they need to be able to view the space, however to prevent them from viewing the content of the space they should not have view permission.

    One solution might be for you to create a 'directory' space that everyone can view, which details all of the available communities and provides a join link to each community.

    The community itself would then be setup as an 'open' community with view rights to %community%, edit and admin rights should be left blank since space-admin rights should give these permissions anyway.

    You shouldn't need to setup the dynamic groups, these should be handled automatically and are referenced with the %communiity% macroscopic group name.

  2. Unknown User (skrebs)

    If you manage to get this working, and have any ideas on how or where the documentation could be improved please let us know.

    1. Unknown User (sfwinter)

      looks like I found the source of my problem.

      This only seems to work if I create a space first, then convert it to a community after it has been created. If I create a community directly from the dashboard link it doesnt work. Odd.