> 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/settings/members-teams-roles-and-access.md).

# Members, Teams, Roles and access

Who can do what in Trulyp comes down to three things:

* **Members** are the people who use Trulyp and its extensions.
* **Roles** decide **what** a member can do, for example manage connections or create dashboards.
* **Teams** decide **where** they can do it: which connections, semantic providers and data they can use.

For example, a member with the **Connections manager** role can edit connections, but only the connections shared with one of their teams.

In short: **roles define permissions; teams define their scope.**

### How access works

* **Roles add up.** Give every role a person needs for their work. See [Roles](/trulyp/settings/members-teams-roles-and-access/roles.md).
* **Signing in to Trulyp needs at least one role**, or administrator access. Members without any role can still use the extensions in Tableau, but can't open the Trulyp workspace.
* **Roles don't override data access.** Team access to connections, schema permissions, row-level security, dashboard sharing and other rules still apply. See [Access control](/trulyp/settings/members-teams-roles-and-access/access-control.md).
* **AI follows the same permissions.** Vizzy and connected AI apps apply the same checks; an AI feature never gives access to data or actions the person couldn't otherwise use.

{% hint style="info" %}
**Administrator access** isn't a role: it's a setting on a member (**User is administrator**). Administrators can do everything and bypass all role checks. Only give it to trusted platform administrators.
{% endhint %}

{% content-ref url="/pages/iQXzCPA32MI7KxmvQTFK" %}
[Members](/trulyp/settings/members-teams-roles-and-access/members.md)
{% endcontent-ref %}

{% content-ref url="/pages/ZGrwAw5CPcHp2sC2mFFS" %}
[Teams](/trulyp/settings/members-teams-roles-and-access/teams.md)
{% endcontent-ref %}

{% content-ref url="/pages/Kcqr9wcVCfXrfKqOAfYi" %}
[Roles](/trulyp/settings/members-teams-roles-and-access/roles.md)
{% endcontent-ref %}


---

# 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.infotopics.com/trulyp/settings/members-teams-roles-and-access.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.