Summary and recommendation
Builder.io 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.
Builder.io organizes access around Spaces, not a central organization console. Every app a team member needs access to is a separate Space, and each Space carries its own member list, role assignments, and invite flow. Admins manage membership entirely through the Builder.io dashboard at builder.io/app > Settings > Team Members.
Quick facts
| Admin console path | builder.io/app > Settings > Team Members (within a Space) |
| Admin console URL | Official docs |
| SCIM available | No |
| SCIM tier required | Enterprise |
| SSO prerequisite | No |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Admin | Full access to Space settings, content, models, integrations, billing, and member management. Can invite and remove members, change roles, and configure SSO. | Cannot manage other Spaces they are not an Admin of; cannot access organization-level billing unless also an org owner. | All plans (Free, Growth, Business, Enterprise) | Counts as a paid seat on Growth and above; Free plan limited to 1 Space with limited collaborators. | Each Space has its own Admin assignments; being Admin in one Space does not grant Admin access to other Spaces in the same organization. |
| Editor | Can create, edit, publish, and delete content entries within the Space. Can manage content models depending on Space settings. | Cannot access Space settings, billing, SSO configuration, or invite/remove team members. | All plans | Counts as a paid seat on Growth and above. | Publish permissions may be further restricted by custom publishing workflows on Business/Enterprise plans. |
| Viewer | Read-only access to content within the Space. Can preview content but cannot publish or edit. | Cannot create, edit, publish, or delete content. Cannot access settings. | All plans | Counts as a seat; exact billing treatment for Viewer-only seats not publicly documented. | Viewer role availability and seat cost distinction from Editor is not clearly differentiated in public pricing documentation. |
Permission model
- Model type: role-based
- Description: Builder.io uses a Space-scoped, role-based access model. Each user is assigned a role (Admin, Editor, or Viewer) per Space. Roles are not customizable on standard plans. Enterprise plans may offer additional access controls. There is no organization-wide unified role; permissions are managed independently per Space.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Space-level role assignment; no field-level or content-type-level permission granularity documented on standard plans.
How to add users
- Log in to builder.io/app and navigate to the target Space.
- Open Settings (gear icon) in the left sidebar.
- Select 'Team Members' or 'Members'.
- Click 'Invite Members' or 'Add Member'.
- Enter the invitee's email address.
- Select the role to assign (Admin, Editor, or Viewer).
- Click 'Send Invite'. The invitee receives an email invitation to join the Space.
Required fields: Email address, Role selection
Watch out for:
- Invitations are Space-specific; a user must be invited separately to each Space they need access to.
- The invitee must accept the email invitation before they appear as an active member.
- If the invitee does not have a Builder.io account, they will be prompted to create one upon accepting the invite.
- Seat limits apply per plan; exceeding the seat limit on Growth/Business plans may require a plan upgrade.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | Yes | Enterprise |
How to remove or deactivate users
- Can delete users: Yes
- Delete/deactivate behavior: Admins can remove (delete) a member from a Space via the Team Members settings panel. Removal revokes access to that Space immediately. There is no documented 'deactivate' state that preserves the account in a suspended form within a Space; removal is the primary offboarding action. The user's Builder.io account itself is not deleted, only their membership in the Space.
- Log in to builder.io/app and navigate to the target Space.
- Open Settings > Team Members.
- Locate the member to remove.
- Click the options menu (ellipsis or remove icon) next to the member.
- Select 'Remove' or 'Remove from Space'.
- Confirm the removal.
| Data impact | Behavior |
|---|---|
| Owned records | Content created by the removed user remains in the Space and is not deleted. Authorship metadata is preserved. |
| Shared content | Shared content and published pages remain intact and accessible to remaining members. |
| Integrations | No documented impact on Space-level integrations from removing a single member. |
| License freed | Removing a member frees the seat, which may reduce billable seat count on the next billing cycle depending on plan terms. |
Watch out for:
- Removal is per-Space; if the user is a member of multiple Spaces, they must be removed from each Space individually.
- There is no organization-wide 'deactivate all access' action documented for non-SSO plans.
- With SSO (Enterprise), deactivating the user in the IdP will prevent login but does not automatically remove them from Space member lists.
- No SCIM provisioning is available, so deprovisioning via IdP does not automatically remove users from Spaces.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Free plan seat | 1 Space, limited collaborators, limited content entries and API calls. | $0 |
| Growth plan seat | Additional collaborators, more content entries, standard support. | $19/month per Space (seat count limits not granularly published) |
| Business plan seat | More collaborators, advanced features, priority support. | $299/month per Space |
| Enterprise plan seat | Unlimited collaborators (per contract), SAML SSO, advanced security, custom SLA. | Custom pricing |
- Where to check usage: builder.io/app > Settings > Team Members (to view current members per Space); billing details in Settings > Billing.
- How to identify unused seats: No automated 'last login' or inactive-user report is documented in the admin UI. Admins must manually review the Team Members list and cross-reference with content activity.
- Billing notes: Builder.io pricing is primarily Space-based rather than strictly per-seat on lower plans. Enterprise contracts define seat/collaborator limits. Seat billing details for Growth and Business plans (e.g., per-seat overage charges) are not granularly documented in public pricing pages as of early 2025.
The cost of manual management
Because Builder.io has no SCIM support, every provisioning and deprovisioning action is a manual, per-Space operation. A user with access to five Spaces must be invited to each one individually and removed from each one individually at offboarding.
There is no organization-wide deactivation action on non-Enterprise plans, and no built-in last-login or inactive-user report exists in the admin UI, so identifying stale accounts requires manually cross-referencing the Team Members list against content activity.
The decision
Builder.io is a reasonable choice for content and CMS workflows where user counts are small and Space sprawl is limited. Teams running many Spaces or requiring automated provisioning will hit the ceiling of what manual administration can sustain. SAML SSO is available on Enterprise, but without SCIM, it only solves authentication, not lifecycle management.
Evaluate whether the per-Space admin overhead is acceptable before committing to a multi-Space rollout.
Bottom line
Builder.io's access model is Space-scoped and fully manual: every app in your environment is a discrete Space requiring its own invite and removal workflow, with no SCIM, no org-wide deactivation, and no inactive-user reporting.
For small teams with a handful of Spaces, the dashboard workflow is straightforward. For larger organizations, the operational cost of per-Space member management compounds quickly, and the absence of automated provisioning is a meaningful gap that SAML SSO alone does not close.
Automate Builder.io 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.
