Onboarding your organization

A seven-step wizard the first admin in a new Strata organization sees right after sign-in, used to configure org-wide defaults, allowed capabilities, teammates, legal acceptance, and your own Azure AI Foundry.

Who sees onboarding

The onboarding wizard appears once per organization, for any admin who can manage organization settings. It runs automatically when the org has not yet completed onboarding and is less than 30 days old. After the first admin completes onboarding, no one else sees the wizard.

You can re-do every choice later from Admin -> Organization Settings.

Layout

Across the top of the page, a rail shows the seven step names: Welcome, Privacy, Capabilities, Teammates, Legal, AI Engine, Ready. The active step is highlighted; finished steps show a checkmark. The page controls are:

• Back (footer) — returns to the previous step (hidden on the first and last steps).
• Continue (footer) — advances to the next step. Disabled until the current step's requirements are met.
• Need help? support@kronisys.com (top-right) — opens a pre-addressed support email.

There is no skip path — the wizard is completed one step at a time, and each step's requirements must be met before Continue enables. Legal acceptance in step 5 is mandatory and enforced server-side: the final save call is rejected unless all three documents have been accepted.

You can press Enter to advance when Continue is enabled.

Step 1: Welcome

Set your organization's name and tell Strata a little about your team.

• Organization name — the label shown to your members everywhere in Strata. Defaults to your email domain if blank. Max 200 characters. If Strata can read your Microsoft Entra tenant, this (and your square logo) is pre-filled from there; editing the name clears the "auto-filled" hint.
• Industry (required) — pick the closest match from the dropdown. Strata uses it to tailor examples, terminology, and assumed defaults to how your team works. Continue stays disabled until you choose one.
• A short overview of your organization (optional) — one or two sentences about what your team does and who you serve, so the AI can frame answers for you from day one. Up to 600 characters; you can add or change it later.

Click Continue.

Step 2: Privacy + defaults

Sets the defaults every new account in your organization inherits. Members can later override these in their own Settings unless an admin locks the field.

• Default database permission — one of:
  • Viewer (recommended) — read-only. Members cannot modify data.
  • Editor — INSERT, UPDATE, DELETE allowed, but every write requires per-query approval.
  • Admin — full SQL including DDL (CREATE, ALTER, DROP). Reserve for DBAs.
• Save AI responses — keep a record of conversations in the platform database. Turn off for zero-retention compliance.
• Save extension output — include SQL results, email bodies, and file contents in the conversation log.
• Long-term memory — let the AI remember facts you tell it across conversations.
• Thumbs up / down on responses — members can rate answers.
• Web search — let the AI fetch live web results during a chat. Off by default.
• Audit log retention — number of days audit-log entries are kept. Anything older than this is deleted nightly. Valid range is 30 to 3650 days; defaults to 365.

Click Continue.

Step 3: Capabilities

Choose which AI models and extensions your organization can use. The header for each section shows the running enabled count.

AI models

Strata runs a Model Catalog — a curated set of AI models that Kronisys maintains centrally and updates over time. New models become available as Kronisys adds them, and retired ones drop out automatically. Your organization picks the subset its members can use, then deploys those models in its own Azure AI Foundry — the resource you connect in step 6.

Every model in the catalog is enabled by default. The summary card shows the providers represented (across OpenAI, Anthropic, xAI, DeepSeek, Mistral AI, Cohere, and Microsoft, all served through Microsoft Azure AI Foundry). To narrow the set:

