> 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/administration-and-communications.md).

# Administration and communications

The Management section contains account controls that affect the person beyond a single item of content.

### Groups and Permissions

**User groups** explains the roles and cohorts the person belongs to. **Permissions** shows administrative abilities granted directly to this account. Direct Permissions are additive to group Permissions, so use them for genuine exceptions rather than routine team access.

### Administration actions

Depending on your own Permissions, Administration can let you edit account details and change account state.

| Action            | Result                                                     |
| ----------------- | ---------------------------------------------------------- |
| Remove from group | Keeps the account but removes one membership               |
| Disable           | Keeps the account and history but prevents sign-in         |
| Reactivate        | Allows a disabled account to sign in again                 |
| Delete            | Removes the account and can affect retention and reporting |

### Communications and learning history

Email history helps confirm which Synap messages were sent; it does not guarantee that the recipient opened or acted on them. Records of learning hold approved activity that may have taken place outside the usual Synap Attempt flow.

{% hint style="danger" %}
Prefer removal from a group or disabling when the account and its history should be retained. Use deletion only when deletion itself is the intended and authorised outcome.
{% 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/administration-and-communications.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.