> 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/user-types.md).

# User types

User types define a person’s main role and baseline portal experience. Use them for genuine differences in capability and navigation, not merely for reporting categories.

| Type          | Intended experience                                                     |
| ------------- | ----------------------------------------------------------------------- |
| Student       | Opens learner pages and completes learning or assessment content        |
| Educator      | Creates and manages permitted content and cohorts                       |
| Manager       | Performs broad operational management apart from certain global actions |
| Administrator | Configures and administers the whole portal                             |
| Marker        | Works with Attempts allocated through marking workflows                 |
| Guest         | Uses a limited externally oriented experience where configured          |

Page controls can enable or hide major areas, change navigation labels and redirect unavailable pages. For Educators, the actions available inside those pages are then governed by Permissions. Students use the simpler content-access system rather than staff Permissions.

{% hint style="warning" %}
Changing a User type can alter much more than its label. Test navigation, landing page, content visibility and direct links with a representative account before applying a change widely.
{% 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/user-types.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.