There are 3 types of security you can apply to a user field to control access.
Security Type | Description | |
---|---|---|
Who Can View | User can view the user field on the form, but the field is read only. | |
Edit | User can enter information in the user field. | |
Admin | User canthis Field | Choose who you want to be able to view the field. |
Who Can Populate or Edit this Field | Choose who can edit this field. | |
Editable Status(es) | Choose which status(es) the field is editable in. | |
Who Can Add or Edit Values When Populating this Field (Field Administrator) | This will allow user(s) to add and remove options in the field from within the form (Only applies to Select, Cascading, Radio and Check Box fields). |
...
1. Select the User field.
2. Click the Security Tab.
3. Using the Contact picker add users, companies or roles in the relevant security type.
4. Click Update.
Note |
---|
Who can edit the field overrides who can view it. Therefore if who can edit is locked down to RIB-AM then only RIB-AM will be able to view it. Regardless of the fact the you have ALL in the View Security. |
Use the keyword AUTHOR in security
We added support for using AUTHOR as a keyword in security in these areas.
See/Edit/Administer a user field
Status Allocation
Status Action button visibility
May edit title/May edit due date
Closers and Status Changers
Status Approvers (For Approval)
May reopen a closed document
Split
Handover report
You may also use -[Author] as a security setting for exclusions. i.e. everyone but the Author can do the edit.
Note |
---|
For security checking, RIB CX will process rules in an order of most specific to least specific, and minus with a higher priority than plus rules. Meaning you could configure a scenario such as +RIB-*, -RIB-JD, which would mean everyone in RIB except John Doe. This means regardless of the order a user enters in the UI, RIB CX will process security in the following order:
|