Document permissions

[tman247]

Another quick question from a new user. Say we have a site, and a bunch of users who are collaborators in the site. My assumption is that everyone with the same permissions within the site should be able to create/modify/upload all documents within the site, but this doesn't seem to be the case. One collaborator uploads a document, and they have the full list of Document Actions available. If another collaborator browses the document, their actions are limited to; Download, view, copy, start workflow and publish (this is 4.2.d by the way).

I've looked at the permissions, and they appear correct. Does this require a further mod to the config files?

[abarisone]

Hi,
always remember to take into account the concept of ownership about content.
The collaborator that uploaded the content is also its owner and as a consequence it has full control over it.
That's why the other collaborator has only a subset of available actions.

Regards,
Andrea

[mitpatoliya]

Also if he is part of two different groups then behavior can be different we need to keep track of that thing as well.

[tman247]

Thanks. I completely understand the concept of 'ownership', so yes that makes sense, but it you have multiple collaborator's working in a site, and they all need to be able to update a specific document, does this need to be done by the owner (and how do they do this?), or can it be done by the administrator? I can't see any options in the document library to modify the permissions of a file. The 'Manage Permissions' option is not granular enough, and I'd assume that anyone with collaborator rights to the site, should have collaborator rights to documents within the site.

Also, one useful feature would be able to setup permissions at the folder level so any documents within that folder can be edited by anyone within the site who has the correct permissions.

[abarisone]

Hi,
you can always build a group of users which has Administrator permission on that folder.
And if a 'standard' role doesn't completely fit your requirements, you can always create a custom one modifying permissionDefiniitions.xml

Regards,
Andrea