Stitchflow
Mural logo

Mural User Management Guide

Manual workflow

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

UpdatedMar 11, 2026

Summary and recommendation

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

Mural is a visual collaboration platform with a two-level permission model: Company Admin governs the entire organization, while Workspace Admins operate within individual workspaces. These roles are fixed - there are no custom role definitions on any plan.

Every app in this category makes a similar trade-off, but Mural's separation of company-level and workspace-level admin is a common source of confusion when managing multiple workspaces.

SSO and SCIM provisioning are locked to the Enterprise tier, which requires custom pricing. Business-tier customers ($17.99/user/month) do not have access to automated provisioning and must manage members entirely through the admin console.

Quick facts

Admin console pathSettings → Members (Company-level: app.mural.co → Company Settings → Members)
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
Company Admin Full control over company settings, billing, all workspaces, member management, SSO/SCIM configuration, and security policies. Cannot act as a regular collaborator without also holding a Member seat in a workspace. All paid plans; at least one Company Admin required. Counts as a paid Member seat. Company Admin role is separate from Workspace Admin; a Company Admin is not automatically a Workspace Admin in every workspace.
Workspace Admin Manage members within a specific workspace, create and delete murals, manage workspace settings and templates. Cannot access company-level billing or SSO settings; cannot manage other workspaces they are not admin of. All plans. Counts as a paid Member seat. Workspace Admin scope is limited to the workspace they administer; multiple workspaces require separate admin assignments.
Member Create murals, collaborate in workspaces they belong to, invite guests (if permitted by admin), access shared content. Cannot access admin settings, billing, or manage other users. All plans. Consumes one paid seat on Team+, Business, or Enterprise plans. On the Free plan, member count is limited; upgrading is required to add more paid members.
Guest Access specific murals or rooms they are explicitly invited to; can edit if given edit permissions. Cannot create murals independently, cannot access workspace-level content beyond their invitation scope. Business and Enterprise plans allow guests; limited or unavailable on lower tiers. Guests do not consume a full paid Member seat on Business/Enterprise; guest seat limits vary by plan. Guest access scope is tightly controlled; guests invited to a room see only that room's murals.
Visitor View-only access to a mural via a shared link; no account required. Cannot edit, comment (unless anonymous commenting enabled), or access any other workspace content. Available on all plans via public/private link sharing. No seat consumed. Visitor access is link-based and not tracked as a named user in member management.

Permission model

  • Model type: role-based
  • Description: Mural uses a fixed set of predefined roles at two levels: company-level (Company Admin) and workspace-level (Workspace Admin, Member, Guest). Permissions are tied to these roles and are not individually configurable. There are no custom role definitions available on any plan.
  • Custom roles: No
  • Custom roles plan: Not documented
  • Granularity: Role-level only; no per-feature or per-object permission overrides beyond role assignment and mural-level share settings (view vs. edit).

How to add users

  1. Log in as Company Admin or Workspace Admin.
  2. Navigate to app.mural.co → Company Settings → Members (for company-level) or open the workspace and go to Workspace Settings → Members.
  3. Click 'Invite members'.
  4. Enter one or more email addresses in the invitation field.
  5. Select the role to assign (Member or Workspace Admin).
  6. Click 'Send invite'. Invitees receive an email to accept and join.

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

Watch out for:

  • Invitees must accept the email invitation before they appear as active members; pending invites occupy a seat on some plans.
  • Inviting a user who already has a Mural account under a different company will prompt them to switch or create a new account.
  • Domain-based auto-join (if configured) allows users with a verified domain to join without an explicit invite, which can cause unexpected seat consumption.
  • Workspace Admins can only invite users to their specific workspace; only Company Admins can invite at the company level.
Bulk option Availability Notes
CSV import Unknown Not documented
Domain whitelisting Yes Automatic domain-based user add
IdP provisioning Yes Enterprise

How to remove or deactivate users

  • Can delete users: No
  • Delete/deactivate behavior: Mural does not offer a permanent account deletion option from the admin console. Admins can remove (deactivate) a member from the company or workspace, which revokes access. The user's Mural account itself is not deleted; their content remains in the workspace. Full account deletion requires the user to submit a request or is handled via SCIM deprovisioning on Enterprise.
  1. Log in as Company Admin.
  2. Navigate to Company Settings → Members.
  3. Locate the member using search or the member list.
  4. Click the three-dot (⋯) menu next to the member's name.
  5. Select 'Remove from company' (or 'Remove from workspace' if acting at workspace level).
  6. Confirm the removal in the dialog.
