Skip to content
Claresia Docs

Quickstart — Mode A in 30 minutes

This is the fast path for IT admins onboarding Claresia in Mode A (Claresia Cloud Shared SaaS). Target time: 30 minutes from welcome email click to your first end-user skill invocation. If you have a 200+ seat tenant or need data residency, switch to Mode B or Mode C.

The 10-step Mode A flow

Section titled “The 10-step Mode A flow”

  1. Click the welcome-email link.

    Subject: Welcome to Claresia, {Admin Name} — your tenant {tenant_slug} is ready.

    You arrive at https://onboarding.claresia.com/{tenant_slug}?token=.... You see a 10-step progress bar. Estimated total time: 30 min.

  2. Sign in with your corporate SSO. WorkOS handles the redirect; you log in with your usual Okta / Azure AD / Google Workspace credentials.

  3. Confirm tenant details. Display name, region (eu-south-1 by default for Mode A), deployment mode (A — Shared), billing contact. Click Confirm.

  4. Configure SSO — paste your SAML metadata URL OR upload SAML XML OR enter your OIDC discovery URL. Click Test login — Claresia opens a popup, completes a real auth round-trip, and shows a green check.

    See per-IdP guides:

  5. Configure SCIM — copy the SCIM endpoint URL + bearer token from the portal. Paste them into your IdP’s SCIM provisioning panel. Click Sync now in the portal — you’ll see the count of users + groups imported.

    See SCIM provisioning for IdP-specific instructions.

  6. Connect your LLM platform. Pick one of:

    • Claude Enterprise — paste your Anthropic Admin API key
    • Microsoft Copilot M365 — grant Claresia an Azure AD service principal scoped to Power Platform admin
    • OpenAI ChatGPT Enterprise — paste your Compliance API key
    • Google Gemini for Workspace — grant Workspace admin OAuth scope

    Click Test connection. Green check means we successfully called your LLM admin API.

    See per-LLM guides under LLM Connectors.

  7. Provision Hub. For Mode A this is 1-click — Claresia provisions the shared Postgres + RLS row + per-tenant encryption key. ~30 seconds. Hub URL becomes hub.{tenant_slug}.claresia.com.

  8. Map roster to archetypes. Either:

    • Auto (recommended) — if SCIM is configured, Claresia maps every user to one of 14 archetypes via cc-061’s title-classifier. Typical accuracy: >99%.
    • CSV upload — upload your roster CSV. Claresia maps and shows you the unmatched rows for manual assignment.

  9. Confirm skill entitlements. Per-archetype skill grants are pre-generated from your Cowork pack. Toggle off any skills your policy forbids (e.g., clawshield.deal-desk for AEs in regulated geographies). Click Publish.

  10. Run the smoke test. The portal opens a guided in-app panel:

    Now go to your LLM and type @claresia.gatespic.pipeline-hygiene.

    The portal listens for the telemetry event. When it lands, you see a green check + congratulations + links to Command Center, Hub, and your CSM Slack/Teams Connect channel.

What just happened, in plain English

Section titled “What just happened, in plain English”
  • A WorkOS connection was established between your IdP and Claresia.
  • Your roster was synced via SCIM and mapped to 14 archetypes by cc-061.
  • The Distribution Plane published your tenant’s skill catalog into your LLM platform’s admin surface (Anthropic Admin API / Power Platform / OpenAI Compliance API / Google Workspace).
  • A Hub row was provisioned (shared Postgres, RLS-isolated to your tenant_id).
  • Telemetry pull-connector was registered with your LLM platform’s audit log.
  • The first output + telemetry_event Hub records were written when you ran the smoke test.

Verifying it worked

Section titled “Verifying it worked”

Open the Command Center: https://app.claresia.com/{tenant_slug}/. You should see:

  • Skills tab — every published skill with its archetype grants
  • Telemetry tab — your smoke-test invocation with cost ($0.04 typical), latency (1.5–3 s typical), and tokens
  • Audit log — governance_event entries for every step you completed
  • Hub tab — the output record with its SHA-256 provenance hash

Common gotchas

Section titled “Common gotchas”
SymptomCauseFix
SSO test fails with invalid_audienceThe IdP’s audience URI doesn’t match https://api.workos.com/sso/saml/{conn-id}Re-copy from the portal — don’t retype
SCIM sync returns 0 usersThe SCIM bearer is correct but the IdP’s SCIM scope is wrongSet the scope to Push users + Push groups in your IdP
LLM connection green but no skills appear in CopilotDistribution publish lag (60s p99)Wait 90s, then refresh Copilot
Smoke-test event never landsLLM platform audit log hasn’t ingested yetWait up to 5 min p95; if still missing, check the LLM platform’s audit log directly

You’re live. What now?

Section titled “You’re live. What now?”