1. Click Customize to expand the full list, grouped by provider.
2. Toggle individual models with their Enable / Enabled buttons, or use Enable all / Disable all and the per-provider All / None controls.
3. Keep at least one chat model enabled — it powers chat, agents, and voice. Continue stays disabled until one is on. (Specialized models — realtime voice, transcription, embeddings — can't drive the chat surface on their own.)

You can change the enabled set anytime later from Admin → Model Catalog.

Tip

Don't anchor on a fixed list — the catalog is the live source of truth. Open each model in the catalog to see its capabilities, context window, pricing per million tokens, and benchmarks before deciding what to enable.

Extensions

Note

Enabling Jira or Confluence here only makes the extension available to your organization — they are separate checkboxes, so you can allow one and deny the other. The Atlassian site, the connection mode (each person signs in with their own Atlassian account, or everyone works through one organization service account), the optional project and space allow-lists, and whether Strata may write to either product are all configured afterwards on the Atlassian extension's own page: Settings -> Extensions -> Atlassian -> Manage -> Organization settings. Writes stay off until an admin turns them on — until then Strata is read-only in both. Turning them on is the ceiling rather than the whole answer: a role and an individual member can each be set to Denied afterwards, and Jira and Confluence writes are decided independently. See Atlassian extensions.

Click Continue.

Step 4: Invite teammates

Add the first members of your organization.

1. For each row, enter the teammate's work email and pick a role (User or Admin).
2. Click Add another teammate to add more rows.
3. Use the remove icon on a row to drop it. The first row cannot be removed.

Invitations are emailed when you finish the wizard. Recipients sign in with Microsoft and inherit the org defaults you set in step 2. Only the built-in Admin and User roles exist during onboarding — create custom roles later from Admin -> Roles. You can also continue without adding anyone and invite teammates afterwards from Admin -> Invitations.

Click Continue.

Step 5: Legal

Three documents must be accepted before you finish onboarding.

• Terms of Service — the contract between Kronisys Inc. and your organization.
• Privacy Policy — what is collected, stored, and retained.
• Usage Policy — acceptable use of the Strata platform.

For each document:

1. The document loads in a scrollable panel. The acceptance checkbox is disabled until you scroll to the bottom (or the document is short enough to fit without scrolling).
2. Check the box labeled I have authority to bind \<your organization\> to the \<document title\>.
3. Click Next: \<next document title\> to move to the next document; on the last document, the Continue button at the bottom of the page enables.

You can switch between the three documents at any time using the tab pills at the top of the step.

If a document fails to load, an inline error appears with a link to open the canonical document at strata.kronisys.com/legal/<slug> in a new tab — read it there, then return and check the box.

Click Continue once all three are accepted.

Step 6: AI engine

This step is required. Strata runs every AI request about your data — chat, agents, documents, voice and the API — through an Azure AI Foundry resource your own organization controls, inside your own Azure tenant. The in-product help assistant is the sole exception: Kronisys hosts and pays for it, so you can ask for help before your Foundry is connected. Inference stays in your Foundry — no prompt, data, or content is ever sent to a Kronisys-controlled model. Connect your Foundry here to finish onboarding.

To connect your Azure AI Foundry:

1. Enter your Foundry endpoint (for example https://your-resource.services.ai.azure.com).
2. Paste your API key. It is stored securely and never displayed again after you save.
3. Make sure your Foundry project exposes a deployment for every model you enabled in step 3. The panel lists the exact deployment names to create based on your selection — so enable your models first, then deploy those names in your Foundry project. A full walkthrough is at strata.kronisys.com/docs/admin/ai-engine.
4. Click Verify & connect. Strata calls your Foundry to confirm reachability and that the deployments for your enabled models exist. The button hides and both fields turn green on success; a red X appears on both fields and the verify button reappears on failure.

Warning

There is no fallback. Every AI request goes to your Foundry. If your Foundry becomes unavailable or misconfigured, AI features stop for your whole organization until you fix them — keep the endpoint reachable and the API key current.

Click Continue. You cannot continue until verification has succeeded.

Step 7: Ready

The wizard saves your choices, sends invitations, and shows three quick links to common next steps:

• Connect your database — opens Admin -> Database Connections so you can add a SQL Server connection.
• Start your first conversation — opens the chat workspace.
• Invite the rest of your team — opens Admin -> Invitations.

After about 1.8 seconds the wizard auto-redirects to the chat workspace. Clicking any of the three quick links cancels the auto-redirect and opens that destination instead.

What can go wrong

• The Continue button stays disabled on the Legal step. You have not scrolled to the bottom of the active document or have not checked its acceptance box. Each of the three documents must be accepted before the wizard advances.
• The Continue button stays disabled on the AI engine step. Verification has not succeeded yet. Connecting your Azure AI Foundry is required to finish onboarding — complete verification by clicking Verify & connect with your Foundry endpoint and a valid API key.
• "Enter both the Foundry endpoint and API key" error on Verify & connect. Both the Foundry endpoint and the API key are required. Fill in any blank field and retry.
• Verify & connect fails (red X on both fields). Strata could not reach your Foundry or could not find a deployment for one of your enabled models. Confirm the endpoint URL is the resource's base URL (not a model-specific URL), confirm the API key has not expired, and confirm a deployment exists for every enabled model using the exact names the panel lists.
• A document fails to load on the Legal step. The error link lets you open the canonical document in a new tab; reading it there satisfies the scroll requirement so you can still check the box.
• "Setup failed" on the Ready step. The final save call to /api/admin/org/onboarding/complete returned an error. The error message is shown in-line; a link lets you continue to Strata and finish setup later from Admin -> Organization Settings. Common causes are network errors and missing permissions on the calling account.
• The wizard does not appear for the first admin. The wizard only opens for accounts with canManageOrgSettings permission or the admin role. If you expected to see it, confirm your role from Admin -> Users (or ask another admin to check). The wizard also stops appearing once onboarding has been completed, or once your org is more than 30 days old — in those cases there is no way to re-launch the wizard, so configure everything directly from Admin -> Organization Settings instead.

Related

• Signing in
• Quickstart: your first conversation
• AI engine — connecting and managing your own Azure AI Foundry
• Troubleshooting and FAQ