For the complete documentation index, see llms.txt. This page is also available as Markdown.

project roles

When a user is assigned to a project, they must also be assigned a project role.

Create a new project role

Navigate to Engineering -> Roles

spinner

Configure project role

The following settings can be made via the project role options

Project role options

If you disable a universal switch: The corresponding menu item will be hidden for holders of this role.

Element
Title
Details

[A]

Name

Project role name

[B]

Location

Determines at which location the ↗ map is opened (↗ Default map section)

[C]

Expert Mode

↗ Expert enable/disable Mode

[D]

Used in projects

Shows in which projects this role is used

[E]

Tags

Allow the role access to specific tags only ↗ Asset Tags

[F]

Full access to assets without tags

If this switch is enabled, users with this role have full access to assets that are not tagged. ↗ Full access to assets without tags

[G]

Tags

A list of all tags to which holders of this role have access

[H]

Universal switch «Dashboards»

Enable/disable all write permissions and read permission for the «Dashboards» function

[H1]

Dashboards

Enable/disable write and read access for the «Dashboards» function

[H2]

Widgets

Enable/disable write and read access for the «Widgets» function

[I]

Universal switch «Alarm»

Enable/disable all write permissions and read permission for the «Alarms» function

[I1]

Alarms

Enable/disable write and read access for the «Alarms» function

[I2]

Alarm history

Enable/disable write and read access for the «Alarm History» function

[J]

Universal switch «Tickets»

Enable/disable all write permissions and read permission for the «Tickets» function

[J1]

Augmented Reality

Enable/disable write and read access for the «Augmented Reality» function

[K]

Universal switch «Rules»

Enable/disable all write permissions and read permission for the «Rules» function

[K1]

Asset Editor

Grant write permission/read permission for the «Asset Editor»

[L]

Universal switch «Assets»

Enable/disable all write permissions and read permission for the «Assets» function

[L1]

Assets

Enable/disable write and read access for the «Assets» function

[M]

Universal switch «Analytics and Reports»

Enable/disable all write permissions and read permission for the «Analytics and Reports» function

[M1]

Analytics

Enable/disable write and read access for the «Analytics» function

[M2]

Reports

Enable/disable write and read access for the «Reports» function

[N]

Universal switch «Smart View»

Enable/disable all write permissions and read permission for the «Smart View» function

[N1]

Views

Enable/disable write and read access for the «Smart Views» function

[O]

Universal switch «Map and Floor»

Enable/disable all write permissions and read permission for the «Map and Floor» function

[O1]

Map and Floor

Enable/disable write and read access for the «Map and Floor» function

[P]

Universal switch «BIM»

Enable/disable all write permissions and read permission for the «BIM» function

[P1]

BIM

Enable/disable write and read access for the «BIM» function

[Q]

Universal switch «Digital Twin»

Enable/disable all write permissions and read permission for the «Digital Twin» function

[Q1]

Digital Twin

Enable/disable write and read access for «Digital Twin»

[R]

Universal switch «Connection»

Enable/disable all write permissions and read permission for the "Connection" function

[R1]

MQTT

Enable/disable write and read access for "MQTT"

[R2]

Webhook

Enable/disable write and read access for "Webhook"

[R3]

RESTful

Enable/disable write and read access for "RESTful"

[R4]

Kafka

Enable/disable write and read access for "Kafka"

[R5]

OPC UA

Enable/disable write and read access for "OPC UA"

[R6]

Legacy

Enable/disable write and read access for "Legacy"

[R7]

PKI

Enable/disable write and read access for "PKI"

[R8]

Node

Enable/disable write and read access for "Node"

[S]

Universal switch «Engineering»

Enable/disable all write permissions and read permission for the "Settings" function

[S1]

Users in other lists

If this function is enabled, users can under certain conditions see the names of other users, even if they are not enabled for this in the corresponding system role. ↗ More information

[S2]

escalation

Enable/disable write and read access for the "Escalation" function

[S3]

Script Engine

Enable/disable write and read access for the "Script Engine" function

[S4]

Asset Editor

Enable/disable write and read access for the "Asset Editor" function

[T]

Universal switch «AR»

Enable/disable all write permissions and read permission for the "Smart Assist" function

[T1]

AR

Enable/disable write permissions and read permission for the "Smart Assist" function

[U]

Save

You must save your selection

It is not possible to have write permissions but no read permissions.

More information about the different permissions can be found -> here

[C] The Expert Mode

If Expert Mode is enabled, ↗ Entities (e.g. tickets, digital twins, etc.) that are assigned to assets to which the role actually has no access can be accessed.

Example 1

  • An asset is tagged with «A», «B» and «C»

  • The user has read permission for tag A

  • The user has no read permission for tag B and tag C

  • The "Expert Mode" option is irrelevant in this example

▷ The user sees the asset in the asset overview

▷ The user sees tickets related to this asset

▷ In a ticket, the user sees the name of the asset. By clicking on the asset name, the user can open the asset details.

Example 2

  • An asset is tagged with «A», «B» and «C»

  • The user has no read permission for the 3 tags

  • The "Expert Mode" option is not enabled

▷ The user does not see the asset in the asset overview

▷ The user does not see any tickets related to this asset

Example 3

  • An asset is tagged with «A», «B» and «C»

  • The user has no read permission for any of the tags

  • The "Expert Mode" option is enabled

▷ The user does not see the asset in the asset overview

▷ The user sees tickets related to this asset

▷ In these tickets, the user does not see the name of the asset

[E] Asset Tags

If you add one or more tags here, this role can only see assets that are tagged with these tags. All other assets will be hidden.

Example: You add the tag "ventilation systems". This role will be able to access only assets that are tagged with "ventilation systems".

[F] Full access to assets without tags

If this option is enabled: Users have full access to all assets that have no (0) tags.

[S1] - Users in other lists

Whether a user can see the usernames of other users is actually defined in the system role. In certain cases, it may be desirable for users to be able to view the names of other users even though they do not have the rights for this in the system role.

For this, the switch [S1] can be enabled.

In the example below, a user can see the usernames after this option has been enabled.

Assign a project role to a user

spinner

Was this helpful?