Roles and what each can do

Summary#

Metric Vault has one enforced permission system for teammates: the blog role, which governs what a member can do in Blog Studio. Access to the rest of the workspace is granted by membership itself, and the rest of a member's dashboard continues to show their own account's data. This page sets out exactly what each role controls so you can assign it with confidence.

Overview#

When you invite someone you pick a value in the BLOG ROLE dropdown. That value does two things: it becomes the badge shown next to the person in Your Team, and it becomes their permission level in Blog Studio.

It does not act as a general access control. There is no viewer-only mode and no per-tool permission today. Every member of a workspace reaches the owner's Blog Studio, and the role decides what they may do once they are there: an Author is confined to their own posts, while an Editor can manage the whole content pipeline. Outside Blog Studio, each person's dashboard shows their own account's data — What teammates share draws that line precisely.

The upside of the model is that it is predictable. There is one matrix to reason about, it applies to one screen, and there is no per-tool toggle to get wrong.

The roles you can assign#

Any value the system does not recognize is treated as Author, which is the least-privileged setting. That means a role you cannot account for is never more powerful than Author.

Blog Studio permission matrix#

This is the one matrix the product enforces. It applies to the owner's blog: an accepted member works inside the owner's Blog Studio, not their own.

When someone attempts an action their role does not allow, the request is refused with Your blog role does not allow this action (<capability>). The capability name in the message identifies which of the rows above was checked.

What the role does not control#

Reading the badges in Your Team#

Each member row shows a role badge and a status badge.

Changing someone's role#

Each member row carries a role dropdown offering Owner, Editor and Author. Choosing Editor or Author saves immediately and takes effect on their next Blog Studio action. Choosing Owner is refused, and because the change is saved silently the dropdown may keep showing Owner until you reload the Team screen. If you need to confirm a role, reload the page and read the badge on the member's row rather than the dropdown.

There is no notification to the member when their role changes.