> For the complete documentation index, see [llms.txt](https://help.modelreef.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.modelreef.io/help/permissions-and-collaboration/model-level-permissions.md).

# Model Level Permissions

This article explains **model level permissions** in Model Reef.

You will learn:

* What model level permissions control.
* When to use model level roles instead of branch level access.
* How model level permissions interact with collaboration tools.

Model level permissions are the simplest way to share a model with your team.

{% stepper %}
{% step %}

### What model level permissions control

When you assign a role at **model level**:

* The user gains access to the entire model.
* They can see every branch and variable.
* They can see every dashboard, report and valuation output.
* Their abilities (edit vs view) are determined by whether they are an Owner, Editor or Viewer.

There is no branch by branch filtering at this level.
{% endstep %}

{% step %}

### When to use model level permissions

Model level permissions are ideal when:

* Everyone on the team is allowed to see the full model.
* The model is for internal use only.
* Separation of teams by entity or division is not required.
* You want quick and simple sharing for collaboration.

In this case, you mainly decide whether each collaborator should be an Owner, Editor or Viewer.
{% endstep %}

{% step %}

### Combining model level and branch level permissions

In some cases you might:

* Give a small group model level Owner access for governance.
* Give selected team members model level Editor access so they can work freely.
* Use branch level permissions only for external collaborators or sensitive areas.

Model Reef uses the most permissive role at model level, so if a user is an Editor at model level they cannot be restricted to read only on a specific branch.

As a rule of thumb:

* Use **model level** roles for core internal team.
* Use **branch level** roles for segmented or external collaboration.
  {% endstep %}

{% step %}

### Model level permissions and collaboration tools

Model level permissions also control collaboration visibility:

* A model level Owner or Editor can see and edit all notes, comments, tags and attachments.
* A model level Viewer can see, but not change, all collaboration artefacts.

Even with model level access, actions are still governed by the core role type constraints.
{% endstep %}
{% endstepper %}

***

## Related articles

* [Clinic-Level Profitability](/use-cases/healthcare-clinics-and-allied-health/clinic-level-profitability.md)
* [Convert a PDF to a Structured Forecast](/how-tos/data-workflows-and-automation/convert-a-pdf-to-a-structured-forecast.md)
* [P\&L Overview](/help/financial-outputs-and-valuation/p-and-l-overview.md)
* [Frequency Inputs](/syntax/timing-syntax/frequency-inputs.md)