> For the complete documentation index, see [llms.txt](https://docs.fabricplan.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fabricplan.com/documentation/readme/roles-in-fabric-plan/role-upgrades.md).

# Role upgrades

Planning roles are assigned dynamically based on user actions through time‑bound sessions. Role upgrades occur based on valid planning actions and are governed by session rules to ensure controlled access.

#### Session duration and start

* A session starts from the first planning action performed by a user (for example, opening a planning sheet).
* Each session has a fixed duration of 30 days.

#### Role upgrades and sessions

* When a planning action triggers an upgrade to a higher role, the system creates a new session for the upgraded role.
* The previous session is prorated based on the time already consumed.

{% hint style="info" %}
Roles can only be upgraded to higher privilege levels. Downgrades are not supported within an active session.
{% endhint %}

#### Session expiry

* Each session automatically terminates after 30 days.
* After 30 days from the first action, a new session begins with the Viewer role.

#### Manual role upgrades

A user is initially assigned the Viewer role. To manually upgrade, select the role and select the upgrade option.

<figure><img src="/files/BdcePxzwPFb94exWiFDL" alt=""><figcaption></figcaption></figure>

Accept the upgrade notification to proceed with the role change.

<figure><img src="/files/2k4GpnBkBvHk4mQvKQZj" alt=""><figcaption></figcaption></figure>

#### Upgrade prompts

* Upgrade prompts are disabled by default.
* A workspace‑level setting controls whether users are prompted before a role upgrade occurs.
* When enabled, an upgrade notification appears before the role is upgraded.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.fabricplan.com/documentation/readme/roles-in-fabric-plan/role-upgrades.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.