Skip to main content
This page is based on code-level analysis. Verify permission behavior in your Polarion environment, as server-side enforcement may vary by version.

​
Step 1: Open the Domain Model

  1. Navigate to Administration > Nextedy POWERSHEET > Domain Models
  2. Select the domain model to edit
  3. Locate the entity type under domainModelTypes where you want to configure permissions

​
Step 2: Set Property-Level Permissions

Each property in an entity type can have readable and updatable flags to control visibility and editability: 
domainModelTypes:
  UserNeed:
    polarionType: userNeed
    properties:
      id:
        readable: true
        updatable: false
      title:
        readable: true
        updatable: true
      description:
        readable: true
        updatable: true
      severity:
        readable: true
        updatable: false
      outlineNumber:
        readable: true
        updatable: false

​
Permission Flag Reference

FlagDefaultEffect when false
readabletrueProperty is hidden from the sheet UI
updatabletrueProperty is displayed as read-only
diagram

​
Step 3: Configure System-Level Read-Only Properties

Certain properties are always read-only regardless of your domain model settings:
  • id — the work item identifier
  • outlineNumber — the document hierarchy position
For Document entity types, properties like moduleFolder, moduleName, title, and type are also read-only after creation.
Setting updatable: true on id or outlineNumber has no effect — these fields are always enforced as read-only by the server.

​
Step 4: Set User-Level Permissions

Powersheet also enforces user-level permissions for document and model administration. These are determined by the user’s Polarion roles:
  • document.admin.read — can view sheet configuration
  • document.admin.write — can modify sheet configuration
  • model.admin.read — can view domain model configuration
  • model.admin.write — can modify domain model configuration
A top-level readOnly flag is also evaluated, which makes the entire powersheet read-only when the user lacks write permissions or the license is invalid.
Combine domain model permissions with column-level read-only settings for fine-grained control. Domain model permissions apply globally, while formatters can be conditional.

​
Step 5: Apply Permissions to Navigation Properties

Permissions can also be set on relationship navigation properties via the direct and back definitions: 
relationships:
  - from: UserNeed
    to: SystemRequirement
    cardinality: one-to-many
    storage: linkedWorkItems
    linkRole: refines
    direct:
      name: systemRequirements
    back:
      name: userNeeds
Navigation property permissions are inherited from the target entity type’s permission settings. If the target entity has updatable: false, the relationship column will also be read-only.

​
Verify

After saving your domain model changes, open a powersheet document. You should now see:
  • Properties with readable: false are not displayed as columns
  • Properties with updatable: false are displayed but cannot be edited (cells appear greyed out)
  • System fields (id, outlineNumber) remain read-only regardless of settings

​
See Also

permissions.yaml, DataPropertyFactory.java, UserPermissions.d.ts, DomainModelTypeV2.java
KB ArticlesSource Code
  • prod-powersheet-src/com.nextedy.powersheet.client/cypress/fixtures/models/permissions.yaml
  • DataPropertyFactory.java
  • MetadataTest.java
  • prod-powersheet-src/com.nextedy.powersheet.client/src/modules/ConfigProvider/types/UserPermissions.d.ts
  • prod-powersheet-src/com.nextedy.powersheet.client/src/modules/ConfigProvider/ConfigProvider.tsx