Roles and what each can do
What the role you pick for a teammate controls today, the Blog Studio permission matrix, and how workspace access is granted.
Last updated 2026-08-06
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 choose their ACCESS: which groups of tools they can open, what they are allowed to do, and which of your websites they can see. That choice is enforced by the server on every request, not just hidden in the interface.
Underneath it, the Blog Studio role still decides who may edit whose post once they are inside Blog Studio. The two compose, and the order matters: the access you grant decides whether they reach Blog Studio at all, and the blog role decides what they may do there. Someone you give Blog Studio access to is an Editor there; everyone else is an Author, which is the least-privileged setting.
Presets#
Most invites do not need the detail. The ACCESS dropdown carries five answers, and Choose exactly opens the full picker.
| Preset | What they can open | What they can do |
|---|---|---|
| Full access | Every group of tools | Run tools, export and share, publish, change settings |
| Content and blog | Content, Blog Studio, Saved work | Run tools, export and share |
| Keyword research | Keyword research, Saved work | Run tools, export and share |
| Social publishing | Social and outreach, Saved work | Run tools, export and share, publish |
| Read only | Every group of tools | Nothing. They can look at results but not run, export or change anything |
| Choose exactly | Whatever you tick | Whatever you tick |
Never shared, whatever you pick#
Two things are the account owner's alone and no preset or tick box opens them:
- API keys. A key is the whole account in one string.
- Billing. The plan, the payment method and checkout all bill the owner's card. The
See billingpermission opens the billing screen to read; it never opens a change.
A teammate who tries either gets Your team access does not include the account owner's settings.
What each permission covers#
| Tools they can open | Covers |
|---|---|
| Overview | The dashboard home and the daily briefing |
| Keyword research | Keyword Explorer, keyword gaps, topics and briefs |
| Content | Writing, optimising and the article tools |
| Blog Studio | Writing and publishing blog posts |
| Social and outreach | Social posting, PR and outreach |
| Technical SEO | Site audits, speed and crawl checks |
| Analytics and reports | Rankings, backlinks, Search Console and scheduled reports |
| AI visibility | Prompt tracking and AI search visibility |
| Local SEO | Local rankings and niche demand |
| Saved work | Past runs and saved reports |
| Websites and integrations | Connecting websites and services |
| Account and team | Account settings and teammates |
| What they can do | Covers |
|---|---|
| Run tools | Anything that spends your credits. Without it they can still open a tool and read past results, but not start a new run |
| Export and share | Downloads and public share links |
| Publish | Posting to connected social accounts and CMSs |
| Change settings | Adding, editing and removing websites and integrations |
| Manage the team | Inviting and removing other teammates |
| See billing | Reading the plan and usage screen |
Websites#
Leave every website ticked and they get the whole account, including any website you add later. Tick specific ones and they see only those.
Teammates invited before this existed#
A membership created before granular access shipped has no permissions recorded against it, and keeps exactly the access it already had: the full workspace, with the blog role applying inside Blog Studio. Nobody was locked out of a workspace they were already working in. Those rows show as Full access, and changing them is the same as changing anyone else's.
Changing someone's access afterwards#
Your Team shows each person's access next to their name, and that control is also how you change it. Pick a different level and it saves immediately; the blog role follows it, so narrowing somebody to Keyword research also stops them editing posts. There is no remove-and-re-invite step, and the person keeps their place on the team.
Access you assembled by hand with Choose exactly shows as Custom. Picking a named level from the row replaces it.
The blog roles you can assign#
| Option in the dropdown | Badge shown in Your Team | What it controls |
|---|---|---|
Author — own posts only | Author | Blog Studio: may write and edit their own posts and upload media. This is the default and the safest choice. |
Editor — posts & media | Editor | Blog Studio: may write, edit and delete any post, manage categories and tags, and upload media. Cannot change blog settings. |
Owner — full access | — | Not assignable. Selecting it returns A member cannot be invited as 'owner'. Ownership belongs to the workspace creator; see Workspace ownership. |
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 applies to the owner's blog: an accepted member works inside the owner's Blog Studio, not their own. It only comes into play once the person has Blog Studio in their access; without it they never reach the screen.
| Capability | Owner | Editor | Author |
|---|---|---|---|
| Create and edit any post | Yes | Yes | No |
| Create and edit their own posts | Yes | Yes | Yes |
| Delete posts | Yes | Yes | No |
| Manage categories and tags | Yes | Yes | No |
| Upload and use media | Yes | Yes | Yes |
| Change blog settings | Yes | No | No |
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.
Note: A person who is a member of more than one workspace works on the blog of their most recently accepted workspace. Blog Studio does not follow the workspace switcher. If someone needs to publish to a specific blog, make sure that workspace is the last one they accepted, or have them join it again after being removed and re-invited.
What the role does not control#
| Area | Governed by |
|---|---|
| Whether a teammate can see your monitored competitors, rank alerts, scheduled reports, notifications, editorial calendar or share links | None of those are shared. Each account sees its own. See What teammates share. |
| Whether a teammate can run a credit-metered tool | That person's own account plan and credit balance. See How credits work. |
| Whether a teammate can change the subscription, invite people or remove people | Ownership of their own account. See Workspace ownership. |
| Whether a teammate can create monitoring or alerts inside your workspace | Nobody can. Anything a member sets up is saved on their own account. See What teammates share. |
Reading the badges in Your Team#
Each member row shows a role badge and a status badge.
| Badge | Meaning |
|---|---|
Owner | Not assignable to a member. The word appears against your own workspace in Workspaces You've Joined, where your row reads owner · your own workspace. |
Editor | The member was invited as Editor. |
Author | The member was invited as Author, or with a value that resolved to Author. |
Admin, Viewer, Member | Display labels the screen can render for historical values. They carry no permissions of their own and behave as Author in Blog Studio. |
PENDING | The invite has been sent but not accepted. No access yet. |
ACTIVE | The invite has been accepted. Access is live. |
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.
See also
Was this article helpful?
Thanks — feedback noted for the docs team.