Within the configuration you can parametrize and manage common resources, workflows and other data entities that are made available to one or multiple teams using Organization Unit hierarchies.

(lightbulb) The configuration is visible to team(service) owners and administrators. UI handling is identical in both cases, although access to individual (sub)items may be limited by Roles and Permissions.

"Configuration" access in Admin and Portal

(question) Are you missing KB chapters in Administration? Note that the "Configuration" view can be accessed both via Nimbus admin (backend) and portal (frontend) UI - depending on your user role.

(lightbulb) You can also learn more about this concept by reading the chapter "Administrative concepts" below.

Tenant and Partner AdministratorsService Administrators (Team Owners)Users

The following configuration topics are exclusive to the backend :

Access to configurable elements is the same for front- and backend.

(info) Refer to the Configuration pages located in the Usage of Nimbus area.

Have no access to configuration in either back or frontend.

Administrative concepts

To understand Nimbus administration you need to know that users accessing the configuration of Nimbus manage data entities according to the concept diagram below.

(lightbulb) Examples of such Nimbus data entities are: Workflows, Context, Opening hours, but also users and services themselves as they have their own configuration properties.

Data entity access

Access to data is granted by assigning a Role and Organization Unit to each user.

  • Permissions  (Create, Read, Update, Delete) are tied to a role as determined by the Roles and Permissions model.
  • Visibility is steered via the Organization Unit (OU), which must be assigned to each entity in a 1:1 manner.
  • Usage of the configuration entities depends on their their Organization Unit. Entities can access any other entity as long as it is within their OU or higher along the path (up to the Tenant root).
    (lightbulb) An example of this could be a workflow accessing playlists within the same service OU or on tenant level.

(info) Note: Licensing may restrict usage and visibility of certain features and configuration items.