> For the complete documentation index, see [llms.txt](https://help.cloudjournals.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cloudjournals.com.au/collaborating/overview/roles-and-permissions.md).

# Roles & Permissions

## Roles & Permissions

Within a relationship, the Contributor and their Beneficiary perform a particular Role. The *relationship* is defined by the roles each performs, and therefore the level of access the Contributor gains to the Beneficiary's content. There are four different relationships that exist in Cloud Journals and they are the following:

### Peer <a href="#peer" id="peer"></a>

By inviting a user to contribute as a Peer, the Beneficiary is giving the Contributor access to view their self-appraisals, reflections and evidence. The Contributor can provide feedback to parts of their specified [Journal](/the-core/journals.md), [Learning Log](/the-core/learning-log.md) or [Plan](/the-core/plan.md), if they have given them [permission](/collaborating/overview/roles-and-permissions.md).

### Coach <a href="#coach" id="coach"></a>

View only your Beneficiary's [Plan](/the-core/plan.md) and provide feedback.

### Supervisor <a href="#supervisor" id="supervisor"></a>

View your Beneficiary's journal and provide feedback and appraisals within levels set for *Supervisors* within that [Journal Template](/admin-console/template-editor/template-design.md#what-are-templates), [Learning Log](/the-core/learning-log.md) or [Plan](/the-core/plan.md), according to the [permissions](/collaborating/overview/roles-and-permissions.md) they have given you.

### Assessor <a href="#assessor" id="assessor"></a>

View and provide feedback and appraisals to levels allowed by industry or organisation certifiers and as applied within the Template for the specific Journal that you have been invited to access. Assessors also get access to the [Learning Log](/the-core/learning-log.md).


---

# 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://help.cloudjournals.com.au/collaborating/overview/roles-and-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.