Summary and recommendation
Coda user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.
Coda's admin surface lives at Workspace Settings → Members, reachable via the workspace name dropdown in the left sidebar, with a direct path at https://coda.io/admin.
The permission model runs on two tiers: workspace-level roles (Admin, Doc Maker, Editor) that govern what a user can create, and per-doc roles (Editor, Commenter, Viewer) that govern what they can do inside a specific document.
Unlike every app that offers a single unified role layer, Coda's two-tier system means a Workspace Admin does not automatically gain access to doc content they have not been explicitly shared on. Custom roles do not exist, and section- or row-level permissions are not natively available.
Quick facts
| Admin console path | Workspace Settings → Members (accessed via the workspace name dropdown in the left sidebar) |
| Admin console URL | Official docs |
| SCIM available | Yes |
| SCIM tier required | Enterprise |
| SSO prerequisite | Yes |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Workspace Admin | Full control over workspace settings, member management, billing, SSO/SCIM configuration, and doc visibility. Can add/remove members, change roles, and access the Admin Panel. | Cannot access doc content they have not been explicitly shared on unless they are also a Doc Maker or Editor on that doc. | All paid plans; Admin Panel features vary by plan (Enterprise unlocks SSO, SCIM, advanced controls) | Billed as a Doc Maker seat if they create or copy docs; otherwise free as an Editor | Admin role is workspace-level only; it does not automatically grant access to all docs in the workspace. |
| Doc Maker | Can create new docs, copy docs, and publish docs. Full editing rights within docs they have access to. | Cannot manage workspace members or billing unless also assigned Admin role. | Free (limited), Pro, Team, or Enterprise | Paid seat - the only role that incurs a per-seat charge. Pro: $10/month (annual), Team: $30/month (annual), Enterprise: custom. | Only Doc Makers are billed. Assigning someone as a Doc Maker immediately adds a billable seat. Downgrading to Editor removes the charge. |
| Editor | Can edit, comment on, and view docs they are shared on. Cannot create new docs or copy docs. | Cannot create docs, copy docs, or access workspace admin settings. | All plans including Free | Free - Editors do not consume a paid seat regardless of plan. | Editors can be added in unlimited numbers at no cost, but they cannot initiate new docs. This is a core part of Coda's Maker Billing model. |
| Commenter | Can view docs and leave comments. Cannot edit doc content. | Cannot edit content, create docs, or access admin settings. | All plans | Free - no seat charge. | Commenters must be explicitly added to a doc; workspace membership alone does not grant comment access to all docs. |
| Viewer | Read-only access to docs they are shared on. | Cannot edit, comment (unless doc settings allow), create, or manage anything. | All plans | Free - no seat charge. | Public docs can be viewed without a Coda account; internal docs require workspace membership or explicit share. |
Permission model
- Model type: role-based
- Description: Coda uses a two-tier role system: workspace-level roles (Admin, Doc Maker, Editor) and doc-level roles (Editor, Commenter, Viewer). Workspace roles determine what a user can create; doc-level roles determine what they can do within a specific doc. Doc owners can share individual docs with any role independently of workspace role.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Workspace-level (Admin/Doc Maker/Editor) and per-doc (Editor/Commenter/Viewer). No custom role creation. Section- or row-level permissions are not available natively; doc builders can simulate restrictions using Coda formulas and hiding sections.
How to add users
- Open the workspace by clicking the workspace name in the top-left sidebar.
- Navigate to Settings → Members.
- Click 'Invite members'.
- Enter the invitee's email address(es).
- Select the workspace role: Doc Maker or Editor (Admin can be assigned separately).
- Click 'Send invite'. The invitee receives an email invitation to join the workspace.
- Alternatively, share a specific doc directly via the Share button in the doc header, which adds the user as a doc-level collaborator without necessarily adding them to the workspace member list.
Required fields: Email address of the invitee, Workspace role selection (Doc Maker or Editor)
Watch out for:
- Inviting someone as a Doc Maker immediately creates a billable seat; confirm role before sending.
- Users invited directly to a doc (not via workspace invite) may appear as guests and not in the main Members list.
- On the Free plan, the number of Doc Makers is limited; exceeding the limit requires a plan upgrade.
- Invitations expire if not accepted; admins must resend if the link lapses.
- SSO-enforced workspaces (Enterprise) may require users to authenticate via the configured IdP before they can accept an invite.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | Yes | Automatic domain-based user add |
| IdP provisioning | Yes | Enterprise |
How to remove or deactivate users
- Can delete users: Verify in tenant
- Delete/deactivate behavior: This app exposes delete operations in its API documentation, but the admin-console path may present removal as deactivation, archiving, or deletion depending on tenant configuration. Confirm whether the UI action is reversible before treating removal as recoverable.
- Go to workspace Settings → Members.
- Locate the member to remove using search or scrolling.
- Click the '...' (more options) menu next to the member's name.
- Select 'Remove from workspace'.
- Confirm the removal in the dialog. The user loses access immediately.
| Data impact | Behavior |
|---|---|
| Owned records | Docs created by the removed user remain in the workspace and are still accessible to anyone they were shared with. Ownership of those docs does not automatically transfer; an admin must manually reassign or move docs. |
| Shared content | Shared docs the removed user had access to remain intact for other collaborators. The removed user loses access but the docs themselves are unaffected. |
| Integrations | Any Packs or integrations the removed user authenticated (e.g., personal OAuth connections within docs) may stop functioning for automations that relied on their credentials. Admins should audit and re-authenticate affected connections. |
| License freed | Removing a Doc Maker frees the paid seat immediately. The seat count and billing adjusts at the next billing cycle or immediately depending on plan terms. |
Watch out for:
- Docs owned by the removed user do not automatically transfer to another owner; admins must manually locate and reassign or copy those docs.
- If the removed user was the sole owner of critical docs, those docs may become difficult to manage without explicit ownership transfer before removal.
- Automations or scheduled tasks that ran under the removed user's identity may fail silently after removal.
- On Enterprise with SCIM, deprovisioning via the IdP (Okta, Entra ID) is the recommended method and will automatically remove the user from the workspace.
- Removing a user does not delete their Coda account; they can still log in to Coda and access any other workspaces they belong to.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Doc Maker seat | Ability to create, copy, and publish docs. Full editing rights. Required for anyone who needs to initiate new documents. | Pro: $10/Doc Maker/month (annual) or $12/month. Team: $30/Doc Maker/month (annual) or $36/month. Enterprise: custom pricing. |
| Editor (free collaborator) | Edit, comment, and view access to docs they are shared on. Cannot create new docs. | $0 - unlimited Editors at no charge on all plans. |
- Where to check usage: Workspace Settings → Members (shows all members and their roles). Workspace Settings → Billing shows current Doc Maker seat count and billing details.
- How to identify unused seats: Admins can review the Members list in Settings and sort or filter by role. Coda does not natively display last-login or last-active timestamps in the admin UI as of early 2025; identifying inactive Doc Makers requires manual review or cross-referencing with IdP activity logs (Enterprise). Downgrading inactive Doc Makers to Editor removes the seat charge.
- Billing notes: Coda uses 'Maker Billing' - only Doc Makers are charged. Editors, Commenters, and Viewers are always free regardless of count. Annual billing provides approximately 15% discount versus monthly. Seat count changes mid-cycle are prorated. Enterprise pricing is negotiated directly with Coda sales. Free plan includes limited Doc Maker seats and 1GB storage per doc.
The cost of manual management
Coda's 'Maker Billing' model means only Doc Makers are charged - Editors, Commenters, and Viewers are free regardless of count. Assigning someone as a Doc Maker creates a billable seat immediately; downgrading them to Editor removes the charge.
The admin panel does not expose last-login or last-active timestamps as of early 2025, so identifying inactive Doc Maker seats requires manual review of the Members list or cross-referencing IdP activity logs on Enterprise. Without that signal, stale Doc Maker seats accumulate silently and inflate the bill over time.
What IT admins are saying
The most consistent friction reported by Coda admins centers on three areas. First, SSO and SCIM are gated to Enterprise, locking smaller teams into fully manual provisioning workflows.
Second, SAML must be fully configured before SCIM can be enabled - a sequencing requirement that adds setup complexity and is easy to miss.
Third, only one SCIM token is valid at a time; regenerating it immediately invalidates the previous token, which breaks any active IdP sync until the new token is updated.
Doc ownership is a separate pain point: removing a member does not auto-transfer their docs, and automations tied to a removed user's credentials fail silently with no admin alert.
Common complaints:
- Enterprise-only SSO/SCIM locks smaller teams out of automated provisioning.
- SAML must be fully configured before SCIM can be enabled, adding setup complexity.
- Only one SCIM token is valid at a time, requiring token rotation coordination.
- No native last-login or activity reporting in the admin panel makes it hard to identify inactive Doc Maker seats.
- Doc ownership does not auto-transfer when a member is removed, creating orphaned doc management burden.
- Automations tied to a removed user's OAuth credentials break silently with no admin alert.
- No CSV bulk import for adding members; large team onboarding must use SCIM (Enterprise) or manual invites.
- The distinction between workspace membership and doc-level sharing confuses new admins - users invited to a doc may not appear in the workspace Members list.
- No custom roles; teams needing granular permission tiers must work around limitations using doc-level sharing and formula-based restrictions.
The decision
Manual management is viable for small workspaces where Doc Maker seat counts are low and member churn is infrequent.
The risk scales with team size: without last-login data in the UI, auditing who actually needs a Doc Maker seat requires external effort, and the problem compounds when every app in the stack demands its own separate access review.
For any org running Okta or Entra ID on Enterprise, SCIM provisioning eliminates the manual invite and removal steps and is the recommended path. Teams below Enterprise tier have no automated option and should plan for periodic manual audits to control seat costs.
Bottom line
Coda's manual admin workflow is functional but carries real operational cost at scale.
The Maker Billing model rewards careful role assignment - every unnecessary Doc Maker seat is a recurring charge - but the admin panel provides no native activity data to make that judgment easy.
Doc ownership gaps and silent automation failures after member removal are the sharpest edges for teams managing frequent offboarding.
Enterprise teams should prioritize SCIM setup over manual workflows as soon as SSO is in place; everyone else should build a recurring audit habit into their access review process.
Automate Coda workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
