Stitchflow
Canva logo

Canva User Management Guide

Manual workflow

How to add, remove, and manage users with operational caveats that matter in production.

UpdatedMar 4, 2026

Summary and recommendation

Canva 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.

Canva's admin console lives at canva.com/settings/people and covers the full member lifecycle: invite, role assignment, and removal. Three fixed team roles exist - Administrator, Member, and Template Designer - with no custom role definitions available at any plan tier.

Like every app that lacks automated provisioning, the operational weight of managing Canva manually falls entirely on the administrator.

Quick facts

Admin console pathcanva.com → (team avatar, top-right) → Settings → People
Admin console URLOfficial docs
SCIM availableYes
SCIM tier requiredEnterprise
SSO prerequisiteYes

User types and roles

Role Permissions Cannot do Plan required Seat cost Watch out for
Administrator Invite and remove members, change member roles, manage billing, configure SSO/SCIM (Enterprise), manage brand kits, approve or restrict template publishing, view usage analytics Cannot be removed from the team without first transferring admin rights to another member; cannot downgrade their own role without another admin present Teams or Enterprise Counts as a paid seat on Teams ($10/user/month billed annually, 3-user minimum); custom pricing on Enterprise On Teams plan there must always be at least one Administrator; if the sole admin leaves, the team is effectively unmanaged
Member Create, edit, and share designs; access shared brand kits and folders; collaborate in real time; publish to approved channels Cannot invite or remove other members, cannot access billing, cannot configure SSO or SCIM, cannot manage brand kit settings Teams or Enterprise Counts as a paid seat; same per-seat rate as Administrator Free Canva accounts can be added to a team but must be upgraded to a paid seat before they gain full team features
Template Designer Create and publish templates to the team template library; same design capabilities as Member Cannot manage team settings, billing, or other members Teams or Enterprise Counts as a paid seat Role is additive to Member; a user can be both Member and Template Designer simultaneously
External Collaborator (Guest) View and comment on specific shared designs when invited via link or email; limited editing if granted edit access on a per-design basis Cannot access team folders, brand kits, or any design not explicitly shared with them; cannot be assigned a team role No paid seat required for the guest; sharing team must be on Teams or Enterprise Does not consume a paid seat External collaborators are not managed through the People settings panel; access is controlled per-design only

Permission model

  • Model type: role-based
  • Description: Canva uses a fixed set of team-level roles (Administrator, Member, Template Designer) applied per team. There are no custom role definitions or granular permission toggles at the team level. Folder and design sharing adds a secondary layer of object-level permissions (view, comment, edit) that any member can apply to individual assets.
  • Custom roles: No
  • Custom roles plan: Not documented
  • Granularity: Coarse: three fixed team roles plus per-object sharing permissions (view/comment/edit). No attribute-level or resource-type-level permission customization.

How to add users

  1. Log in as an Administrator and navigate to canva.com/settings/people.
  2. Click 'Invite members'.
  3. Enter one or more email addresses in the invite field (comma-separated for multiple).
  4. Select the role to assign: Member or Administrator.
  5. Click 'Send invite'. Invitees receive an email with a join link.
  6. Invitees without a Canva account are prompted to create one; existing Canva users are prompted to accept the invite.
  7. Once accepted, the user appears in the People list and a paid seat is consumed.

Required fields: Email address of invitee, Role selection (Member or Administrator)

Watch out for:

  • Invites expire after 7 days; a new invite must be sent if the link is not used in time.
  • On the Teams plan the minimum seat count is 3; adding a first or second member may trigger a billing adjustment.
  • If the invitee already has a Canva account under a different team, they must leave that team or the admin of that team must remove them before they can join.
  • Domain-based auto-join is available on Enterprise only; Teams plan requires explicit per-email invites.
  • Bulk CSV import is available on Enterprise; Teams plan does not expose a CSV upload UI in the standard admin panel.
Bulk option Availability Notes
CSV import Yes Enterprise only: canva.com/settings/people → 'Import members' → Upload CSV. Not available on Teams plan.
Domain whitelisting Yes Automatic domain-based user add
IdP provisioning Yes Enterprise (custom pricing); SCIM not available on Teams plan

How to remove or deactivate users

  • Can delete users: No
  • Delete/deactivate behavior: Canva does not offer a hard-delete of a user account from the admin console. Administrators can remove a member from the team, which revokes their access to team resources and frees the paid seat. The user's personal Canva account continues to exist. Via SCIM (Enterprise only), deprovisioning suspends the user's access but does not delete the underlying account.
  1. Log in as an Administrator and navigate to canva.com/settings/people.
  2. Locate the member using the search or scroll.
  3. Click the three-dot (…) menu next to the member's name.
  4. Select 'Remove from team'.
  5. Confirm the removal in the dialog. The member is immediately removed and loses access to team folders, brand kits, and shared designs.
Data impact Behavior
Owned records Designs created by the removed member that were stored in team folders remain in those folders and are accessible to other team members. Designs stored only in the user's personal drafts are not accessible to the team after removal.
Shared content Shared designs and folders the user was a collaborator on remain intact; the user's edit/comment access is revoked. Links shared externally by that user may still function depending on link settings.
Integrations Any personal integrations (e.g., connected social accounts) configured by the removed user are detached from the team context. Team-level integrations configured by an admin are unaffected.
License freed The paid seat is freed immediately upon removal and the team's billable seat count decreases at the next billing cycle or immediately depending on plan terms.

