User Problem

Enterprise customer want to use Service Accounts—non-human accounts managed by IT or administrators—for tasks like forwarding emails to boards, integrating with other systems, or automating workflows. Currently, Trello does not support Service Accounts that can log in, generate Email-to-Board addresses, or authenticate directly with Trello, which creates administrative overhead and potential security risks when using personal or shared user accounts for automation.

Suggested Solutions

• Allow the creation and management of Service Accounts within Trello/Atlassian Admin that can:

• • Log in programmatically (not interactively)

• • Be assigned to boards and workspaces without using a paid user license

• • Generate Email-to-Board addresses

• • Authenticate via API tokens or OAuth for integrations and automation

• Provide clear documentation and admin controls for managing Service Accounts and their permissions.

Current Workarounds

• Organizations create a dedicated Managed/Generic User Account (e.g., bot@company.com), assign it to boards, and use it for automation. This requires purchasing an additional Trello license and managing the account like a regular user, which is inefficient and can create audit/logging challenges.

• Alternatively, organisations may use personal user accounts, which creates risk if those users leave or change roles.

• No official Service Account support is currently available.