Human onboarding (self-serve sign-up)

Last verified: 23 October 2026, against the public site.

Follow these steps to create an organization, confirm the email address, and open Control Tower. An automated agent that should skip human verification and email confirmation should use the AI agent onboarding guide.

Before you start

• /robots.txt. Public pages may be fetched. The paths /api/, /*/Auth/, and /swagger are not for crawling. Opening the sign-up and sign-in pages to complete this flow for a person is allowed.
• /llms.txt. This is the site index. Add .md to a page address for a markdown copy.

The password must be at least 12 characters and include an uppercase letter, a lowercase letter, a number, and a special character. The confirmation must match. Do not publish a real password.

Example values

Replace every example with your own. These placeholders are not a real account.

Step 1: Open the sign-up page

Open the Create Account page for your language. The form has these fields and no terms checkbox. /en/Auth/Register

Step 2: Pass human verification and submit

1. Fill every field. The password and the confirmation must match.
2. Wait until the Cloudflare Turnstile check shows Success, then click Create Account.

If you submit before the check finishes, the page asks you to complete the human verification. Wait, then click again.

You are taken to the sign-in page. A green banner says: Registration successful! Please confirm your email before signing in.

Step 3: Confirm the email address

SeekBytes sends a confirmation message to the address you registered.

• From: noreply@seekbytes.com
• Subject: Confirm your SeekBytes email

The message asks the named person to confirm that email address for the named organization before sign-in, and it includes a Confirm email link.

The link has this shape. The token is one-time. Replace the placeholders with the values from your own message. Never post the token in logs or public channels.

https://seekbytes.com/Auth/ConfirmEmail?userId=<user-id>&token=<one-time-token>&email=operator%40example.com

Open the link. The page says: Email confirmed — welcome aboard. You can sign in now. A Sign in button is on the page.

A person or agent without access to that mailbox must get the link from the mailbox owner.

Step 4: Sign in

Open the sign-in page, enter the email and password, and submit. /en/Auth/Login

The browser continues to the admin app with a one-time code. The admin app can take a short time to finish loading. Stay on that page until it appears. Do not reload while it is still loading.

You arrive at Control Tower. The header shows the first name and the organization name.

Step 5: What a new organization sees

The first account is the administrator for that organization, so the menu includes users, roles, settings, and the day-to-day work areas.

Menu areas observed on 23 October 2026. Names below are the English labels from that check.

Starting cards observed on the same check. A new self-serve organization has no commercial edition until one is assigned.

Readiness list observed on the same check.

When an automated agent should use the other guide

This page needs the Cloudflare check and a mailbox. The AI agent onboarding guide covers a sandbox sign-up with no human verification and no confirmation email, and it also points back here when a person must open the confirmation link.

AI agent onboarding (sandbox and browser)

Checklist

1. Read robots.txt and llms.txt.
2. Open Create Account and fill in the six fields with your own values.
3. Wait for the human verification success state, then click Create Account.
4. Confirm the green banner on the sign-in page.
5. Open the confirmation link from the email and confirm the welcome line.
6. Sign in and wait for the admin app to finish loading.
7. Confirm Control Tower shows your organization name.