About Relationship Family Data Permissions

Relationship family permissions are similar to entity family permissions in that the same permission levels are available: View, Update, Insert, and Delete. Each permission level, however, provides access that is slightly different from the access provided through entity family permissions.

Remember that relationship families are used to create links between records in entity families. Consider an example where the Equipment family is related to the Failure family through the Has Failure relationship. In this case, to provide a user with full access to an Equipment record and its associated Failure record, that user would need permissions to three families: Equipment, Failure, and Has Failure.

Note: Permissions to a relationship family do not automatically provide access to the predecessor and successor families; for that, explicit entity family permissions are required.

The following table provides details about each relationship family data permission.

Permission	Description	Notes
View	Users have basic access to the links that relate predecessor and successor records. Users with View-only access to a relationship family can open existing linked records, but cannot link and unlink records using that relationship.	None
Update	Users can modify existing links in a relationship family.	This applies only in cases where fields are defined for the relationship family. Users with Update permissions will also need View permissions.
Insert	Users can link records together using that relationship family. Using the previous example, a user would need Insert permissions on the Has Failure family to link Equipment records to Failure records.	Users with Insert permissions will also need View permissions.
Delete	Users can unlink records associated with the relationship family. Using the previous example, a user would need Delete permissions on the Has Failure family to unlink Failure records from Equipment records	Users with Delete permissions will also need View permissions.