Completing your profile
This page appears when a user has a sign-in account but isn’t yet associated with any production company — typically because:
- They started creating an account but the company creation failed
- They were invited to join a company but haven’t yet completed the invite flow
- They signed in for the first time on an orphaned account
The page doesn’t do anything itself — it’s a routing form. The user picks one of three options and the app sends them on to the appropriate flow.
What happens
Section titled “What happens”The user is presented with three choices:
- Create a new company — sends them to the create-account flow to set up a company.
- Join an existing company — they have an invitation code; they enter it and are sent to the company-user registration flow.
- Contact support — opens their email client with a pre-filled message to your support address.
What the user sees
Section titled “What the user sees”| Visible text | Translation key |
|---|---|
| Page title | auth.CompleteProfile.title |
| Description | auth.CompleteProfile.description |
| ”Create a company” option | auth.CompleteProfile.create-company + auth.CompleteProfile.create-company-description |
| ”Join a company” option | auth.CompleteProfile.join-company + auth.CompleteProfile.join-company-description |
| ”Contact support” option | auth.CompleteProfile.contact-support + auth.CompleteProfile.contact-support-description |
| Invitation code field (shown when “Join” is selected) | auth.CompleteProfile.invitation-code (label) + auth.CompleteProfile.placeholders.invitation-code |
| Submit button | auth.CompleteProfile.submit |
What you can customise
Section titled “What you can customise”Translations
Section titled “Translations”All text lives under auth.CompleteProfile.* in tep-configuration/translations/{locale}/main/auth.json. Override per client in clients/{client}/translations/{locale}/overrides.json.
Support email
Section titled “Support email”The “Contact support” option opens the user’s email client with a message pre-addressed to your support address. The address comes from your client’s configuration (AppConfig.supportEmail).
Variations for your deployment
Section titled “Variations for your deployment”The page is the same across all clients. The only thing that varies is the support email address (set per client).
Need more detail?
Section titled “Need more detail?”For code paths, see Completing your profile (engineering).