Configure permissions for a collection
Collection permissions determine users and groups permissions for the documents in a collection.
There are three types of collection permissions, as shown in the following table:
Permissions | Available Tasks |
---|---|
Read only |
|
Write only (read is implicit) | All of the above, plus:
|
User administration |
|
- Users and groups that were assigned Document Base Administrator and Server Administrator permissions have read, write, and user administration permissions at the repository and collection levels.
- Users and groups that were assigned Document Base User and Server User permissions have read and write permissions at the repository and collection levels.
You can customize these permissions using the procedure below.
When you assign permissions at the repository and collection levels, these permissions become restrictive, meaning that all other inherited permissions assigned for this repository or collection are automatically removed.
For example, consider that DocBase A has a Repository with three collections: Collection A, Collection B, and Collection C. Collections A and B contain user documents and Collection C contains system documents that can only be modified by a specific user (User1). Group A, which contains three users (User1, User2, User3), has Document Base User permissions on DocBase A, which means that, by default, every user in this group has read and write access to the repository and collections of DocBase A.
To restrict access to Collection C to User1 only, you assign read and write permissions to User1 at the Collection level. Since collection permissions are restrictive, User2 and User 3 no longer have Read and Write access to Collection C.
To configure collection permissions for a group or a user: