Ontology permissions

Ontology resources are managed as project resources and permissions are handled through Compass, the Palantir platform’s filesystem.

This project-based permissioning approach unifies control and provides the following benefits:

• Bulk management: Manage permissions efficiently at the folder and project level, reducing the need to permission individual resources.
• Clearer visibility: The updated Security tab and sidebar display permissions and project context for all resources, including ontologies.

Viewing object type definitions and instances

Object type definitions are permissioned differently from instances of object data. To see an object type definition, you must have View permissions on the object type definition, but do not need View permissions for the backing datasource.

To see object data instances, you must hold View permissions on both the object type definition and the backing datasource.

For more information on the distinction between definitions (metadata) and instances (data), review the documentation on object permissioning.

Edit permissions for links and actions

You will need the appropriate edit permissions depending on the resource you would like to edit:

• For links: You must hold edit permissions on both the link type and the linking object types.
• For actions: You must hold edit permissions on the action type and on all ontology resource types edited by the action.

Previous permissioning models

Previously, permissioning ontology resources varied based on your ontology authorization model. The table below summarizes how resources are currently managed for each model.