Watch out for:

  • Designs in the removed user's personal drafts (not in team folders) cannot be recovered by the admin; there is no admin-level content transfer tool on Teams plan.
  • On Enterprise with SCIM, deprovisioning via the IdP suspends the user but does not automatically reassign their owned team content.
  • Removing the last Administrator is blocked; another member must be promoted to Administrator first.
  • If the team drops below the 3-seat minimum on the Teams plan after removal, Canva may prompt the admin to add seats or adjust the subscription.

License and seat management

Seat type Includes Cost
Teams paid seat Full access to Canva Teams features: brand kits, premium content, team folders, collaboration, admin controls $10/user/month billed annually (minimum 3 users); monthly billing available at higher per-seat rate
Enterprise seat All Teams features plus SSO/SAML, SCIM provisioning, advanced admin controls, audit logs, dedicated support, custom contracts Custom pricing; contact Canva sales
Free seat (personal) Limited free-tier Canva features; no access to team brand kits or premium assets unless upgraded $0
  • Where to check usage: canva.com/settings/people - lists all current members and their roles. Billing seat count visible at canva.com/settings/billing.
  • How to identify unused seats: No built-in last-login or activity report is exposed in the Teams admin console. Administrators must manually review the People list and cross-reference with known active users. Enterprise customers may have access to usage analytics; specifics depend on contract.
  • Billing notes: Teams plan bills per seat with a 3-seat minimum. Adding members mid-cycle is prorated. Removing members frees the seat but refunds or credits depend on billing cycle; annual plans may not refund mid-year seat reductions. Enterprise pricing and true-up terms are negotiated per contract.

The cost of manual management

There is no last-login or inactivity report in the Teams admin console, so identifying unused seats requires manually cross-referencing the People list against known active users. Domain-based auto-join and bulk CSV import are both Enterprise-only, meaning Teams admins must issue individual per-email invites. Invites expire after 7 days, adding a re-invite loop for slow responders.

Removing a member frees the seat but does not transfer their personal-draft content - there is no admin-level content transfer tool on the Teams plan.

What IT admins are saying

The loudest recurring complaint is that SCIM provisioning is locked to Enterprise, leaving Teams subscribers - a paid tier - without automated provisioning. Admins on Teams plans report frustration with the 3-seat billing minimum, which forces small teams to carry seats they do not use.

The absence of any inactivity or last-login report is a consistent pain point for license audits. Enterprise custom pricing is opaque, making it difficult to evaluate the upgrade cost before committing to a sales conversation.

Common complaints:

  • Teams plan excluded from SCIM despite being a paid tier; SCIM requires Enterprise upgrade.
  • Enterprise custom pricing is not publicly disclosed, making cost comparison difficult.
  • No built-in admin tool to transfer or recover designs owned by a removed member on Teams plan.
  • No last-login or inactivity report in the Teams admin console, making it hard to identify unused seats.
  • Minimum 3-seat requirement on Teams plan forces small teams to pay for seats they do not need.
  • Domain-based auto-join (claimed enrollment) is Enterprise-only; Teams admins must invite each user individually.
  • Bulk CSV import for user provisioning is Enterprise-only; not available on Teams plan.
  • Invite links expire after 7 days with no automatic resend, requiring manual follow-up.

The decision

Every app in your stack that requires manual provisioning adds incremental admin burden, and Canva's Teams plan offers no shortcuts: no inactivity reports, no bulk import, no domain auto-join, and no content transfer tooling for departing members. The Teams plan is viable for small, stable headcounts where turnover is low and seat counts rarely change.

For organizations with frequent onboarding and offboarding, or those already running an identity provider, the operational overhead scales poorly. SCIM and SSO require the Enterprise tier, which carries custom pricing and a sales-negotiated contract.

Bottom line

Canva's manual administration is straightforward for small, static teams but becomes operationally expensive as headcount grows.

Every app in your stack that lacks automated provisioning adds incremental admin burden, and Canva's Teams plan offers no shortcuts: no inactivity reports, no bulk import, no domain auto-join, and no content transfer tooling for departing members.

Teams that anticipate regular user churn or already operate an IdP should factor the Enterprise upgrade - and its undisclosed pricing - into their evaluation before committing to manual workflows.

Automate Canva 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.

Every app coverage, including apps without APIs
60+ app integrations plus browser automation for apps without APIs
IT graph reconciliation across apps and your IdP
Less than a week to launch, maintained as APIs and admin consoles change
SOC 2 Type II. ~2 hours of your team's time

UpdatedMar 4, 2026

* Details sourced from official product documentation and admin references.

Keep exploring

Related apps

15Five logo

15Five

Full API + SCIM
AutomationAPI + SCIM
Last updatedFeb 2026

15Five uses a fixed role-based permission model with six predefined roles: Account Admin, HR Admin, Billing Admin, Group Admin, Manager, and Employee. No custom roles can be constructed. User management lives at Settings gear → People → Manage people p

1Password logo

1Password

Full API + SCIM
AutomationAPI + SCIM
Last updatedFeb 2026

1Password's admin console at my.1password.com covers the full user lifecycle — invitations, group assignments, vault access, suspension, and deletion — without any third-party tooling. Like every app that mixes role-based and resource-level permissions

8x8 logo

8x8

Full API + SCIM
AutomationAPI + SCIM
Last updatedFeb 2026

8x8 Admin Console supports full lifecycle user management — create, deactivate, and delete — across its X Series unified communications platform. Every app a user can access (8x8 Work desktop, mobile, web, Agent Workspace) is gated by license assignmen