Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Domain visibility

Log in to subscribe to topics and get notified when content changes.

Domain visibility

Domain visibility determines whether users from one domain can access records from another domain.

For example, if Don Goodliffe is in the Database domain, and Bow Ruggeri is in the Network domain, and no incidents are in the global domain, then Don Goodliffe cannot access Bow Ruggeri's incidents since data separation prevents this.

Note: While visibility is one method to allow users to access records, it is recommended that you use Contains for more robust control.
Figure 1. A sample set of domain separated incident records
Figure 2. Bow Ruggeri's incident list
Figure 3. Don Goodliffe's incident list

You can add the Database domain as a Visibility Domain to the Bow Ruggeri's user record (Visibility Domains is a related list on the user record). Then, Bow Ruggeri can access Don Goodliffe's incidents since he now has visibility to the Database domain. If you remove the visibility domain, then Bow Ruggeri can no longer access incidents in the Database domain.

Figure 4. Bow Ruggeri's incident list with visibility domain
Note: Granting users a visibility domain grants them all the rights they would normally have to the record based on ACL rule permissions.

Users can also inherit visibility domains based on their group membership if you set the domain table to the Group [sys_user_group] table. For example, as a member of the Database group, Don Goodliffe also automatically gains the Database domain as a visibility domain. Group membership grants visibility to any matching domain name.

Figure 5. Visibility domains granted by group membership