Create your organisation

Your organisation is your company in Seylo. It owns your clusters, users, agents, approvals and audit trail, and it is isolated from every other organisation.

Your email domain decides which organisation you belong to. Signing up as you@acme.example either creates the organisation for acme.example or asks to join the one that already exists.

Sign up

1. Go to the portal and choose “Create an account”.

   Use your work email address. Consumer mailbox providers — Gmail, Outlook.com, Yahoo, and disposable-address services — cannot claim a domain, because claiming one would route every other person who uses that provider into your organisation. You can still sign up with one; you get a personal workspace rather than a company organisation.

2. Check your inbox and click the verification link.

   Nothing exists until you click. No user record, no organisation, and no domain claim — so typing a colleague’s address into the form cannot claim your company’s domain on their behalf. The link is single-use and short-lived; requesting a new one supersedes the old.

3. What the click does depends on whether your domain is already claimed.

   Situation	Outcome
   Nobody from your domain has signed up	The organisation is created and you become its first admin
   The organisation exists and allows self-service signup	Your account is created as pending and a join request goes to the administrators
   The organisation exists and has closed self-service signup	You are told to contact your administrator. No mail is sent and no account is created
   You used a consumer mailbox provider	A personal workspace is created for you alone

4. If you founded the organisation, you now hold admin.

   Go to roles and permissions before you invite anyone — the four roles are worth understanding first — and then to single sign-on if you want your identity provider to grant access instead of individual invitations.

Joining an organisation that already exists

Your account is created in pending status. An administrator sees the request and either approves it — choosing which roles you get — or rejects it. You are notified either way.

An administrator approving a request activates your account only if your email address was actually verified. An approval never activates an account whose address was never proven; that is the thing verification exists to prevent.

Administrators: turning self-service signup off

Under the organisation’s authentication policy you can disable public signup. New colleagues then cannot create a pending account at all, and access is granted exclusively through your identity provider or by explicit invitation. Most organisations do this once SSO is configured.

Why the form never says “that email is already registered”

Registration, password reset and verification all return the same response whether or not the address exists:

• Register → “Check your email.”
• Reset → “If that address has an account, a code is on its way.”
• Verify → the same failure for a wrong, an expired and an already-used token.

This reads like missing error handling. It is the error handling. A registration form that says “that email is already taken” is a free account checker, and for an infrastructure product it is also a staff directory of our customers. The cost is that you occasionally check your inbox for a mail that explains you already have an account. That is the trade, and we chose it deliberately.

The same reasoning applies to the sign-in page’s domain lookup. It answers per domain, never per address, so it cannot be used to discover whether a particular person has an account.

Rate limits on signup

Signup attempts are counted in a rolling one-hour window:

Limit	Value
Attempts per source IP	5 per hour
Attempts per email domain	20 per hour

A throttled attempt looks identical to a successful one from outside. If you are onboarding a large team at once, use your identity provider or invitations rather than asking twenty people to sign up in the same hour.

Next

• Roles and permissions — what each role can do
• Managing users — invitations, join requests, deactivation
• Set up single sign-on — grant access from your existing directory