> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/documentation/rollen/projektrollen.md).

# 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*

{% @supademo/embed url="<https://app.supademo.com/demo/FbyUVm0B-hzWFp2LFv5o6>" demoId="FbyUVm0B-hzWFp2LFv5o6" fullWidth="true" %}

## Configure project role

The following settings can be made via the project role options

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/nC0enETmMDuAKLOOMAbH/Docs_Projektrolle%20U%CC%88berblickv2.png" alt=""><figcaption><p>Project role options</p></figcaption></figure></div>

{% hint style="info" %}
If you disable a universal switch: The corresponding menu item will be hidden for holders of this role.
{% endhint %}

<table data-full-width="true"><thead><tr><th width="103.33333333333331">Element</th><th>Title</th><th>Details</th></tr></thead><tbody><tr><td><strong>[A]</strong></td><td>Name</td><td>Name of the project role</td></tr><tr><td><strong>[B]</strong></td><td>Location</td><td>Determines at which location the <a href="/collection/english-v14/documentation/karte-und-stockwerk/karte.md">↗ map</a> is opened (<a href="/collection/english-v14/documentation/karte-und-stockwerk/karte.md#standard-kartenausschnitt-festlegen">↗ Default map section</a>)</td></tr><tr><td><strong>[C]</strong></td><td>Expert mode</td><td><a href="#c-der-expert-mode">↗ Expert </a>Enable/disable mode</td></tr><tr><td><strong>[D]</strong></td><td>Used in projects</td><td>Indicates in which projects this role is used</td></tr><tr><td><strong>[E]</strong></td><td>Tags</td><td>Allow this role access only to certain tags<a href="#e-asset-tags"> </a><a href="#e-asset-tags">↗ Asset Tags</a></td></tr><tr><td><strong>[F]</strong></td><td>Full access to assets without tags</td><td>If this switch is enabled, users with this role have full access to assets that are not tagged. <a href="#f-voller-zugriff-auf-assets-ohne-tags">↗ Full access to assets without tags</a></td></tr><tr><td><strong>[G]</strong></td><td>Tags</td><td>A list of all tags to which holders of this role have access</td></tr><tr><td><strong>[H]</strong></td><td><strong>Universal switch «Dashboards»</strong></td><td><strong>Enable/disable all write permissions and read permission for the function «Dashboards»</strong></td></tr><tr><td><strong>[H1]</strong></td><td>Dashboards</td><td>Enable/disable write and read access for the function «Dashboards»</td></tr><tr><td><strong>[H2]</strong></td><td>Widgets</td><td>Enable/disable write and read access for the function «Widgets»</td></tr><tr><td><strong>[I]</strong></td><td><strong>Universal switch «Alarm»</strong></td><td><strong>Enable/disable all write permissions and read permission for the function «Alarms»</strong></td></tr><tr><td><strong>[I1]</strong></td><td>Alarms</td><td>Enable/disable write and read access for the function «Alarms»</td></tr><tr><td><strong>[I2]</strong></td><td>Alarm history</td><td>Enable/disable write and read access for the function «Alarm history»</td></tr><tr><td><strong>[J]</strong></td><td><strong>Universal switch «Tickets»</strong></td><td><strong>Enable/disable all write permissions and read permission for the function «Tickets»</strong></td></tr><tr><td><strong>[J1]</strong></td><td>Augmented Reality</td><td>Enable/disable write and read access for the function «Augmented Reality»</td></tr><tr><td><strong>[K]</strong></td><td><strong>Universal switch «Rules»</strong></td><td><strong>Enable/disable all write permissions and read permission for the function «Rules»</strong></td></tr><tr><td><strong>[K1]</strong></td><td>Asset Editor</td><td>Grant write permission/read permission for the «Asset Editor»</td></tr><tr><td><strong>[L]</strong></td><td><strong>Universal switch «Assets»</strong></td><td><strong>Enable/disable all write permissions and read permission for the function «Assets»</strong></td></tr><tr><td><strong>[L1]</strong></td><td>Assets</td><td>Enable/disable write and read access for the function «Assets»</td></tr><tr><td><strong>[M]</strong></td><td><strong>Universal switch «Analytics and Reports»</strong></td><td><strong>Enable/disable all write permissions and read permission for the function «Analytics and Reports»</strong></td></tr><tr><td><strong>[M1]</strong></td><td>Analytics</td><td>Enable/disable write and read access for the function «Analytics»</td></tr><tr><td><strong>[M2]</strong></td><td>Reports</td><td>Enable/disable write and read access for the function «Reports»</td></tr><tr><td><strong>[N]</strong></td><td><strong>Universal switch «Smart View»</strong></td><td><strong>Enable/disable all write permissions and read permission for the function «Smart View»</strong></td></tr><tr><td><strong>[N1]</strong></td><td>Views</td><td>Enable/disable write and read access for the function «Smart Views»</td></tr><tr><td><strong>[O]</strong></td><td><strong>Universal switch «Map and Floor»</strong></td><td><strong>Enable/disable all write permissions and read permission for the function «Map and Floor»</strong></td></tr><tr><td><strong>[O1]</strong></td><td>Map and Floor</td><td>Enable/disable write and read access for the function «Map and Floor»</td></tr><tr><td><strong>[P]</strong></td><td><strong>Universal switch «BIM»</strong></td><td><strong>Enable/disable all write permissions and read permission for the function «BIM»</strong></td></tr><tr><td><strong>[P1]</strong></td><td>BIM</td><td>Enable/disable write and read access for the function «BIM»</td></tr><tr><td><strong>[Q]</strong></td><td><strong>Universal switch «Digital Twin»</strong></td><td><strong>Enable/disable all write permissions and read permission for the function «Digital Twin»</strong></td></tr><tr><td><strong>[Q1]</strong></td><td>Digital Twin</td><td>Enable/disable write and read access for «Digital Twin»</td></tr><tr><td><strong>[R]</strong></td><td><strong>Universal switch «Connection»</strong></td><td><strong>Enable/disable all write permissions and read permission for the function "Connection"</strong></td></tr><tr><td><strong>[R1]</strong></td><td>MQTT</td><td>Enable/disable write and read access for "MQTT"</td></tr><tr><td><strong>[R2]</strong></td><td>Webhook</td><td>Enable/disable write and read access for „Webhook“</td></tr><tr><td><strong>[R3]</strong></td><td>RESTful</td><td>Enable/disable write and read access for „RESTful</td></tr><tr><td><strong>[R4]</strong></td><td>Kafka</td><td>Enable/disable write and read access for „Kafka“</td></tr><tr><td><strong>[R5]</strong></td><td>OPC UA</td><td>Enable/disable write and read access for „OPC UA“</td></tr><tr><td><strong>[R6]</strong></td><td>Legacy</td><td>Enable/disable write and read access for „Legacy</td></tr><tr><td><strong>[R7]</strong></td><td>PKI</td><td>Enable/disable write and read access for „PKI</td></tr><tr><td><strong>[R8]</strong></td><td>Node</td><td>Enable/disable write and read access for "Node"</td></tr><tr><td><strong>[S]</strong></td><td><strong>Universal switch «Engineering»</strong></td><td><strong>Enable/disable all write permissions and read permission for the function "Settings"</strong></td></tr><tr><td><strong>[S1]</strong></td><td>Users in other lists</td><td>If this function is enabled, users can under certain circumstances see the names of other users, even if they are not enabled for this in the corresponding system role. ↗ More information</td></tr><tr><td><strong>[S2]</strong></td><td>Escalation</td><td>Enable/disable write and read access for the function „Escalation“</td></tr><tr><td><strong>[S3]</strong></td><td>Script Engine</td><td>Enable/disable write and read access for the function „Script Engine“</td></tr><tr><td><strong>[S4]</strong></td><td>Asset Editor</td><td>Enable/disable write and read access for the function "Asset Editor"</td></tr><tr><td><strong>[T]</strong></td><td><strong>Universal switch «AR»</strong></td><td><strong>Enable/disable all write permissions and read permission for the function "Smart Assist"</strong></td></tr><tr><td><strong>[T1]</strong></td><td>AR</td><td>Enable/disable write permissions and read permission for the function "Smart Assist"</td></tr><tr><td><strong>[U]</strong></td><td>Save</td><td>You must save your selection</td></tr></tbody></table>

