Tenant settings
Everything tenant-wide that is not a user, a queue, a node or money.
Open registration
Section titled “Open registration”Whether anyone can sign up into your tenant on their own, rather than being invited.
The platform can forbid open registration system-wide regardless of this setting - see System settings.
Invitations
Section titled “Invitations”Generate an invitation link for your tenant. This is the controlled counterpart to open registration: the link is what you hand to someone who should have an account.
Point the tenant at a directory server so accounts and groups come from it rather than being maintained here. With it configured, groups can be imported instead of created by hand.
Docker registries
Section titled “Docker registries”The registries your users can pull images from, beyond the public ones.
A registry added here appears in the Docker registry selector on the
submission form, grouped as private or public. Without it, a private image
fails its pull the moment the job starts, with pull access denied in the
logs.
Groups can be given the add registries permission so their members can add their own.
Outgoing mail
Section titled “Outgoing mail”SMTP for this tenant’s mail: invitations, password resets, notification emails.
If people report that invitation or reset mails never arrive, this is the first thing to check. A tenant with no working SMTP can create users who can never complete their invitation - the account exists and the person can never reach it.
Admin notification preferences
Section titled “Admin notification preferences”Which events you want to be told about as an administrator, and whether by email.
Integrations
Section titled “Integrations”NetApp backs storage with NetApp volumes rather than node paths.
Azure VM configurations let the tenant start virtual machines as nodes.
Both are optional and both require the corresponding platform-side configuration to exist first.