Tenant settings

Tenant admin

Everything tenant-wide that is not a user, a queue, a node or money.

Open registration

Whether anyone can sign up into your tenant on their own, rather than being invited.

Open registration is exactly as open as it sounds

Anyone who can reach the sign-in page can create an account in your tenant. They land with no group, so they cannot submit anything - but they exist, and they are yours to clean up. Leave it off unless you have a reason.

The platform can forbid open registration system-wide regardless of this setting - see System settings.

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.

LDAP

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

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

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

Which events you want to be told about as an administrator, and whether by email.

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.

Branding

Your own logo in the navigation, instead of the standard AiQu one, for everyone in the tenant. A tenant that sets none keeps the standard logo, so this is entirely opt-in.

Pick an image and it is previewed on the navigation’s own dark background before you save it, which is the only way to tell whether a mark actually reads there. A logo drawn for a white page often disappears against it. Remove logo brings the standard one back.

PNG, JPEG, WEBP or SVG. A large image is scaled down to fit rather than refused, so exporting straight out of a design tool is fine. Files above 5 MB are refused. SVG has its own, much smaller limit of 64 KB, because an SVG is stored exactly as you uploaded it rather than being re-encoded, so nothing shrinks it for you. Raster images are converted to PNG when saved, and transparency is kept.