{% hint style="warning" %}
Don't forget to **Save** **\[U]**
{% endhint %}

{% hint style="info" %}
It is not possible to have write rights but no read rights.
{% endhint %}

{% hint style="info" %}
You can get more information about the different permissions [-> here](/collection/english-v14/documentation/rollen.md#leseberechtigung-und-schreibberechtigung)
{% endhint %}

### Ticket permissions

The universal switch **Tickets \[J]** controls access to the ticket area. The ticket list view, ticket details and tasks are separately authorized. For ticket details and tasks, the levels **Read**, **Write** and **Manage**determine who can view, create, edit or manage content. In addition, special rules apply to assignees and creators.

[-> Permissions for tickets and tasks](/collection/english-v14/documentation/tickets/rechte-fuer-tickets-und-tasks.md)

### \[C] The Expert Mode

If Expert Mode is enabled, [↗ Entities](/collection/english-v14/preface/glossar.md#entitaeten) (e.g. tickets, digital twins, etc.) can be accessed that are assigned to assets to which the role actually has no access.

#### 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 option „Expert Mode“ is irrelevant in this example

▷ The user sees the asset in the asset overview

▷ The user sees tickets that relate 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.

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/4vMiXitcD7FZWJhHEBDW/Docs_Roles_Pg3%20-%201%20Expert%20Mode.png" alt=""><figcaption></figcaption></figure>

#### Example 2

* An asset is tagged with «A», «B» and «C»
* The user has no read permission for the 3 tags
* The option „Expert Mode“ is **not** enabled

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

▷ The user does not see any tickets that relate to this asset

#### Example 3

* An asset is tagged with «A», «B» and «C»
* The user has no read permission for all tags
* The option „Expert Mode“ is enabled

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

▷ The user sees tickets that relate to this asset

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

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/Vgrz9czMXNQjnQ31ElzH/Docs_Roles_Pg3%20-%202%20Expert%20Mode.png" alt=""><figcaption></figcaption></figure>

### \[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 only be able to access assets that are tagged with the tag "Ventilation systems".

{% hint style="warning" %}
If an asset is assigned multiple tags: The role has access to the asset even if it is enabled for only one of the asset's tags.
{% endhint %}

### \[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 see the names of other users even though they lack the rights for this in the system role.

For this, the toggle **\[S1]** can be enabled.

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

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/eEBBAOp6JDiHQRAz5o92/Docs%20Roles%20-%20Can%20be%20seen%20by%20other%20Roles.png" alt=""><figcaption></figcaption></figure>

## Assign a project role to a user

{% @supademo/embed url="<https://app.supademo.com/demo/oukZv4RR6w0t7GGGkoFUS>" demoId="oukZv4RR6w0t7GGGkoFUS" fullWidth="true" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.buildings.ability.abb/collection/english-v14/documentation/rollen/projektrollen.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.