Understanding Cadenza Feature Availability

Several factors determine whether functionality is available to the current user in a given Cadenza instance. This page explains these mechanisms so you can understand why something may not appear and how to configure Cadenza accordingly.

Cadenza Features and Licenses

Some Cadenza functionality is bundled in features whose availability depends on your specific edition type and its configuration. In Cadenza Editions and Features we document all available features and which edition includes them.

Availability of a Cadenza feature depends on whether it …

  • is enabled by the current Cadenza edition.

  • is not explicitly deactivated via the core Configuration configuration.

  • has no mandatory configuration, or Cadenza is configured appropriately.

Roles and Privileges

Cadenza has an extensive system of rights and access control where a user inherits certain roles and privileges based on what groups they belong to and other configuration options. Depending on these roles and privileges, the user may or may not have access to certain functionality.

We document more about system privileges and where they are required in System Roles and Privileges.

Application Design

Some functionality may be shown or hidden depending on whether it is appropriate in the current UI context. For example, a workbook preview does not allow saving the workbook even if it looks like a normal workbook. Another example is the access settings of a workbook: they can only be changed if the workbook is saved.

Embedding

Cadenza can be embedded in other applications using our Embedding API. In these cases the application developer can decide to hide certain kinds of functionality using the disabledUiFeatures option of our API.