Feature request: Bot / service account support for API integrations

[adriantaut]

We're integrating Fizzy into our development workflow using the fizzy-mcp server to let AI agents interact with boards programmatically. Currently, API access requires Personal Access Tokens tied to human user accounts.

This means we have to create a regular human user to represent a bot — which works, but has drawbacks:

• The "user" consumes a seat and appears in user lists alongside real humans
• No way to distinguish bot actions from human actions in the UI
• No bot-specific permissions or rate limits

Proposal

Support a bot / service account user type that:

• Can generate Personal Access Tokens like regular users
• Is visually distinguishable in the UI (e.g., a bot badge on comments/actions)
• Doesn't consume a regular user seat
• Can be scoped to specific boards or permissions

Context

Basecamp 3 had chatbot support. A similar concept for Fizzy's API would make it much easier to build integrations where actions are correctly attributed to bots rather than phantom human accounts.

On a related note — we're also looking forward to the official MCP server landing via #2298, which would make integrations like this even smoother.

[adriantaut]

We've implemented this in our fork with a bot role on the User model. The approach:

• Bots are a distinct role alongside owner/admin/member/system
• They skip notifications, push notifications, email bundling, settings creation, and onboarding
• They get synthetic email identities so existing PAT auth works unchanged
• Admin UI for creating/managing bots and their access tokens
• JSON API endpoint (POST /account/bots) for programmatic provisioning
• Bots appear in the active scope (can be assigned to cards) but don't trigger human-facing side effects

Happy to open a PR upstream if there's interest — would appreciate any guidance on preferred approach before we do.