Organisation settings
The admin console's Organisation section holds the settings a company or a hoster makes for its users: what every message carries, what warns them, when they are signed out, and what teams share. Each page explains in one sentence what it does for users.
| Page | What it sets |
|---|---|
| Domains and groups | Different settings for some domains or groups, the effective policy of a user, the policy file |
| Signatures | The organisation signature with each user's details, and the legal disclaimer |
| Templates | The template library every user sees, and what users may keep of their own |
| Security | External sender label, external recipient warning, sign-out times, third-party traffic |
| Sharing | Tags in shared mailboxes, delegates, recovering deleted items |
Assigning messages in a shared mailbox and marking them done comes from the Team inbox plugin, not from these pages. It isn't in the extension directory yet; you upload its ZIP under Extensions > Plugins.
Every setting has a default that works without configuration. An admin who does nothing gets Bulwark as before.
Locking a setting
For 26 settings the admin can lock the value users get or hide the option, and each setting offers only what fits it. Users then see the admin's value with Set by your organisation next to a locked setting, instead of a control that does nothing. Two settings have a limit of their own: Notification duration takes a minimum, and Rights users can give can be limited to read access. Most of the 26 are on the User policy page; the Organisation pages list theirs next to the settings they belong to.
Many more settings can be preset: users start with the admin's value and can change it. The accessibility reading aids, such as text size, contrast and motion, are among them. They can be preset but never locked or hidden.
Everything is one file
All of it, and the User policy page, is stored in one file, policy.json in ADMIN_CONFIG_DIR. The one exception is the No third-party traffic switch on the Security page, which is a server setting in config.json. You can keep policy.json in git and mount it read-only, export it from one instance and import it on another, or put it next to a Bulwark Lite build, which reads the same file. See the policy file. With several instances on a shared store, the policy lives in the store unless you mount the file read-only, and a saved change reaches every instance within seconds. When two admins save the policy at the same time, the one who saves second is told that someone else changed it and keeps their edits until they reload.
policy.json by hand, or export it from a full Bulwark, and put it next to index.html. Lite applies the same domain and group settings.