Editor Permissions
This article describes what Editors can do in a Model Reef model.
You will learn:
What Editors can change in a model.
How branch level access limits Editor scope.
How Editors use notes, comments, tags and attachments.
Access scope for Editors
Editors can be granted access at:
Model level
Full visibility of the entire model and branch tree.
Can edit all branches and variables.
Branch level
Visibility only for specified branches and their children.
Can edit variables and structure only within those branches.
Cannot see or change branches they do not have access to.
Branch level access is useful when multiple teams work in parallel on different parts of the model.
What Editors can change
Within their allowed scope, Editors can:
Create, edit and delete variables.
Change drivers, formulas, timing and delays.
Change variable names, categories and branches.
Create and edit Data Library entries.
Build or adjust dashboards and custom reports.
Create new branches inside their permitted sections and move sub branches under them.
Editors cannot:
Change roles or permissions for other users.
Archive or delete the entire model.
Access branches outside their assigned scope.
Collaboration tools for Editors
Editors play a central role in collaboration. They can:
Add notes to variables, branches and Data Library entries.
Create and respond to comments.
Tag items for review, approval or grouping.
Upload supporting attachments such as PDFs, spreadsheets or screenshots.
Viewers can see these collaboration artefacts but cannot modify them.
Best practices for Editors
To keep the model clean and reviewable, Editors should:
Use clear naming conventions for variables and branches.
Document major assumptions with notes and attachments.
Tag items that need review or sign off.
Avoid changing structures or assumptions outside their responsibility area.
Owners can then review Editor changes via dashboards, reports and targeted drill downs.
Related articles
Last updated