Roles & permissions
Bifrost separates company-level administration from table-level data roles, so you can give each person exactly the access their job needs — no more.
Company administrator
The person who creates a company becomes its administrator; they can promote others. Administrators manage users and invitations, create departments, create tables, and assign the table roles below. Being an administrator does not silently make you a data approver everywhere — data duties stay explicit.
Table roles
Every table assigns its own roles. One person can hold different roles on different tables.
| Role | Can view data | Can enter data | Can approve | Typical use |
|---|---|---|---|---|
| Viewer | Yes | No | No | Management, analysts, report readers |
| Editor | Yes | Yes | No | The people producing the numbers |
| Approver | Yes | No | Yes | Controllers, team leads signing off |
| Editor + approver | Yes | Yes | Yes* | Small teams where one person does both |
*Four-eyes principle: nobody can approve their own submission — not even
administrators or combined editor-approvers. A row always needs a second person to sign it off.
What this means in practice
- Someone with no role on a table doesn't see it at all — in the app or through the API.
- Editors see their rejected rows with the rejection reason, fix them, and resubmit.
- Approvers see a queue of pending rows on their dashboard for the tables they approve.
- The API enforces exactly the same rules as the web app — a token can never do more than the person it belongs to.
Managing roles
Administrators assign roles when inviting a colleague and can change them any time under Manage permissions on the company page. Reassignments take effect immediately.