Data impact Behavior
Owned records Murals created by the removed user remain in the workspace and are not deleted. Ownership is retained under the original creator's name but the content stays accessible to workspace members.
Shared content Shared murals and rooms the user was part of remain intact and accessible to other collaborators.
Integrations Any personal integrations or tokens the user set up (e.g., Slack, Microsoft Teams connections) may become inactive for that user but do not affect workspace-level integrations.
License freed Removing a member frees their paid seat, which becomes available for reassignment on the next billing cycle or immediately depending on plan terms.

Watch out for:

  • Removed users lose access immediately upon removal, but their content is not reassigned automatically - admins must manually transfer ownership if needed.
  • On Enterprise with SCIM, deprovisioning via the IdP automatically removes the user from Mural; manual removal in the admin console is redundant but possible.
  • If a removed user is re-invited, they rejoin as a new member and may lose previous workspace-specific settings.
  • Removing a Workspace Admin does not remove them from the company; they retain Member-level access unless also removed at the company level.

License and seat management

Seat type Includes Cost
Member seat Full create/edit access to murals within assigned workspaces; counts toward paid seat total. Team+: $9.99/user/month; Business: $17.99/user/month; Enterprise: custom pricing.
Guest seat Access limited to specific rooms or murals; does not consume a full Member seat on Business/Enterprise plans. Included within plan limits on Business and Enterprise; not available as a standalone purchasable seat.
Visitor (anonymous) View-only link-based access; no account or seat required. Free; no seat consumed.
  • Where to check usage: Company Settings → Members → view active member count and pending invites; billing seat count shown in Company Settings → Billing.
  • How to identify unused seats: Mural does not provide a native last-login or activity report in the standard admin console. Admins must manually review the member list for inactive users. Enterprise plans with SCIM/IdP integration can cross-reference IdP activity logs to identify unused seats.
  • Billing notes: Seats are billed per active Member on a monthly or annual basis. Removing a member mid-cycle does not typically result in a prorated refund on monthly plans; annual plans may have different terms. Pending (unaccepted) invitations may or may not count against seat limits depending on plan configuration - verify with Mural billing support.

The cost of manual management

Mural provides no native last-login or activity reporting in the standard admin console. Identifying inactive seats requires manually reviewing the member list - there is no exportable activity log on non-Enterprise plans.

Removing a member revokes access immediately but does not reassign their murals. Ownership transfer is a separate manual step that admins must handle individually. Pending invitations may consume seats before the invitee accepts, depending on plan configuration - verify behavior with Mural billing support before bulk-inviting.

Every app with a guest model introduces edge cases, and Mural is no exception: guests require Business or Enterprise to function properly, and their visibility in member lists depends on workspace settings.

What IT admins are saying

Recurring complaints from Mural admins center on three areas. First, the absence of built-in activity reporting makes license hygiene difficult at scale.

Second, the Company Admin vs. Workspace Admin scope distinction causes operational errors, particularly in organizations running many workspaces.

Third, SCIM being gated to Enterprise is a consistent frustration for Business-tier customers who want automated deprovisioning without committing to custom pricing.

Complaints about content orphaning after member removal are also common - murals owned by a removed user remain in the workspace with no automatic reassignment.

Common complaints:

  • Admins report no built-in activity or last-login reporting, making it difficult to identify inactive seats without manual review.
  • Users note that removing a member does not reassign their murals, requiring manual ownership transfer.
  • Complaints about guest seat limitations on lower-tier plans, with guests requiring Business or Enterprise to function properly.
  • Some admins report confusion between Company Admin and Workspace Admin scopes, particularly when managing multiple workspaces.
  • Users report that pending invitations can consume seats before the invitee accepts, leading to unexpected billing.
  • SCIM provisioning and SSO are locked to Enterprise, which is a common complaint from Business-tier customers who want automated provisioning.

The decision

Manual management in Mural is workable for small teams but becomes operationally expensive as headcount grows. The lack of activity data means seat audits require cross-referencing external sources. If your organization is on Business tier and needs automated provisioning, the only path is upgrading to Enterprise.

For teams already on Enterprise with an IdP configured, SCIM via Okta or Microsoft Entra ID handles provisioning and deprovisioning reliably. The manual console remains useful for one-off changes and workspace-level adjustments that fall outside IdP-managed flows.

Bottom line

Mural's manual user management is straightforward for small teams but lacks the reporting and automation features needed to run a clean identity posture at scale. No activity logs, no bulk operations, and no custom roles mean that growing organizations will hit friction quickly.

SCIM and SSO are available, but only on Enterprise - teams on lower tiers should plan for manual overhead and build compensating processes around seat audits and offboarding until they reach that tier.

Automate Mural 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 11, 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