> For the complete documentation index, see [llms.txt](https://documentation.pushly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.pushly.com/platform/organizations/organization-access.md).
# Organization Access
Manage who can access your organization and what they can do there
Organization access controls what someone can do at the **organization** level — its settings, its people, and its organization-wide notifications and segments. It is separate from access to any individual domain.
{% hint style="warning" %}
**Organization access grants nothing at the domain level.** An organization admin with no domain roles administers the organization and sees no domains in the domain list. Someone who needs both is given both, on the same screen.
{% endhint %}
An **Organization Admin** can grant and change organization access for other people in the organization. Before this was available in the platform, it was arranged through your Account Manager.
## Organization access levels
| Level | What it allows at the organization level |
| --------- | -------------------------------------------------------------------------------------------------------------------------------- |
| Admin | Change organization settings, manage other members' organization access, and manage organization-wide notifications and segments |
| User | See the organization and its members, and manage organization-wide notifications and segments |
| Read-Only | See the organization, its members, and its organization-wide notifications and segments |
| No Access | No organization-level access. Domain access is unaffected |
{% hint style="info" %}
Organization **User** is not a read-only role. It can create and send organization-wide notifications and manage organization-wide segments — it simply cannot change organization settings or anyone's access.
{% endhint %}
## Where to set it
Switch to the organization context — see [Organizations](https://documentation.pushly.com/platform/organizations) — then open **Settings** and the **Users** tab. Open any member to see their access.
A member's access panel shows two sections: **Organization** above **Domains**. Both are read-only in the panel; use **Edit** to change them.
Click the information icon beside **Organization** to see what each level grants without leaving the screen.
## Changing someone's organization access
1. Open the member from the organization user list.
2. Click **Edit**.
3. Set the level under **Organization**, and any domain levels they need under **Domains**.
4. Click **Submit**.
## Adding someone with organization access only
Someone can hold organization access and no domain access at all — useful for a person who works across organization-wide notifications and reporting without owning any single property. Use **Add User** from the organization user list and leave every domain at **No Access**.
## Related
* [User Management](/platform/user-management.md) — access to individual domains
* [Organizations](https://documentation.pushly.com/platform/organizations) — switching to the organization context and what is available there
* [API Access](/platform/organizations/api-access.md) — organization API tokens, which require Organization Admin
---
# 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.pushly.com/platform/organizations/organization-access.md?ask=&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.
