About Entity Family Data Permissions

For each entity family, you can grant users View, Update, Insert, and Delete permissions. The following table provides details about each permission.

Permission	Description	Notes
View	Users can view records that belong to the family. Users with only View permissions on a family will be able to open existing records belonging to that family but would not be able to create, modify, or delete them.	For typical users, View permissions are a prerequisite to Update, Insert, and Delete permissions because they provide users with the initial access required for modify, create, and delete operations. For example, users with View permissions on a family can: Search for records in that family and open them in the Record Manager. Create a Select query on that family. Open reports that include that family.
Update	Users can modify records that belong to the family. Users with only Update permissions on a family would be able to modify existing records belonging to that family but would not be able to view, delete, or create records in that family.	Typically, you would not grant Update-only permissions to a user because, while that user would be able to modify records in that family, without View permissions, they would not be able to search for them or open them. Update-only permissions, however, may be used to support processes and operations that occur outside of the user interface (i.e., interfaces or scheduled jobs).
Insert	Users can create records in the family. Users with only Insert permissions on a family would be able to create records in that family, but would not be able to view, modify, or delete them.	Typically, you would not grant Insert-only permissions to a user because, while that user would be able to create records in that family, without View permissions, they would not be able to initiate the record-creation process in GE Digital APM. Insert-only permissions, however, may be used to support processes and operations that occur outside of the user interface (i.e., interfaces or scheduled jobs).
Delete	Users can delete records that belong to the family. Users with only Delete permissions on a family would be able to delete records belonging to a family, but would not be able to view, modify or create them.	Typically, you would not grant Delete-only permissions to a user because, while that user would be able to delete records in that family, without View permissions, they would not be able to perform a search to find the records that they wanted to delete. Delete-only permissions, however, may be used to support processes and operations that occur outside of the user interface (i.e., interfaces or scheduled jobs).