Atlassian Trello User Management Guide

• Model type: role-based
• Description: Trello uses a layered role-based permission model. At the Enterprise level, Enterprise Admins govern organization-wide policies. At the Workspace level, Workspace Admins and Normal members have defined capabilities. At the board level, board Admins and Members have distinct permissions. Observer is an Enterprise-only read-only board role. There are no custom roles; permissions are fixed per role type.
• Custom roles: No
• Custom roles plan: Not documented
• Granularity: Three layers: Enterprise-level, Workspace-level, and Board-level. Within each layer, roles are predefined with fixed permission sets. No granular permission toggling per user.

1. Navigate to your Workspace at trello.com.
2. Click on the Workspace name in the left sidebar to open Workspace settings.
3. Select 'Members' from the Workspace menu.
4. Click 'Invite Workspace Members'.
5. Enter the email address(es) of the user(s) to invite.
6. Select the role (Admin or Normal member) for the invitee.
7. Click 'Send Invitation'. The invitee receives an email and must accept to join.
8. For Enterprise: Enterprise Admins can also add members via the Enterprise Admin Dashboard at trello.com/enterprise under the 'Members' tab.

Required fields: Email address of the invitee

Watch out for:

• Invited users must accept the email invitation before they appear as active members; pending invitations still count toward billing on some plans.
• On the Free plan, Workspaces are limited to 10 collaborators per board.
• Enterprise Admins can restrict who can invite members (Admins only vs. all members) at the Workspace level.
• If SSO is enforced on Enterprise, new users must authenticate via the configured IdP before accessing Trello.
• Adding a guest to a second board on Standard/Premium automatically converts them to a full billable member.

• Can delete users: No
• Delete/deactivate behavior: Trello does not offer a permanent account deletion option for Enterprise admins. Enterprise Admins can deactivate a member, which revokes their access to all Enterprise Workspaces and boards and frees the license seat. The user's account and their created content (cards, boards, comments) are retained. Deactivated users can be reactivated. Full account deletion must be initiated by the user themselves through Atlassian account settings.

1. Navigate to the Enterprise Admin Dashboard at trello.com/enterprise.
2. Click 'Members' in the left navigation.
3. Search for the member to deactivate.
4. Click on the member's name to open their profile.
5. Click 'Deactivate Member'.
6. Confirm the deactivation in the dialog. The member is immediately removed from all Enterprise Workspaces and boards and loses access.

Watch out for:

• Deactivation is Enterprise-only as a centralized admin action. On Standard/Premium, Workspace Admins can only remove members from their specific Workspace, not deactivate them organization-wide.
• Removing a member from a Workspace on non-Enterprise plans does not prevent them from being re-invited or accessing other Workspaces.
• Boards set to 'Public' visibility remain accessible to deactivated users if they have the direct URL, since public boards do not require authentication.
• If the deactivated user was the sole Admin of a board, another Enterprise Admin must manually assign a new board Admin.
• SCIM-based deactivation via Atlassian Guard will deactivate the user's entire Atlassian account, not just Trello access.

• Where to check usage: Enterprise Admin Dashboard (trello.com/enterprise) → Members tab shows all active, deactivated, and pending members with last activity data. Workspace Admins can view member counts under Workspace Settings → Members.
• How to identify unused seats: Enterprise Admin Dashboard provides last activity timestamps per member. Admins can filter or sort by last active date to identify inactive users. No automated idle-user report; manual review of last activity column is required.
• Billing notes: All active Workspace members (including guests added to multiple boards) consume a billable seat. Pending invitations may count toward billing depending on plan. Enterprise plan requires a 50-user minimum and is billed annually. Trello Enterprise includes Atlassian Guard Standard (required for SCIM). Nonprofits and educational institutions qualify for 75% discount on Standard/Premium and 50% on Enterprise. Billing is managed through Atlassian's billing portal, not within Trello directly.

