Roles — admin, editor, viewer

Three roles, three permission levels. Admin administers, editor edits, viewer watches. Here's what changes and how to pick the right role for each person.

Updated on Apr 25, 20264 min readCollaboration

Every workspace member has one of three roles: admin, editor, viewer. They define what they can do in the workspace.

ActionAdminEditorViewer
See expenses, Centers, people
See calendar, totals
Add an expense
Edit / delete an expense
Mark as paid
Create / edit a Cost Center
Add / edit people
Invite new members
Change another member's role
Remove a member
Rename the workspace
Delete the workspace

Three logics behind:

When to pick admin

Remember admins can do destructive things like delete the workspace or remove other admins. Give the role only to people you trust at that level.

When to pick editor

The default role for most cohabiting family members:

Editor can do the daily work (add bills, mark as paid, edit amounts) but doesn't touch the structure.

When to pick viewer

Rarer but useful cases:

Viewer can change nothing, not even the status of an expense. It's read-only.

The last admin can't be stripped

A workspace must have at least one admin. If you're the only admin:

This avoids leaving an orphan workspace with nobody to administer it.

Changing a member's role

From Settings → Members, click the member, pick the new role, save. The change is immediate.

Common example: you gave the partner editor, after a few months you promote them to admin (because they now also handle invites and Centers). One click.

What does NOT change between roles

All roles see the same things. There are no "admin-only expenses", no "private Centers". A workspace is completely transparent inside — what changes is who can modify.

If you want privacy between people, the answer isn't the role — it's creating two separate workspaces (e.g. one personal, one family).

Security: what the role is NOT

Roles are application authorization, not data security. A viewer can still see everything — it's not a "limited view permission".

If you have data some members shouldn't see, viewer isn't enough: you have to separate into different workspaces.

Related articles

Useful actions