Console & project onboarding
Workspaces, logos, integrations and secrets.
Account and company
Sign into Console with Google or an
email code. Google returns through Console's /sso-callback; missing names or
unverified email continue through signup rather than skipping requirements.
A My or Mobile session cannot authenticate Console.
Create/select your company organization and provide its logo. Only an organization administrator can administer projects or reveal their credentials. The current default is 20 members per new organization.
Logos and validation
Company and project logos are separate assets. Upload PNG, JPEG or WebP, at most 2 MiB. The server checks file signatures, size, ownership and one-time upload state. A company logo is required by onboarding; a project logo is optional.
Private object storage and short-lived signed reads protect storage access. Logos are displayed on public authentication screens, so do not upload confidential images. Never attach an asset belonging to another company.
Projects
Start by choosing Use my AI assistant or Set up manually. The AI copy contains the full integration skill plus non-secret project context. It guides the developer through frontend/backend changes and asks about agent permissions; enter client/webhook secrets directly in Auth0 or a server secret manager, not chat.
The wizard validates project identity, Auth0 callback/security, webhook URL and
optional Advanced legal fields before review. HTTPS URLs cannot include embedded
credentials or fragments; callbacks must match the configured Auth0 origin and
/login/callback exactly, without query parameters.
Continuing after Integration saves a disabled draft and generates stable client and webhook credentials. The next Auth0 step shows the Versine client ID, discovery URL and on-demand client secret for Auth0's OIDC connection. These are not your existing Auth0 application's credentials. Follow Auth0 setup, then implement the login/signup entry, agent permissions and webhook endpoint. Finish setup activates the project only after the remaining fields validate. You can reopen a draft from Dashboard; draft OIDC/MCP authentication is blocked.
With no projects, Projects in the sidebar is disabled. Use Create project from Dashboard. Once projects load, the sidebar and project switcher are available.
Secrets and delivery
The integration screen reveals the client secret and VERSINE_WEBHOOK_SECRET
only on request. Hide them after copying into the correct server-side destination.
They are not included in the initial configuration response.
Webhook Delivery & Verification explains signatures, retries and event history. Only exactly HTTP 200 succeeds. Read delivery rules before launch.
Changing Terms/Privacy URLs increments the legal version. Current acceptance is reused; the next authorization prompts again after a change. Do not silently replace legal text behind a URL without coordinating versioning.
Authorized users
A project's Users view shows its authorized-user identity and available acceptance history. This is organization-scoped personal data; limit access and retention. “Connected” reflects recorded authorizations, not a production certification badge.