Tenants
A Tenant is the top level of VeroXM's organization hierarchy: Tenant → Department → Project. Every Department belongs to exactly one Tenant, every Project belongs to at most one Department, and a Tenant Admin administers everything beneath their Tenant without needing a separate role on each Department or Project inside it.
Most workspaces have one Tenant
A single VeroXM deployment can host more than one Tenant, but most workspaces run with exactly one. You don't need to think about Tenants at all until you're managing more than one organization's worth of Departments from the same workspace.
Tenant details
A Tenant has a display name (editable at any time by a Tenant Admin or Super Admin) and a slug, a URL-safe identifier chosen at creation that can't be changed afterward.
Deleting a Tenant is permanent and only possible while it has no Departments — every Department, Project, and role grant beneath a Tenant stops having a home the moment it's gone, so this is deliberately a Super Admin–only action, not something a Tenant Admin can do to their own Tenant.
Tenant Admins
A Tenant Admin sees and manages every Department in their Tenant — and every Project inside each of those Departments — without needing a separate role on each one. Grant Tenant Admin by email from the Tenant's page; if the address doesn't match an existing account, VeroXM creates one and emails a set-password link, shown as Pending activation until they sign in for the first time. Only a Tenant Admin or Super Admin can grant or revoke another Tenant Admin.
Tenant users
The Tenant page's user list is a read-only roll-up of everyone with a role anywhere under the Tenant — Tenant Admins, Department Admins and members of every Department, and Project members across every Project in those Departments — each row showing every role that person holds. It's a single place to answer "does this person have access to anything here," without opening each Department and Project individually. Manage someone's actual role from the Department or Project page it applies to; this list doesn't grant or revoke anything itself.
Email (Resend) integration
By default, transactional email VeroXM sends on a Tenant's behalf — invitations, set-password links, notifications — goes out under the platform's shared Resend sending identity. A Tenant can instead configure its own Resend API key and From address, so that email goes out under its own sending identity instead. This is optional per Tenant; leave it unconfigured to keep using the platform default, or toggle it off later to fall back without losing the saved key.
Where a Tenant fits in
A Tenant Admin's job is largely structural: create Departments, grant Department Admins, and keep an eye on who has access to what across the Tenant. Day-to-day content work — Collections, Content, Media, API tokens — happens one level down, inside a Project. See Departments for how a Tenant's Departments are structured, and Approval Workflows for how a Tenant Admin gates publishing within a Department.