Content can be secured by assigning a role to a specific user (or group) on that content.
Alfresco uses roles to determine what a user can and cannot do with the content. These roles are associated with permissions. The table below shows each role and the permissions on the content for that particular role:
Permissions |
Consumer |
Contributor |
Editor |
Collaborator |
Coordinator |
---|---|---|---|---|---|
Read Content |
X |
X |
X |
X |
X |
Read Content Properties |
X |
X |
X |
X |
X |
Copy |
X |
X |
X |
X |
X |
Preview in Template |
X |
X |
X |
X |
X |
Start Discussion |
— |
X |
— |
X |
X |
Edit Content |
— |
— |
X |
X |
X |
Edit Properties |
— |
— |
X |
X |
X |
Apply Versioning |
— |
— |
X |
X |
X |
Apply Categorization |
— |
— |
X |
X |
X |
Checkout |
— |
— |
X |
X |
X |
Update |
— |
— |
X |
X |
X |
Take ownership |
— |
— |
— |
— |
X |
Cut |
— |
— |
— |
— |
X |
Delete |
— |
— |
— |
— |
X |
Typically, security and access control rules are defined at the space level. It is not advisable to secure individual content items, as this may become unmanageable with a large number of files. It is best to secure the parent space, rather than securing the content itself. However, you can still control the access to a specific content item.
Follow the steps given next to invite users to your content item:
Now the user can collaborate on the file.