Roles and workspaces
KopiMark's permission model — workspace roles, project roles, and how owners, admins, members, and guests differ across the team and per project.
Open as Markdown Full docs bundle
Open this page in
KopiMark separates “the team” (your workspace) from “the work” (each project). Permissions exist at both layers, which makes most setups feel natural once you know what each role can touch.
The two layers
- Workspace roles control who can manage the team, billing, and shared resources (glossary, fonts, member list).
- Project roles control who can edit a specific project’s content and settings.
A teammate has a workspace role and a project role per project they can access. The project role is what gates editing in the editor itself.
Workspace roles
| Role | What they can do |
|---|---|
| Owner | Everything. Delete or rename the workspace, transfer ownership, manage billing, promote admins, manage the team. There’s at least one. |
| Admin | Invite and remove members, create projects, manage domains, manage billing. Cannot delete the workspace. |
| Member | View workspace projects they’ve been added to. Create content inside projects where their project role allows it. Edit the workspace glossary. |
| Guest | See only projects they’ve been explicitly invited to. They still count as a paid seat. Useful for freelancers and external reviewers. |
Members get implicit access to new projects in the workspace — admins and owners always see every project; members are auto-added when they open one. Guests don’t get implicit access; you must invite them per project.
Project roles
When you invite someone to a project (or they’re auto-added as a workspace member), they get a project role:
| Role | What they can do |
|---|---|
| Owner | Manage project members, change every setting, delete the project. There’s one per project — created when the project is. |
| Content manager | Manage members, change settings, delete pages, edit all content. Can’t delete the project itself. |
| Editor | Add and sync pages, edit copy and translations, comment, assign statuses. Can’t change settings or remove pages. This is the default. |
A workspace admin who only happens to be an editor on a particular project still can’t change that project’s languages — project role wins inside a project.
What this means in practice
- You hire a freelance copywriter → invite them as a workspace guest, then as an editor on the one project they’re working on.
- A localisation agency reviews translations → invite them as workspace guests with editor project access. They can’t see your other work.
- A new full-time hire → invite them as a workspace member. They’ll auto-pick-up new projects as they open them.
- A PM who only needs to read and comment → still a member or guest with editor project access. There’s no read-only project role; the editor’s status workflow is what gates “shipped vs not”.
Inviting people
Workspace invites and role changes live in Workspace Settings → People. Project invites and role changes live in the Share dialog on any project page, and also in the project’s settings.
See Invite your team for the step-by-step.
Seats and billing
- Every workspace member or guest counts as one paid seat.
- The Free plan includes 2 seats total (owner + 1 other).
- Pending invites count too — KopiMark won’t let you hold a seat open by inviting people you never plan to confirm.
See Plans and limits for the per-plan seat caps.