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

# Permissions and access policies

Permissions determine which actions a user or group can perform across the portal.

### Global permissions

Global permissions apply across a broad product area. They are appropriate when a role genuinely needs the same capability throughout the portal.

### Specific permissions

Specific permissions target a particular resource or scope. Use them when access should be narrow and explicit.

### Effective permissions

A user’s effective permissions can come from their user type, one or more groups, and direct user settings. When troubleshooting, inspect each source rather than assuming the nearest visible setting is the only one in effect.

{% hint style="info" %}
Prefer group-based permissions for roles and teams. Reserve direct user permissions for genuine exceptions and review those exceptions periodically.
{% 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://synap.ac/docs/platform/users/permissions-and-access-policies.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.