Creating tenants

Organisations come into being exclusively through provisioning. Whether the operator creates them in the panel, a checkout frontend books them, or someone registers themselves: all three paths invoke the same mechanism. This means there is no second place where a half-created tenant could arise.

Each creation produces:

• the organisation (tenant) with plan and home region,
• its first administrator (account plus global identity),
• that administrator’s base project.

Path 1: Operator API

curl -X POST \
  -H "X-Operator-Token: $DNSE_OPERATOR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
        "name": "acme",
        "plan": "pro",
        "adminUser": "alice@acme.example",
        "adminPassword": "geheim-123"
      }' \
  https://cloud.example.com/api/v1/operator/tenants

Field	Required	Meaning
name	yes	Name of the organisation (unique, case-insensitive)
plan	no	free (default), plus, pro, enterprise
adminUser	yes	Email of the first administrator
adminPassword	yes	Initial password
adminDisplayName	no	Display name
adminEmail	no	Different contact address
region	no	Home region; empty = primary region of the instance

A name already taken is rejected with 409.

Instead of the token, a signed-in operator session also works — in the panel that is exactly the Create organisation button.

Path 2: Self-service registration

Registration runs via a magic link:

Step	Call
Enter address	POST /api/v1/register/start
Verify link	GET /api/v1/register/check
Complete	POST /api/v1/register/complete

The link is valid for 15 minutes. Only in the final step do the organisation and account come into being — before that, nothing exists that would need cleaning up.

In demo mode the link is returned directly in the response, so the flow can be walked through without an outgoing mail server. In production it is sent by email, for which the SMTP settings must be configured at the platform level.

Signing in afterwards

Sign-in uses email and password — no field for the organisation. If a person belongs to several organisations, the sign-in form asks after the password which one is meant. Details: Identity and organisations.