Skip to main content
Version: 0.9.19

Register an account

Register when you need a new Delphi product account and team through the installation's self-service checkout. If an administrator has already invited you or you need access to an existing team, follow that invitation instead; provisioning and membership explains the administrator's route. Creating another registration does not add your existing account to someone else's team.

Before you begin​

Use the intended Delphi installation and an email address you can receive mail at. Have your account details ready and review the plans and checkout requirements shown by that installation. Do not assume the same prices, plan names or selectable options across deployments.

Availability: /register requires self-service registration to be enabled in the UI; when disabled it redirects to sign-in. The backend also requires credentials/password authentication to be enabled. The deployment administrator owns these settings. A Microsoft-only installation does not turn this form into corporate SSO registration: request the appropriate account/team access from your administrator. See feature availability for configuration ownership and access and sign-in for an existing account.

Registration follows Choose Plan → Your Details → Verify Email → Legal Agreements, then checkout and a separate setup-status page. Email verification, payment completion, account provisioning and usable application resources are different steps.

1. Choose a plan and enter your details​

  1. Open /register on the intended installation and select an available plan. Only currently eligible self-service plans are listed. No plans available at this time requires help from the installation administrator; it is not an invitation to guess a plan URL.
  2. Under Your Details, enter First Name, Last Name, Email, optional Company Name, Password and Confirm Password. Follow the displayed password validation; use the visibility control to check your entry privately.
  3. Review Commitment Period, the displayed price and totals. The form offers 1, 6 or 12 months; use the actual terms and checkout summary rather than a documentation example as the price agreement. Later changes belong to subscription and usage.
  4. Review Provide me a Delphi phone number when shown, including any displayed surcharge. The Starter form requests a number automatically and hides this switch. Requesting a number is not proof that allocation will succeed or that calls will work.
  5. Choose Continue to request the verification email. The details remain in the current browser flow; this initial request does not submit the password or create a usable account.

If you already use that email on this installation, use sign-in or password recovery. To protect account information, the verification request can return success for an existing account without sending a new registration email. A “sent” message therefore does not prove delivery, eligibility or account creation.

2. Verify your email​

Enter the six-digit code from the email into the PIN boxes, or paste the complete code, then choose Verify. All six digits are required. Back lets you correct the address/details; returning from this verification step clears the current browser verification state.

The pending verification expires after 15 minutes. Resend code becomes available after a 60-second cooldown, but resending does not extend the original expiry. Repeated incorrect codes are also limited by the backend; stop guessing and follow the returned error/restart instructions.

Successful verification gives this browser flow a time-limited completion proof and another 15-minute completion window. Continue to document review in the same flow. This proof is not a login session, and verification alone does not create the team. If you go back from Legal Agreements to edit details with the same verified email, the form can reuse the still-valid proof without asking for the PIN again. Changing the email requires verification again.

If no code arrives, check the address and mailbox filtering, wait for the resend cooldown, and use Resend code while the pending request is valid. If you already have an account, return to sign-in/recovery. If delivery still fails, contact the administrator; they can investigate the mail job. Do not keep starting parallel registrations or use a second address to work around a delivery problem.

3. Review the documents and continue to checkout​

  1. In Legal Agreements, open each displayed document/version. The document viewer offers Download; use it if you need to inspect the file outside the embedded view.
  2. Review the actual documents supplied by the installation. Select the combined acceptance checkbox only when you intend to accept the listed documents, then choose Continue.
  3. Wait for the checkout redirect. Do not treat the click or a loading indicator as confirmation of payment or registration completion.

The server checks the exact current document-version set and the selected plan again. If a document version or plan changed while you were completing registration, reload the flow, review the new selection and verify your email again if required. Do not retry against stale document versions. No legal documents found blocks this step and requires the administrator to correct the catalogue; there is no skip option.

For ongoing team review after onboarding, use Review legal documents. Registration's combined checkbox and the later team review are separate workflows.

4. Complete checkout and wait for setup​

Review and complete the hosted checkout presented by this installation. This registration path still uses checkout; disabling subscription-management UI elsewhere is not a documented payment bypass. A valid reserved checkout may be reused on a retry, so inspect the current result before creating another payment attempt.

After checkout returns, the setup page checks the server status every two seconds until a terminal result. Provisioning is handled asynchronously by the payment webhook. A successful payment or return URL is not proof that every subsequent setup task succeeded.

What the setup page showsWhat to do
Setting up your account...Keep the returned page open while provisioning runs.
Taking longer than expectedThis appears after 60 seconds while status is still pending. It does not cancel setup or prove it failed; polling continues. Check your email and contact support if it remains pending. Avoid paying again to repair it.
Registration SuccessfulCheck for the welcome/password-setup email and use Go to Login when ready. The browser is not automatically signed in. Continue with the checks below.
Registration Expired / Start New RegistrationA registration proof/session expired. If you have not paid, start a fresh registration. If payment was taken or its result is uncertain, ask support to reconcile it first.
Session Not Found or Missing session informationThe page cannot identify this registration. Check that you returned to the same installation and check email; contact support if checkout completed. Do not manufacture a session_id or infer a refund from this screen.

Payment Cancelled is a return page with Back to Registration. Loading that page does not itself cancel a server record, roll back provisioning or issue a refund. If a charge or completed checkout appears elsewhere, have support reconcile it before trying again.

5. Check the account and team before using an application​

Follow the welcome setup link if required. Registration queues that email separately from the initial PIN email; a status page is not proof the welcome message reached your mailbox. For expired setup links, sign-in or password problems, use access and account recovery.

After signing in:

  • Confirm that the intended team is available and selected. If it is missing, ask the administrator to inspect account/team provisioning; creating another registration is not the recovery step.
  • Review the selected team's subscription and legal-document status.
  • If you requested a phone number, confirm its assignment before testing a phone entry point. A completed registration can still have a failed number allocation.
  • Start with your first application only after the required provider credentials, channels and team resources are ready.

The provisioning handler can record consent-insertion or phone-allocation failures and still mark registration completed. Other later failures can leave setup pending after some resources were created. Support should reconcile the existing registration rather than assume another webhook delivery or another checkout will repair every partial state.

Information to give support​

Provide the installation, your registration email through the approved support channel, the approximate time and the visible step/error. If you paid, include the payment receipt reference through that channel. Do not post PINs, passwords, completion proofs or full checkout/status URLs publicly. Support can correlate the existing registration, payment webhook, account/team and mail jobs without asking you to disclose those secrets.