Stitchflow
Mailchimp logo

Mailchimp User Management Guide

Manual workflow

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

UpdatedMar 6, 2026

Summary and recommendation

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

Mailchimp uses a fixed five-role model - Owner, Admin, Manager, Author, and Viewer - with no custom roles or granular permission toggles on any plan. Permissions are bundled at the role level only; there is no per-audience, per-campaign, or per-feature scoping available.

Every app in a well-governed stack benefits from automated provisioning, but multi-user access in Mailchimp requires upgrading from the Free plan, which is restricted to a single Owner.

Quick facts

Admin console pathAccount menu (top-right avatar) → Account & billing → Settings → Users
Admin console URLOfficial docs
SCIM availableNo
SCIM tier requiredPremium or Enterprise
SSO prerequisiteNo

User types and roles

Role Permissions Cannot do Plan required Seat cost Watch out for
Owner Full account access: billing, plan changes, account deletion, all settings, all content, all audiences. Only role that can transfer ownership or close the account. Cannot be removed by other users; only one Owner per account. All plans (exactly one per account) Included in plan base cost Ownership transfer requires the current Owner to initiate it. If the Owner leaves the organization without transferring, account recovery requires contacting Mailchimp support.
Admin Nearly identical to Owner: manage users, billing, audiences, campaigns, automations, templates, integrations, and account settings. Cannot delete the account or transfer ownership. Cannot close the account, cannot transfer ownership, cannot remove the Owner. Essentials, Standard, or Premium (multi-user seats required; Free plan is single-user only) Counts as a paid user seat on multi-user plans Admins can invite and remove other Admins and lower roles, which creates a risk of accidental privilege escalation if not monitored.
Manager Can create and send campaigns, manage audiences (add/edit/archive contacts), view reports, manage automations and templates. Cannot access billing or account settings. Cannot access billing, cannot manage users, cannot change account settings, cannot view or edit integrations. Essentials, Standard, or Premium Counts as a paid user seat Managers have broad content and audience access; they can export contact lists, which is a data-governance consideration.
Author Can create and edit campaigns and templates, but cannot send campaigns or publish automations without Admin/Manager approval. Can view reports. Cannot send campaigns, cannot manage audiences or contacts, cannot access billing or user settings. Essentials, Standard, or Premium Counts as a paid user seat Author role is designed for content creators who should not have send authority; useful for agencies or contractors.
Viewer Read-only access to campaigns, reports, and audience data. Cannot create, edit, or send anything. Cannot create or edit any content, cannot manage contacts, cannot access billing or settings. Essentials, Standard, or Premium Counts as a paid user seat Viewers can still see audience/contact data in reports, which may be a compliance concern depending on data sensitivity.

Permission model

  • Model type: role-based
  • Description: Mailchimp uses a fixed set of five predefined roles (Owner, Admin, Manager, Author, Viewer). Permissions are bundled per role and cannot be individually customized. There are no custom roles or granular permission toggles available on any plan.
  • Custom roles: No
  • Custom roles plan: Not documented
  • Granularity: Role-level only; no per-audience, per-campaign, or per-feature permission scoping available within a role.

How to add users

  1. Log in as Owner or Admin.
  2. Click the account avatar/name in the top-right corner.
  3. Select 'Account & billing' from the dropdown.
  4. Navigate to the 'Settings' tab, then click 'Users'.
  5. Click the 'Invite A User' button.
  6. Enter the invitee's email address.
  7. Select the desired role (Admin, Manager, Author, or Viewer) from the role dropdown.
  8. Click 'Send Invite'.
  9. The invitee receives an email invitation and must accept it to gain access. If they do not have a Mailchimp account, they will be prompted to create one.

Required fields: Email address of the invitee, Role selection

Watch out for:

  • Free plan accounts are single-user only; multi-user access requires upgrading to Essentials or higher.
  • The invitee must accept the email invitation before they appear as an active user; pending invites are shown separately.
  • Invitations expire if not accepted; a new invite must be sent if the original expires.
  • Each additional user seat on paid plans may increase the monthly cost depending on the plan tier and seat count.
  • The invited user's Mailchimp account (if they already have one) will be linked; they will see this account in their account switcher.
Bulk option Availability Notes
CSV import No Not documented
Domain whitelisting No Automatic domain-based user add
IdP provisioning Yes Premium (via third-party SSO/SCIM integrations with Okta, OneLogin, or miniOrange; no native SCIM provisioning)

How to remove or deactivate users

  • Can delete users: Yes
  • Delete/deactivate behavior: Mailchimp allows Owners and Admins to remove (revoke access for) other users from the account. Removal is immediate and revokes all access to the account. The removed user's Mailchimp account itself is not deleted-only their access to this specific account is revoked. There is no 'deactivate/suspend' state; the only options are active access or full removal.
  1. Log in as Owner or Admin.
  2. Click the account avatar/name in the top-right corner.
  3. Select 'Account & billing'.
  4. Go to 'Settings' → 'Users'.
  5. Locate the user to remove in the active users list.
  6. Click the trash/remove icon or 'Remove' option next to that user.
  7. Confirm the removal in the confirmation dialog.
Data impact Behavior
Owned records Campaigns, templates, and automations created by the removed user remain in the account and are accessible to remaining Admins and the Owner. No content is deleted upon user removal.
Shared content All shared audiences, campaigns, and reports remain intact and accessible to other users with appropriate roles.
Integrations API keys and OAuth connections created by the removed user may remain active and should be manually audited and revoked separately via Account → Extras → API keys.
License freed Removing a user frees up that user seat, which may reduce the billed seat count on the next billing cycle depending on the plan.

