Permission Levels
User Permissions
Powersheet fetches user permissions from the server API to determine access capabilities. Permissions are structured as follows:| Name | Type | Default | Description |
|---|---|---|---|
document.admin.read | boolean | See application | Permission to view the sheet configuration YAML. |
document.admin.write | boolean | See application | Permission to modify the sheet configuration YAML. |
model.admin.read | boolean | See application | Permission to view the domain model configuration YAML. |
model.admin.write | boolean | See application | Permission to modify the domain model configuration YAML. |
readOnly | boolean | false | Top-level flag indicating if the entire sheet should be read-only for the current user. |
license.status | string | See application | License validation status: OK, INFO, WARNING, or INVALID. |
license.message | string | None | Human-readable message explaining the license status. |
License Status Values
| Status | Description |
|---|---|
OK | Valid license with full functionality. |
INFO | Informational message about the license. |
WARNING | License issue detected; limited functionality may apply. |
INVALID | No valid license; restricted access. |
Property-Level Permissions
Individual properties on entity types can be configured withreadable and updatable flags to control field-level access:
| Name | Type | Default | Description |
|---|---|---|---|
readable | boolean | true | Controls whether the property is visible to users. When false, the property is hidden in the UI. |
updatable | boolean | true | Controls whether the property can be modified by users. When false, the property is read-only. |
Configuring Property Permissions
internalScoreis completely hidden from usersapprovalStatusis visible but cannot be edited
System Read-Only Properties
Certain built-in properties are always read-only regardless of configuration:| Property | Entity | Behavior |
|---|---|---|
id | All work items | Always read-only. |
outlineNumber | All work items | Automatically managed by Polarion. Always read-only. |
objectId | All entities | Universal primary key. Always read-only. |
moduleFolder | Document | Create-only (set during creation, read-only thereafter). |
moduleName | Document | Create-only. |
title | Document | Create-only. |
type | Document | Create-only. |
allowedWITypes | Document | Create-only. |
The complete list of create-only Document fields may vary by version. Verify the current behavior in your Powersheet installation.
Relationship Permissions
Relationships between entity types can have their own permission controls, independent of the entity type permissions:| Name | Type | Default | Description |
|---|---|---|---|
createable | boolean | See application | Controls whether new relationship instances can be created by users. |
readable | boolean | See application | Controls whether relationship instances are visible in queries. |
Permission Inheritance
Relationship navigation properties inherit permissions through a hierarchy:- Navigation property permissions — Explicit
readable/updatableon the navigation direction - Entity-level permissions — Permissions defined on the parent entity type
- Server-rendered override — Properties using server rendering are automatically set as non-editable
direct and back) can optionally carry its own constraint configuration that further restricts access.
Complete YAML Example
Related pages: Properties | Domain Model Types | Constraints | Relationships
Sources
Sources
Source Code
prod-powersheet-src/com.nextedy.powersheet.client/src/modules/ConfigProvider/ConfigProvider.tsxprod-powersheet-src/com.nextedy.powersheet.client/src/modules/ConfigProvider/types/UserPermissions.d.tsprod-powersheet-src/com.nextedy.powersheet.client/cypress/fixtures/models/permissions.yamlprod-powersheet-src/com.nextedy.powersheet.client/src/modules/Powersheet/Powersheet.tsxRelationship.java