Site access and administration
Manage role access and the services that apply across the WordPress installation.
Personal settings belong to one WordPress user. Administrative settings govern the PressedMail installation. Use the gear icon to open Settings, then choose the relevant administrative tab.
Grant workspace access
Open Access Control and review which WordPress roles have access. Administrators have access by default. Grant only the capabilities a role needs, such as using the workspace, adding accounts, or viewing diagnostics.
After changing a role, verify with a separate account assigned to that role. A setting visible to an administrator is not proof it is available to another user.
Roles and people
The paid plugin splits Access Control into three tabs. General holds attachments and email display. Roles chooses which WordPress roles can open PressedMail, and says how many people hold each one. Users lists everyone on the site and lets you set one person to Allow or Deny.
A setting on a person beats their role. Inherit, the default, follows the role. Allow lets someone in even when their role cannot open PressedMail, and Deny keeps them out even when it can. Administrators always have access, so their row cannot be changed. If a person becomes an administrator while a Deny is still on them, the Deny is ignored and the row offers to clear it. Someone who has no role, or a role that cannot read the site, cannot open PressedMail whatever is set for them, so Allow is not offered on their row until they have one.
Changes on every tab wait for one Save. The count beside Save says how many are waiting, and the Users tab previews what each person's access will be before you apply anything.
If your licence includes audit logs, every change to who can open PressedMail is written to the audit history, with who made it and when. A change to one person is recorded for them and for you, and a change to roles is recorded for you. If the site refuses a write, Save says the change was not saved and nothing is recorded. A Deny on someone whose role already keeps them out stops nothing today, so it is saved without the warning about lost work, and it still wins if a role lets them in later.
What happens when someone loses access
Losing access, by role or by Deny, pauses that person's PressedMail work. Mailbox sync, scheduled emails and follow-up reminders wait, and carry on when access returns. A scheduled email that came due in the meantime goes out as soon as access is back, even though its time has passed. Filter rules and auto-replies stop, so an out-of-office reply is not sent while they are out, and their API keys and webhooks are refused. New notifications are not created for them, and anything they share is hidden until then. Bulk actions in progress and an email still in its undo window stay pending and resume when access returns. Mail with an uncertain send outcome is not retried automatically, and accepted sends are never replayed. Nothing is deleted.
Role access does not transfer mailbox ownership. A connected account remains associated with the WordPress user who added it. These are application access controls, not protection against someone who controls the server or database.
Configure site-wide services
| Task | Guide |
|---|---|
| Send WordPress notifications through a dedicated SMTP configuration | WordPress SMTP setup |
| Keep or inspect notification metadata | WordPress email logs |
| Activate a paid installation or move its license | Activate and manage a license |
| Configure an AI endpoint and see what it is sent | Set up and use AI |
| Replace the product identity on an eligible plan | White labeling |
WordPress SMTP has its own server configuration. Choosing a mailer there does not reuse a user's inbox credentials or change composer sending.
AI is optional and off until configured and enabled. A site-wide Enable AI features switch turns the AI features off in the interface and in automatic processing, and each feature has its own switch. Do not enable automatic checks or tagging before reviewing the data they can send.
Review security and diagnostics
Site-wide image and phishing policies can restrict the choices shown to users. Check Email safety and audit history before forcing a policy.
Diagnostics checks the environment and connection health. Capture the relevant results before changing several settings at once, then repeat the affected check afterward. Find the problem and collect diagnostics lists what to include in a support request.
Uninstall data deletion is a separate destructive choice. Keep it off unless you intend to remove PressedMail's local records when deleting the plugin. See Update, deactivate, and uninstall.