> For the complete documentation index, see [llms.txt](https://docs.inspector.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inspector.dev/security-and-access/permissions.md).

# Access control

### Organization access control

When you set up your Inspector account, an **Organization** is automatically created.

An organization is essentially a container for your applications, settings, and team members.

Within the organization, you can add members and assign them different roles and permissions. This document covers the different roles and the ways you can assign permissions.

### Application Permissions

You can restrict the developers access to your Inspector organization by limiting access to one or more applications without being able to access organization data.

Our authorization system give you the ability to limit the access of your collaborator to specific projects they are responsible for.

![](/files/-LuX7Cj6UXv6dZYNc3Aq)

Here is a short video about “*per-app*” authorization: <https://www.youtube.com/watch?v=ZOn8SD3pWzw>

### Admin

If you want to share full control of your organization data with other team members you can assign them the `Admin` role.

![](/files/-LuX7WycyfMRPccCGC8u)

{% hint style="danger" %}
"Admin" permission allows users to view/delete organization's projects and to access and modify organization informations (billing, subscription plan, users, etc...).
{% 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.inspector.dev/security-and-access/permissions.md?ask=<question>&goal=<endgoal>
```

`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.