> For the complete documentation index, see [llms.txt](https://docs.controlbee.nl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.controlbee.nl/en/partner-portaal/partner-gebruikers.md).
# Partner users
Manage partner accounts for access to customer and template environments
## General information
On the Partner page, the partner can edit their general information and the partner environment can be activated or deactivated as a whole. In addition, partner users are managed here.
## Partner users
So that employees of implementation partners do not need separate accounts for each customer, the partner can manage partner accounts. These accounts have the following characteristics:
* The partner account provides access to the partner portal. Administrative rights in the partner portal are reserved for partner managers.
* Partner accounts can be added to the partner's customer environments and template environments. The following applies:
* **Partner manager** — is added by default to all customer environments
* **Partner user** — is selectively added to customer environments
* The login credentials (password and 2FA) of partner accounts are the same for the partner portal and the individual environments. That information is synchronized automatically.
* Partner accounts can bypass Single Sign-On in customer environments.
* Partner accounts do not count toward license usage.
When adding a partner user, the name and email address are entered, and it is selected whether the user is a partner manager or a partner user.
As soon as a partner user is removed in the partner portal, the account is also automatically removed from the underlying customer environments.
{% hint style="warning" %}
It remains the partner's responsibility to check that removed users no longer appear in the customer environments. If a partner user was not added correctly from the environment, there is a risk that the account will not be removed automatically. For verification, run an export of users in the environments overview within the partner portal and search for the relevant user there.
{% endhint %}
---
# 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.controlbee.nl/en/partner-portaal/partner-gebruikers.md?ask=&goal=
```
`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.
