# Owner Permissions

This article describes what **Owners** can do in a Model Reef model.

You will learn:

* The full scope of Owner control.
* How Owners manage access for other users.
* How Owners use collaboration tools safely across a team.

Owners are responsible for governance, structure and access control for a model.

{% stepper %}
{% step %}

### Access scope for Owners

An Owner has full access to a model:

* Can see all branches and variables.
* Can view and edit all dashboards, reports and valuation settings.
* Can use any scenario or model as a base for new versions.
* Can see and manage all notes, comments, tags and attachments.

There is no branch level restriction on an Owner. They always see the full branch tree.
{% endstep %}

{% step %}

### Structural and modelling powers

Owners can:

* Create, rename and delete branches.
* Move branches around in the hierarchy.
* Create, rename and delete variables and drivers.
* Change variable types, categories and branches.
* Edit Data Library entries and global assumptions.
* Change model settings such as periodicity, start and end dates and valuation configuration.

Because Owners have unlimited edit rights, there should usually be a small number of Owners per model.
{% endstep %}

{% step %}

### Permission management

Only Owners can:

* Invite new collaborators to the model.
* Assign or change roles for collaborators.
* Configure model level and branch level access.
* Remove collaborators from the model.
* Decide which branches are visible to which collaborators.

This is the main governance mechanism in Model Reef. It ensures that Editors and Viewers only see the parts of the model the Owner intends.
{% endstep %}

{% step %}

### Collaboration tools for Owners

Owners can also:

* Add, edit and delete notes and comments anywhere in the model.
* Tag variables, branches and Data Library entries.
* Upload and remove attachments.
* Review and clean up collaboration artefacts as the model evolves.

Notes, comments and tags are visible to anyone with access to the relevant branches, so Owners should use them to document key assumptions and decisions.
{% endstep %}

{% step %}

### Archiving and lifecycle control

Owners control the lifecycle of the model:

* Can archive the model when it is no longer active.
* Can restore archived models if needed.
* Can duplicate the model to create new versions or scenarios.
* Can remove models entirely if they are no longer required.

These actions affect the entire model and all collaborators attached to it.
{% endstep %}
{% endstepper %}

***

## Related articles

* [ARR/MRR Forecasting](/use-cases/saas-and-subscription-businesses/arr-mrr-forecasting.md)
* [Build an Investor Update Pack](/how-tos/dashboards-and-reporting/build-an-investor-update-pack.md)
* [Viewer Permissions](/help/permissions-and-collaboration/viewer-permissions.md)
* [Formula Syntax](/syntax/formula-syntax.md)


---

# Agent Instructions: 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:

```
GET https://help.modelreef.io/help/permissions-and-collaboration/owner-permissions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.