I have been through this page, I have already configured roles and security groups, including security suite settings.
I even created a test user and gave it full access to all modules via the roles/security groups yet they still can’t set an outbound email account as default.
I’m wondering is there a way to set a default outbound email account for a specific user from the database
(Screenshot from ADMIN account, as you can see the option is there, it is missing when the regular user “Phil” accesses the page)
Attention to the emails module in the roadmap is good @BastianHammer though its hard to say if it will be included in the update, I will make an issue on git when I get a chance
This line will only be set if the account has a default outbound account defined, I tried adding the line in anyways but it didn’t make a difference. I’m guessing this is a caching table and the true value is set somewhere else.
I proposed a fix for this issue for SuiteCRM core.
I traced this to a mismatch between user ownership and default-outbound preference handling.
In compose, the From field (outbound_email_name) is initialized by outbound-email-default.
Before this fix, that process only looked at the user preference Emails.defaultOEAccount. If that preference was empty, compose stayed blank.
The issue is that for personal outbound accounts created by an admin, default assignment and “Set as default” checks were effectively tied to created_by in some paths, not the personal account owner (user_id). So regular users could end up with no usable default even though they owned a valid personal outbound account.
Owner-based default assignment on save
For type=user outbound accounts, default is assigned to the account owner (user_id), not implicitly to the current session user.
Owner-based SetDefault flow
“Set as default” resolves owner by user_id first (for personal accounts), and UI visibility is based on owner/admin, not only creator.
Safe compose fallback
If defaultOEAccount is empty, compose now auto-selects the outbound account only when the user has exactly one valid personal outbound account.
If there are multiple (or none), it still requires explicit user selection (no risky guessing).
This keeps behavior predictable and fixes the regular-user case without changing transport/sending logic.
The Pull Request needs to be reviewed by two write-access developers to be merged into SuiteCRM Core.
How interesting, thank you so much for your reply,
I deleted the outbound account and recreated it as the actual user and it was automatically assigned as default. Email from is auto-selected now. Hope your pull request can get some attention, this feels like a no brainer!