# Sign-up > Create an organisation's LightHouse tenant by self-service sign-up, or through Atlantic from an order form. An organisation’s LightHouse™ tenant is created by self-service sign-up or by Atlantic from a signed order form. Both routes produce a tenant with one client administrator (`client_admin`), who then completes the [set-up mission](/start/setup/). ## Routes | | Self-service sign-up | Sales-led onboarding | | --------------------------------- | ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------- | | **Started by** | A person at the organisation | Atlantic, from the order form | | **Agreements** | The MSA and DPA in force, accepted by click-through | The order form; a negotiated MSA or DPA signed on paper is [recorded by reference](/enterprise/agreements/#negotiated-agreements) | | **Commercial terms** | Standard; set on **Billing → Terms** | Set by agreement and recorded on the tenant | | **Administrator’s first sign-in** | At the portal address shown when sign-up completes | From the invitation email Atlantic sends | | **Sign-in method at first** | One-time PIN sent to the administrator’s email address | One-time PIN sent to the administrator’s email address | ## Self-service sign-up ### Requirements | Field | Requirement | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Work email** | Required. Disposable email domains are refused. A personal mail domain is accepted and reviewed by Atlantic. The address becomes the client administrator’s sign-in | | **Organisation** | Required. The name the organisation trades under, 2 to 120 characters. The tenant’s identifier is derived from it | | **Country of registration** | Required. The country in which the organisation is registered | | **VAT number** | Optional. Checked against the EU VIES service where given, and kept for invoices | ### Procedure 1. Open `https://platform.atlanticagenticlabs.com/register`, enter the organisation’s details and choose **Send me a code**. Result: LightHouse sends an email to the address with a six-digit code and a link to continue. The response is the same whether or not the address or company is already registered. 2. Enter the code. The code is valid for 30 minutes and accepts six attempts; **Send a new code** issues a new one and invalidates the previous code. The sign-up link is valid for 24 hours. Result: the email address is verified and the VAT number is checked against VIES. The VIES result is recorded as valid, invalid or unavailable. An unavailable VIES service does not stop the sign-up. 3. Read the master services agreement (MSA) and the data processing agreement (DPA) in force, select both, and choose **Accept and create my organisation**. No tenant exists before this step. Result: LightHouse records each acceptance (agreement, version, time, the verified email address, and keyed hashes of the network address and browser) and creates the tenant in the same transaction. The page shows the tenant ID and the portal address, `https://.atlanticagenticlabs.com`, and LightHouse emails the tenant ID to the administrator. 4. Open the portal address and sign in with the one-time PIN sent to the same email address. Result: the person is signed in as the tenant’s client administrator. ### The new tenant | Property | Value | | ------------------- | ------------------------------------------------------------------------------------------------------------------- | | **State** | Sandbox: synthetic sample data, with Octy™ available | | **Spend** | No managed model calls until a payment method or invoice terms exist (set-up step **Settle how you pay**) | | **Sign-in** | One-time PIN to the administrator’s address, until an [identity provider](/enterprise/single-sign-on/) is connected | | **Billing details** | The country, VAT number and VIES result are carried to **Billing → Terms** | ## Sales-led onboarding 1. The organisation signs Atlantic’s order form. The agreements are part of the order. A negotiated MSA or DPA is signed outside the portal. 2. Atlantic creates the tenant from the order form, with the commercial terms set, and records the agreements against it. Result: the tenant exists in the same initial state as a self-service tenant, with the order’s terms recorded. 3. Atlantic sends the named administrator an invitation email, **Your LightHouse sign-in**, with the portal address and the tenant ID. The email contains no credential. 4. The administrator opens the portal address and signs in with the one-time PIN sent to that email address. Result: the administrator is signed in as the tenant’s client administrator. Atlantic can resend the invitation on request. ## Limits | Limit | Value | | --------------------- | ----------------------------------------------------------- | | Sign-up link validity | 24 hours | | Code validity | 30 minutes | | Code attempts | 6; then `429 code_spent`, and a new code is required | | Rate limiting | Per network address, per email address and per email domain | ## Audit Tenant creation is recorded in the tenant’s audit log as `tenant_registered`, with the route (self-service or Atlantic), the VIES result and the agreements recorded. An invitation sent by Atlantic is recorded as `tenant_invite_sent`, and commercial terms set from an order form as `commercial_terms_set`. ## Next Complete the [set-up mission](/start/setup/). [Organisation set-up](/enterprise/) lists the steps in order. Source: https://docs.atlanticagenticlabs.com/enterprise/sign-up/