Alfresco Share groups and users

[mike54]

Hi,

I want to add a group to my site. This group contains users A, B, C.
This group has a Consumer (read only) role for this site.

Then I want to add user A as Collaborator, but the Add button is grayed out (Because this user belongs to a group that is associated with this site?)

It is possible in Alfresco Explorer - why it is not allowed in Share?

Thanks,
Mike

[mike54]

One more thing regarding permissions.

I have a group, lets say GROUP1 that has Collaborator role for Share Site.
I want to create one folder that is read only for GROUP1.

So I have selected Edit Permissions on that folder and set Consumer role for all groups (Consumers, Collaborators etc)

Now when I navigate to that folder as one of GROUP1 users, this user cannot create new folders or upload content - that works as expected.
But this user CAN upload or edit documents inside!
When I review document permissions - they inherited "consumer" role.
Why a consumer is able to upload new Version?

Another thing is that Consumers are not able to create comments for a document. I ant the document to be protected, not the ability to comment it…
That's my view at least…

thanks,
Mike

[mike54]

I haven't found the answer yet… to summarize / simplify, my two basic questions are:
1 . Why Consumer role allows for uploading new version of a document?
2. Why I cant add user to Site,  when this user belongs to a group that is already assigned to this Site (this is possible in Explorer)

Thanks,
Mike

[zoao]

Hi Mike,

   1. I think this can happen because the Share applied the rule of Consumer only to the folder and not for children (documents and sub-folders), you should be able to verify this through the Explorer.

   2. This is a behavior that has already been reported for some time, but that has not been fixed.

By the way another behavior of the Share is that when you add a group to a site, users of this group do not appear in members Dashlet.

[mike54]

1. I think this can happen because the Share applied the rule of Consumer only to the folder and not for children (documents and sub-folders), you should be able to verify this through the Explorer.

Well, I don't think so…

Share:
Space Permissions: all roles have Consumer privileges.
Document contained inside: all roles have Consumer privileges.

Explorer:
Space Permissions: Contains roles with Consumer privileges.
Document itself has "Inherit Parent Space Permissions"

After that all editing options are removed (for example - there is no delete option), but Upload New Version remains!
For me this is not a "consumer" operation.

[mike54]

I have found one more thing that confirms for me that there is something wrong with the interface.

When I remove all privileges for a document, and there is only "Everyone - Consumer" permission - the Upload New version button is visible for a normal user.
When the user actually tries to upload a document, he gets a Failure notification…

Thats ok in terms of security, but confusing…

(sorry for creating so many posts!)

Mike

[shiftycow]

I've also been frustrated by this behavior and would like to note that it applies to subgroups as well (cannot add a subgroup of a group that has already been added). The workaround is simple - just add individual users, then subgroups, then groups - but this is a silly thing to have to do when the functionality exists elsewhere in the interface…

Community gurus - where would be a good place to file a bug-report/feature request about this?

[natguyton]

Using Community Edition 3.2 and the Admin Console within share, I have been able to create a group "A" that has collaborator privs, and within that group I have a group "Aadmin" that has manager privs on several sites.   I am able to add users to both groups, or to just one or the other.   Perhaps the admin group being a subgroup of the collaborator group makes it work differently?

[ebogaard]

Sorry for opening up an old post, but I experience the same problems.
Opened a enhancement request on Jira, but noone has voted for this already, so it isn't handled. Mayby someone can vote to fix this?
https://issues.alfresco.com/jira/browse/ALF-5202