#Organizations
Organizations model who you are (a company, its subsidiaries, divisions) and carry the data that appears in signatures — name, address, logo, colour and any custom fields. They are also the unit of access control: roles granted on an organization apply to everything below it.
Open Organizations in the sidebar.
#The tree
Organizations form a tree, for example:
My Group (top level)
├── Company A
│ ├── Sales
│ └── Support
└── Company B
- The tree is shown on the left; select a node to edit it.
- Signatures created in an organization can be used by that organization and everything beneath it.
- Data is inherited downwards: a child shows the parent's value in grey and only needs to override what is different (for example its own address or logo).
#Data used in signatures
For the selected organization, Data used in signatures has these standard fields:
| Field | Template variable | Notes |
|---|---|---|
| Name in signature | org.name |
Company name as it should be printed. |
| Address | org.address |
Free text; one line or several. |
| Website (display) | org.website |
Text shown, for example www.example.com. |
| Website (link) | org.websiteUrl |
The link target, with https://. |
| Logo | org.logoUrl |
Upload an image, or enter a public https:// address. |
| Colour | org.accentColor |
A hex colour such as #0f766e, used for accents. |
An empty field means "use the inherited value".
#Logos
Click Upload image, choose a file and then Save the organization.
- Allowed: PNG, JPEG, GIF, up to 1 MB. The type is checked by content, not by file name.
- SVG is not supported: most mail clients cannot display it.
- Uploaded logos are stored on the server (
data/uploads/) and served publicly fromhttps://<host>/uploads/<hash>.png. This is required: the recipient's mail client downloads the image directly, so it must be reachable from the internet. - File names are content hashes, so uploading the same image twice stores it once. Images are not deleted when an organization is deleted.
Tip. Use a logo around twice the size it is displayed at (for example 160×160 px for an 80×80 px slot) so it looks sharp on high-density screens.
#Custom fields
Type a name under New field (for example vatId) and click Add. The field becomes available in templates as {{ org.vatId }}, and you can set a different value per organization. Typical uses: company registration number, VAT ID, legal disclaimer text, social-network URLs, a second logo.
Custom field names should use letters and digits (no spaces) so they are easy to reference.
#Creating organizations
- Top-level organization — button at the top of the tree. Only Owners can create top-level organizations.
- Sub-organization — select the parent and choose Sub-organization. Admins can create sub-organizations below the organizations they administer.
You enter a name and a short name (slug). The slug is unique, uses lowercase letters, digits and hyphens, and cannot be changed later.
#Deleting an organization
Only an empty organization can be deleted — no sub-organizations, no signatures and no rules. Remove those first. Deletion is recorded in the audit log.
#Which organization's data does a user get?
A user is not "in" an organization. Instead, each rule names the signature and the organization whose data fills it. This lets one person in one directory use different branding depending on the rule that matches — for example subsidiaries sharing a single Entra tenant.