The SYSTEM tab contains non-contextual system objects that govern platform-level capabilities across Neostella. Permissions configured here control how users interact with global tools within the Cases workspace and platform governance environments.
access the system tab
To access the SYSTEM tab, follow these steps:
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 SYSTEM tab.
system tab dashboard
The SYSTEM tab dashboard provides the operational workspace where platform-level permissions are configured.
| 1. SYSTEM tab 2. Description column 3. Permission column |
description column
The Description column lists all system objects and their governed features. It serves as the structural reference that defines which platform capabilities can be controlled through the permission set.
permission column
The Permission column displays the configurable access levels available for each system object. Administrators assign action rights or visibility scopes here, depending on the governed capability.
system permissions matrix
The SYSTEM tab includes multiple platform-level objects (such as governance tools, account settings, reporting components, and administrative structures).
Rather than listing every system object individually, the matrix follows consistent permission patterns depending on the object type. Here some examples:
- standard administrative objects (example)
Objects such as governance and organizational components typically use a binary permission model:
| Permission | Type | Description | Reflected In |
| Create | Yes / No | Create new records | Administrative structure |
| View | Yes / No | View existing records | Listing or management panels |
| Edit | Yes / No | Modify records | Configuration screens |
| Delete | Yes / No | Remove records | Management workflows |
This structure applies consistently across administrative objects within the SYSTEM tab.
- reporting components (example)
Reporting-related objects use a scoped permission model to support granular access control:
| Permission | Type | Description |
| View | Any / Own & Shared / Own / None | Controls visibility scope |
| Edit | Any / Own & Shared / Own / None | Controls modification rights |
| Delete | Any / Own & Shared / Own / None | Controls removal rights |
These objects allow contextual scope (Any, Own, Shared) rather than simple Yes/No authorization.