Set Entity Permissions - Nextedy Documentation

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

Open the Data Model

Navigate to Administration > Nextedy Powersheet > Data Models
Select the data model to edit
Locate the entity type under domainModelTypes where you want to configure permissions

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

Flag	Default	Effect when `false`
`readable`	`true`	Property is hidden from the sheet UI
`updatable`	`true`	Property is displayed as read-only

Configure System-Level Read-Only Properties

Some properties are enforced as read-only regardless of your data model settings:

id — the work item identifier. This is a built-in property and is always read-only.

Other properties become read-only only when explicitly declared in the entity type:

outlineNumber — the document hierarchy position. Unlike id, outlineNumber is not a built-in property. It must be declared under properties for the entity type before it appears on the sheet, and it is treated as read-only when declared (the server controls outline numbers automatically).

For Document entity types, properties like moduleFolder, moduleName, title, and type are also read-only after creation.

Setting updatable: true on id has no effect — it is always enforced as read-only by the server. The same applies to outlineNumber once you declare it: the server ignores updatable: true and keeps the value under its control.

Set User-Level Permissions

Nextedy 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 data model configuration
model.admin.write — can modify data 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 data model permissions with column-level read-only settings for fine-grained control. Data model permissions apply globally, while formatters can be conditional.

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 data 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)
id remains read-only regardless of settings; outlineNumber, when declared, is also enforced as read-only by the server

​Permission Flag Reference

​Verify

​See Also

Permission Flag Reference

Verify

See Also