Without automated provisioning, every app in your stack demands individual admin attention for onboarding and offboarding. In Trello specifically, removing a departing user requires a Workspace Admin to manually remove them from each Workspace they belong to-and on non-Enterprise plans, that action does not prevent the user from being re-invited or accessing other Workspaces.

Board-level access compounds the problem: removing a member from a Workspace does not automatically remove them from boards they were added to directly. Each board requires a separate removal step. On Standard and Premium plans there is no centralized deactivation; only Enterprise provides a single action that revokes access across all Workspaces simultaneously.

Identifying unused seats also requires manual effort. The Enterprise Admin Dashboard surfaces last-activity timestamps per member, but there is no automated idle-user report-admins must sort and review the last-activity column by hand.

Admins consistently flag that SCIM provisioning is not intuitive because it lives inside Atlassian Guard rather than Trello itself, making the dependency non-obvious during initial Enterprise setup.

The lack of native IdP group-to-Workspace sync is a recurring friction point: group membership must be managed manually or through Guard's limited mapping capabilities.

A frequently cited surprise is the blast radius of SCIM deactivation-disabling a user via Guard deactivates their entire Atlassian account across every Atlassian product, not just Trello. Organizations running Jira, Confluence, or other Atlassian tools alongside Trello need to account for this before automating offboarding.

The Observer role-read-only board access-is Enterprise-only, which admins on Standard or Premium plans flag as a meaningful gap when they need to grant stakeholder visibility without edit rights.

Common complaints:

• SCIM API transition and deprecation of older provisioning endpoints causes disruption for existing IdP integrations.
• No native group sync between IdP groups and Trello Workspaces; group membership must be managed manually or via Atlassian Guard with limited mapping.
• SCIM provisioning requires Atlassian Guard (additional product), which is not intuitive for admins expecting provisioning to be native to Trello Enterprise.
• Deactivating a user via SCIM deactivates their entire Atlassian account across all Atlassian products, not just Trello, which is unexpected for organizations using multiple Atlassian tools.
• No CSV bulk import for users; bulk provisioning requires IdP/SCIM setup which has a high configuration overhead.
• Observer role is only available on Enterprise, making read-only access expensive for organizations on lower tiers.
• Removing a member from a Workspace on Standard/Premium does not prevent them from retaining access to public boards or being re-invited.
• Lack of granular permission controls at the board or card level beyond the fixed role types.
• Enterprise pricing requires a 50-user minimum, making it inaccessible for smaller teams that need Enterprise features like SSO or Observer roles.

Trello Enterprise is the minimum tier required for centralized user lifecycle management, and it is the only plan where every app and Workspace in the organization falls under a single deactivation action. It unlocks the Enterprise Admin Dashboard, SCIM provisioning via Atlassian Guard Standard (included), SSO enforcement, and the Observer role.

Standard and Premium plans lack centralized deactivation and SCIM, making them unsuitable for organizations with compliance or audit requirements around access control.

The 50-user minimum and annual billing commitment on Enterprise are hard constraints to evaluate before committing. Nonprofits and educational institutions qualify for a 50% discount on Enterprise.

Guard Standard is bundled with Trello Enterprise, so no separate Guard purchase is needed at that tier-but Guard is a prerequisite for SCIM regardless of how it is obtained.

Organizations already running other Atlassian products should validate their offboarding workflows carefully: SCIM deactivation is Atlassian-account-wide, not Trello-scoped.

Bottom line

Trello Enterprise provides the only viable path to centralized, auditable user lifecycle management, bundling SSO, SCIM via Atlassian Guard Standard, and a single-action deactivation that covers every app and Workspace in the organization.

Below Enterprise, admins face manual, per-Workspace removal with no organization-wide deactivation and no automated provisioning.

The layered permission model-Enterprise, Workspace, and Board-means offboarding is never a single step without SCIM in place, and the cross-product scope of Atlassian account deactivation requires deliberate coordination for organizations running multiple Atlassian tools.