Watch out for:

  • The Owner cannot be removed by anyone other than themselves (via ownership transfer). If an Owner leaves without transferring, account recovery requires Mailchimp support intervention.
  • API keys created by a removed user are NOT automatically revoked. Admins must manually review and delete orphaned API keys under Account → Extras → API keys.
  • There is no audit log of user actions available on lower-tier plans, making it difficult to review what a removed user did before removal.
  • Pending invitations for a removed user should also be cancelled manually if the invite was sent in error.
  • Admins cannot remove other Admins on some account configurations; only the Owner can remove Admin-level users in certain scenarios-verify current behavior in the Users settings panel.

License and seat management

Seat type Includes Cost
Single user (Free plan) One user only (the Owner). No additional seats available. $0/month
Multi-user seats (Essentials) Up to 3 users (Owner + 2 additional seats) included in base plan price. Starting at $13/month for 500 contacts; additional seats may incur extra cost
Multi-user seats (Standard) Up to 5 users included in base plan price. Starting at $20/month for 500 contacts
Multi-user seats (Premium) Unlimited users included. Starting at $350/month for 10,000 contacts
  • Where to check usage: Account avatar → Account & billing → Settings → Users (shows all active users and pending invitations)
  • How to identify unused seats: No built-in last-login or activity timestamp is displayed in the Users panel. Admins must manually review the user list and cross-reference with known team members to identify potentially unused seats. No automated idle-user detection is available.
  • Billing notes: Mailchimp's pricing is primarily contact-count-based, not seat-based. Additional user seats on Essentials and Standard plans may add incremental cost; Premium includes unlimited seats. Removing a user frees the seat but billing adjustments depend on the plan's seat tier thresholds. Always verify current seat pricing on the Mailchimp pricing page as it changes with contact tier.

The cost of manual management

Without automated provisioning, offboarding requires manual invite-and-remove cycles through the Users settings panel. API keys created by a removed user are not automatically revoked, requiring a separate manual audit under Account → Extras → API Keys.

There is no last-login or activity timestamp in the Users panel, so identifying stale seats means cross-referencing the user list against known team members by hand.

What IT admins are saying

The most consistent friction reported by Mailchimp administrators centers on three gaps. First, no native SCIM endpoint exists - automated provisioning depends entirely on third-party IdP connectors (Okta, OneLogin, miniOrange), which add integration cost and maintenance overhead.

Second, the absence of audit logs on Essentials and Standard plans makes it difficult to reconstruct what a removed user accessed or changed.

Third, the five-role model is widely considered too coarse for larger teams: there is no way to restrict a Manager from exporting contact lists, which is a data-governance concern on plans below Premium.

Common complaints:

  • No native SCIM support; automated provisioning requires third-party integrations (Okta, OneLogin, miniOrange) which add cost and complexity.
  • No last-login or activity data visible in the Users panel, making it impossible to identify inactive users without manual tracking.
  • API keys created by removed users are not automatically revoked, creating a security gap that requires manual cleanup.
  • No custom roles or granular permissions; the fixed five-role model is considered too coarse for larger teams with complex access requirements.
  • Free plan restricts accounts to a single user, forcing upgrades even for small teams needing basic collaboration.
  • No audit log of user actions on Essentials or Standard plans, limiting accountability and compliance capabilities.
  • Ownership transfer process is cumbersome and requires the departing Owner to be available; no admin-override path without contacting support.
  • Pending invitations do not auto-expire with a clear notification, leading to forgotten open invitations.
  • Limited native enterprise identity features despite Intuit acquisition; SSO is only available via third-party providers.

The decision

Every app in a compliance-conscious stack should support automated deprovisioning; Mailchimp currently requires third-party tooling to reach that baseline. Teams that need audit trails or scoped audience-level permissions will hit hard limits on every plan below Premium, and even Premium does not offer native SCIM.

If your organization already runs an IdP like Okta or OneLogin, evaluate whether the connector overhead is justified before committing to a provisioning workflow.

Bottom line

Mailchimp's user management is straightforward for small teams but shows meaningful gaps at scale: no native SCIM, no last-login visibility, no audit logs below Premium, and orphaned API keys on offboarding that require manual cleanup.

Every app in a well-governed stack should have automated deprovisioning; Mailchimp currently requires third-party tooling to get there. Teams with strict compliance or access-control requirements should weigh those gaps against the platform's marketing capabilities before expanding seat count.

Automate Mailchimp 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 6, 2026

* Details sourced from official product documentation and admin references.

Keep exploring

Related apps

Abnormal Security logo

Abnormal Security

API Only
AutomationAPI only
Last updatedMar 2026

Abnormal Security is an enterprise email security platform focused on detecting and investigating threats such as phishing, account takeover (ATO), and vendor email compromise. It does not support SCIM provisioning, which means every app in your stack

ActiveCampaign logo

ActiveCampaign

API Only
AutomationAPI only
Last updatedFeb 2026

ActiveCampaign uses a group-based permission model: every user belongs to exactly one group, and all feature-area access (Contacts, Campaigns, Automations, Deals, Reports, Templates) is configured at the group level, not per individual. The default Adm

ADP logo

ADP

API Only
AutomationAPI only
Last updatedFeb 2026

ADP Workforce Now is a mid-market to enterprise HCM platform that serves as the HR source of record for employee data — payroll, benefits, time, and talent. User access is governed by a hybrid permission model: predefined security roles (Security Maste