Because of the extreme flexibility of OA, understanding of the permission system and the configuration can get very complex.
Speaking for myself, it can take days to figure out all the possibilities in OA just for this matter.

A lot of questions are asked in the issue list on this and my conclusion is that o lot of people are facing the same problems and difficulties.
It would be great if there were use cases available on the documentation pages that will answer most permission questions.

I have created a first use case as a child page of the Open Atrium Permissions page in the handbook.
Use case: Public space, section write permission via group membership
Please have a look at this page and comment on the styling and content so we will come up with a nice default Use case layout on which we can further base other use cases.

Cheers,
Joep

Comments

Anonymous’s picture

joep.hendrix created an issue. See original summary.

mpotter’s picture

As with Drupal, the complexity comes with the flexibility as you said. That means there are sometimes multiple ways to accomplish a task.

While your initial use-case is good, it's also not quite the "best practices" recommended for Groups. Groups themselves have permissions. In your use-case, the recommended approach is:

1) Create a Group with Create X content permissions
2) Assign users to the group
3) Assign the Group to the space, but set the group to the default "Inherit Permissions"

In other words, using "Child permissions" basically prevents any of the Group permissions from working, and those Group permissions are there for a reason. Often, Groups themselves come from an external user identity management system (such as LDAP, Active Directory, etc) and the permissions are part of the Group and not part of the Space.

For example, you have a group called "Contributors" which have Create X Content permissions that you can then assign to any set of spaces on the site that they are allowed to contribute to. Another example is a group called "Managers" that have admin-like permissions that you can assign to other spaces.

Your use-case is only for the specific case where you want the users assigned to a Group but you want to use the Space membership permissions rather than the Group, so maybe the handbook page title needs to be tweaked.

Anonymous’s picture

Thanks Mike for your reply and your thoughts.

I am aware of the fact that the permissions can be set via Group permissions and than the inherit mechanism. There are definitely situations where that route would make perfect sense. If you want to organise the users by what the are allowed to do, I understand that.
The problem with the approach above is that when you have multiple spaces and multiple groups with per space individual write permission requirements, you will end up with a huge list of groups.

A lot of businesses group their users in organisational groups. For example Financial Department employees rather then content editors. A lot of LDAP's (ie Active Directory) are organised that way.
Suppose there is a public Financial Department space where only the members are allowed to post content. All Financial Department employees would have to be added one by one to make them a member of the Financial Department space. Or, by by assigning the FD Employees group to the space.
In this example the grouping functionality of OA is just used to group users, nothing more, nothing less.

Personally, I think the second example is more in line of what site administrators expect what the grouping is all about when they start with OA: A mechanism to group users in order to keep space membership maintainable.
If the permissions are set on group level there is no easy way to see which users can do what on space level. You will need to dig into each group to see what the permissions are of the group.

Another option to set custom space permissions is through a special space role. Although the current OA user interface lacks the support to easily ad a user to a custom space role.

mpotter’s picture

Sure, I understand your use case.

My comment was to improve the page title or make it more specific and indicate that it's just one way to accomplish this (as a review of your page). And if possible mention the other method since different people will need the different method.

Anonymous’s picture

No problem. If you have any suggestions for a better page title, please let me know.

Argus’s picture

Title: Community effort: describe use cases for several permission needs » [Documentation] Community effort: describe use cases for several permission needs