Object Authorizations per Status

Use

To enable you to control exactly who works on an object in different phases of a project, it is possible to create authorizations that depend on the status of an object.

Features

Set object authorization for a status

In a status profile , you can assign object authorizations to each status by choosing Object Authorizations in the status detail screen. You can assign a user, user group, or role to the status and also define what sort of activities they can carry out, for example, read, write, delete, and so on. When a cFolders object using this particular status profile achieves a particular status, only those users, user groups, and roles assigned to the status in the status profile can work on the object. Object authorizations inherited from a status profile override all other authorizations for an object.

To ensure that the status transitions can be carried out, you must do one of the following:
- Assign write authorization for the object to at least one user in each status.
- Specifically assign authorization to carry out the status transition to a user. The user must have at least read authorization for the object.
  
  For more information, see Transition Authorization .
Set field group authorization for a status

If a generic object or object category has field groups, you can also assign authorizations for a field group for a status . You also do this by choosing Object Authorizations in the status detail screen and then the field group.
Set write protection for an object for a status

You can set write protection an object when it has a particular status by selecting the Protected indicator in the status detail screen. This restricts an object with that status to read only. For more information, see Protection .
Set write protections for a field group for a status

You can set write protection for a field group of a generic object or object category when it has a particular status.

Note Note

If, for example, user Steve Gates has administration authorization for a collaboration in which document A is located, he would normally have administration authorization for all objects in the collaboration including document A. However, if document A has a status profile with object authorizations and Gates has not been assigned authorization in any of the statuses, he will not be able to work on the document at all, that is, he will not even have read authorization for the document.

This graphic is explained in the accompanying text.

Note that the object authorizations are optional. If you do not create object authorizations in a status profile, then the normal authorizations are valid for an object with this status profile, for example, authorizations inherited by the object or specifically assigned to it. As soon as you create object authorizations in a status profile, however, they are valid for any object using this status profile and override all other authorizations.

Also note that as soon as you assign a status profile with object authorizations to an object, the authorizations for the object defined by the status are inherited by all objects below that object until the system finds an object with another status profile with status authorizations.

End of the note.