> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/stifler/setup/upgrading-from-stifler-3.0-to-3.1.md).

# Upgrading from StifleR 3.0 to 3.1

The upgrade from 3.0 to 3.1 is in-place. Install the new server over the existing installation and restart the service.

### After upgrading

#### Set up RBAC roles

RBAC is new in 3.1. No roles exist after upgrade — you need to create them if you want to use fine-grained access control.

Your existing Global Admin and Global Read configuration (set via the Config Editor `AdministratorGroup` and `ReadGroup` settings) carries over automatically. Users in those groups will continue to have full or read-only access as before.

If you do not set up any roles, users who are not Global Admin or Global Read will be blocked at login. Create at least one role with appropriate permissions for your users before rolling out to production.

See [Roles and Permissions](/stifler/configuration/roles-and-permissions-rbac.md) for how to create roles and assign claim rules.

#### Remote Tools permissions are not migrated

In 3.0, Remote Tools had its own access control configuration. That configuration is **not carried over** to 3.1.

### Rolling out 3.1 clients

You do not need to upgrade all clients at the same time as the server.

| Scenario                | Behaviour                                                                                                                                   |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| 3.0 client → 3.1 server | Works normally. 3.0 clients are unaware of the new capability endpoint and ignore it.                                                       |
| 3.1 client → 3.0 server | Client defaults to standard mode. The 3.0 server does not support the licensing endpoint, so the client assumes no restriction is intended. |

You can upgrade the server first and roll out 3.1 clients at your own pace. 3.1 clients still pointing at a 3.0 server will run in full mode — no disruption during the transition.


---

# 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://documentation.2pintsoftware.com/stifler/setup/upgrading-from-stifler-3.0-to-3.1.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.