> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/trulyp/members-teams-and-roles.md).
# Members, Teams and Roles
Explaining access in Trulyp
Trulyp has **Roles** and **Teams**, that both play a role in what users are allowed to do.
* **Roles** determine **what a user is allowed to do**.
* **Teams** determine **where or to what they can do it**.
For example, a user with the **Connection Manager** role can edit connections. However, they can only edit connections that are assigned to their team.
In short: **Roles define permissions; teams define their scope.**
#### How access works
Access in UAW is determined by a combination of **roles, and resource-specific permissions**.
* **Roles are additive.** Assign every role a person needs for their responsibilities.
* A person needs **at least one role** or **administrator status** to access Trulyp.
* **Roles do not override data access.** Group membership, connection access, schema permissions, row-level security, dashboard sharing, and other resource-specific rules continue to apply.
* **AI follows the same permissions.** The assistant and MCP tools apply the same role and resource checks. Access to an AI feature does not grant access to data or actions that the person could not otherwise use.
{% hint style="info" %}
**Administrator access**
Administrator is a privilege, not an assignable role. Administrators have full access to the management console and bypass role checks.
Use administrator access only for trusted platform administrators.
{% 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.infotopics.com/trulyp/members-teams-and-roles.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.
