The PROJECTS tab contains all object-level records that belong to the project's context, with a permission set configuration assigned to each one.
It displays only objects that belong to the context of a Project, which may include documents, contacts, related records and other dependent objects.
access the projects tab
To access the PROJECTS tab:
1. Open the Control Center workspace.
2. Click Access.
3. Select Permission Sets.
4.In the Name column, select a Permission Set.
The Permission Set Editor will open.
5. Click the PROJECTS tab.
projects tab dashboard
The PROJECTS tab dashboard contains the following components:
| 1. PROJECTS tab 2. Objects column 3. View column 4. Edit column | 5. Delete column 6. Create column 7. Conditionals column |
objects column
The Objects column lists all object-level entities governed by the Permission Set. This column is informational and displays the scope of records where permissions will be applied.
view column
The View column controls record visibility within the object.
| View Level | Access Scope | Visibility Definition | Governance Impact |
| Any | Global | Users can view all records. | Enables full downstream permission flexibility. |
| Related | Contextual | Users can view related records only. | Restricts Edit/Delete to related or lower scope. |
| Own | Individual | Users can view records they own. | Limits downstream permissions to owned records. |
| None | Restricted | Users cannot view records. | Blocks all additional permissions. |
edit column
The Edit column defines the ability to modify object records.
| Edit Level | Access Scope | Modification Definition | Governance Dependency |
| Any | Global | Users can edit all records. | Allowed only if View = Any. |
| Related | Contextual | Users can edit related records only. | Cannot exceed View scope. |
| Own | Individual | Users can edit records they own. | Restricted by View level. |
| None | Restricted | Users cannot edit records. | Applies regardless of View. |
delete column
The Delete column governs the ability to remove records from the object.
| Delete Level | Access Scope | Deletion Definition | Governance Dependency |
| Any | Global | Users can delete any record. | Allowed only if View and Edit = Any. |
| Related | Contextual | Users can delete related records only. | Cannot exceed View/Edit scope. |
| Own | Individual | Users can delete records they own. | Restricted by View/Edit level. |
| None | Restricted | Users cannot delete records. | Applies regardless of other permissions. |
create column
The Create column grants the ability to generate new records within the object. This permission is enabled via checkbox selection. When checked, users can create new records aligned with their configured access scope and object visibility permissions.
conditionals column
The Conditionals column allows administrators to apply exception-based permissions on top of the base object configuration. Instead of modifying global access, conditionals create governance overlays that adjust permissions only when specific criteria are met.
For example, a permission set may grant users standard access to all objects. Using conditionals, administrators can add an exception such as restricting access completely for that specific project type like Mass Tort. In this scenario, users retain their general permissions across all other records, while access to the restricted classification remains limited.
This enables firms to control sensitive operational data without restructuring the entire permission framework.