Add an isActive / disabled status field for Accounts

[chuyenim]

Topic

Hi Stalwart Team,

I am currently using the Internal Directory (RocksDB) to manage user accounts. Currently, to temporarily deactivate a user, we have to manually move authenticate and authenticate-oauth to the disabledPermissions list via the Permissions system.

While this workaround achieves the goal, it is overly complex and inconsistent for standard account lifecycle management. From a system administration perspective, relying on permission overrides to handle a basic account state adds unnecessary friction.

Proposed Solution:
Please consider adding a simple boolean status field (e.g., isActive: true/false or a "Disable Account" toggle) directly on the Account object.

This would provide a cleaner, more intuitive, and standard way to block user authentication without tampering with the underlying permission matrix.

Thanks for considering this!

---

Screenshot 1: Users mistakenly believe they have entered the wrong account.

Screenshot 2: Status feature is available with domains.

Acknowledgement

• I have reviewed the documentation and the FAQ and confirm that my question is not addressed there.
• I understand that maintainers no longer answer support questions through GitHub Discussions, and that for an official response from the Stalwart team I need to post my question at support.stalw.art.
• I agree to follow the project's Code of Conduct.

[github-actions[bot]]

Hi @chuyenim, thanks for posting!

Stalwart support has moved to support.stalw.art. The support portal is now the canonical place to ask questions, request help, and report issues for triage. Other community members may still reply here, but the maintainers no longer answer support questions through GitHub Discussions, so your question may go unanswered unless you also post it on the portal.

You can sign in to support.stalw.art with your existing GitHub account, so no separate registration is required. Google, Discord, LinkedIn, and email/password sign-in are also available.

Why we are unifying our support channels

Until now, Stalwart support has been spread across GitHub Discussions, Discord, Matrix, and Reddit. As the project has grown, tracking parallel inboxes and deduplicating threads has become unsustainable; the result has been slower answers, repeated work for the people helping out, and good information buried in chat scrollback where the next person with the same question would never find it.

support.stalw.art is a Discourse instance that we operate ourselves, hosted at Hetzner in Germany and GDPR-compliant.

Thank you for helping us keep the conversation in one place.