Skip to content

Conversation

@DerDreschner
Copy link
Contributor

When using the provisioning functionality, only the configured pattern where checked before pushing the mail account configuration into the database. This is fine as long as all users can use the mail app. But as the access to specific apps can be limited to specific groups, this can lead to accounts that are configured and synced in the background, yet being never used and only eat up precious resources.

To ensure this does not happen anymore, I use the IAppManager to check if the specific user has the right to use the mail app. If not, the provisioning for the user will be stopped.

This fixes #12057.

Signed-off-by: David Dreschner <github-2017@dreschner.net>
@DerDreschner DerDreschner force-pushed the fix/check-for-disabled-app branch from 27e6211 to 6b43c71 Compare January 9, 2026 15:03
@DerDreschner
Copy link
Contributor Author

DerDreschner commented Jan 9, 2026

@ChristophWurst : Should I add a migration to remove mail accounts from users that have no access to the mail app...? Or is that already being handled by a background job, etc.?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Don't provisioning an account when user is not able to use the mail app

2 participants