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 change these choices later from Organization: your organization's name, industry and overview in Profile, the step 2 defaults in Member defaults (audit log retention is in Data and privacy), models in Models, extensions in Extensions, and your Foundry in AI engine.

Note

This wizard runs for the first admin of any new organization, whether the org was created for you by Kronisys or you started it yourself through the self-serve trial (a card up front, a 14-day trial with seat and credit limits, and your own Azure AI Foundry). Either way, the first admin lands here to finish setup. See Billing for how trials and seats work.

Layout

Down the left of the page, a rail shows the seven step names: Welcome, Privacy, Capabilities, Teammates, Legal, AI Engine, Ready. The active step is highlighted, and under each name a short line says where it stands (for example Now, Skippable, 3 of 3 signed or Connected). You can click back to any step you have already reached. 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, and the line beside it says what is still missing (for example Choose an industry to continue).
• Need help? support@kronisys.com (top-right) — opens a pre-addressed support email.

The wizard is completed one step at a time. Three steps have a requirement before Continue enables: an industry on Welcome, at least one chat model on Capabilities, and all three documents on Legal. Privacy and Teammates can be passed as they are (on Teammates the button reads Skip for now → until you enter an address), and AI Engine can be finished without a Foundry (see step 6). Legal acceptance is also enforced server-side: the final save call is rejected unless all three documents have been accepted.

Your progress is kept in this browser as you go, so if you close the tab or reload, the wizard reopens on the step you were on, for up to seven days. Two things are not kept and are asked for again: the legal acceptances and your Foundry API key.

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 data from connected tools — include content pulled by any connected tool (query results, email text, 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. A model Microsoft retires drops out on its retirement date, and Strata moves anything that used it to its replacement unless you turn off Move to the replacement when a model retires under Organization -> Models. 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.) Models that are retiring are not offered here; they stay in the Model Catalog.

You can change the enabled set anytime later from Organization → Models → Manage models, which opens the 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 -> Apps -> 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.

On a self-serve trial, the step says how many people the trial covers (you included) and offers only as many rows as there are spare seats; when the trial covers only you, it says so and points to Organization -> Billing to add seats. On a paid plan, it says how many seats the plan covers and how many are still free; you can invite past that, and the step says by how many and that the extra seats are added to your next invoice.

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 Organization -> Roles. You can also continue without adding anyone and invite teammates afterwards from Organization -> Users with Add user.

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 says so, with Retry and a link that opens the published document at strata.kronisys.com/legal/<slug> in a new tab for reading. The checkbox stays locked until the document shows in the panel, so Retry is the way to accept it.

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. Everything else stays in your Foundry — no prompt, data, or content from those features is 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 (it turns on once both fields hold text). Strata calls your Foundry to confirm reachability and that the deployments for your enabled models exist. On success the button gives way to Connected to your Foundry with Disconnect, the line in the footer says Foundry connected · AI turns on when you finish, and the button at the bottom reads Finish setup →. If Strata reached your Foundry but some of your models are not deployed, or it could not confirm them, the note says Connected to your Foundry and names each deployment still to create. If it could not connect, the note says Couldn't connect to your Foundry and why (the endpoint, the key, the network). Either way the button reads Try again.

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 Finish setup →. You can also finish before your Foundry is connected: the button then reads Finish without AI →, and AI features stay off until you connect your Foundry from Organization -> AI engine.

Step 7: Ready

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

• Start your first conversation — opens the chat workspace. If your Foundry is not connected yet, this link is Connect your AI engine instead, and opens Organization -> AI engine.
• Invite the rest of your team — opens Organization -> Users with the Add user form open.
• Connect your tools — opens Settings -> Apps, where you can connect SQL Server, OneDrive or Outlook. Shared SQL Server connections for the whole organization are added under Organization -> Database connections.

On a self-serve trial, the step repeats what the trial covers and when your card is charged.

After about 1.8 seconds the wizard moves on to the chat workspace. Clicking any of the three quick links opens that destination instead. If any invitation could not be sent, the step lists each one (the address, or Unknown address, and why) and stays put so you can read it; you can send them again from Organization -> Users.

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.
• Verify & connect stays disabled on the AI engine step. It waits for both the Foundry endpoint and the API key; fill in both.
• "Couldn't connect to your Foundry" on the AI engine step. Strata could not reach your Foundry or it refused the key. Confirm the endpoint URL is the resource's base URL (not a model-specific URL) and that the API key has not expired, then click Try again.
• "Connected to your Foundry" with a list of deployments. The endpoint and key work, but those models are not deployed in your Foundry project. Create each deployment with the exact name shown, then click Try again, or finish now and deploy them later.
• A document fails to load on the Legal step. Click Retry. The new-tab link is there for reading only: the box can be checked once the document shows in the panel.
• "Something went wrong" on the Ready step. The final save call to /api/admin/org/onboarding/complete returned an error. The reason is shown in-line, with a link to continue to Strata and finish setup later from Organization. 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 Organization -> 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 Organization instead.

In your language and on a phone

The whole wizard is in the language you chose in Strata: its seven steps, the rail and the line beside Continue, the trial and seat sentences, the legal step's frame (the documents themselves are in English), every answer of the Foundry check and the Ready step, with counts, dates and amounts written the way your language writes them (Bengali and Marathi in their own digits). The names of products and models, the SQL words of the database permissions (INSERT, CREATE and so on) and your Foundry's deployment names stay as written.

On a phone or a narrow window, the rail becomes a strip across the top that shows the name of the step you are on and scrolls sideways to the others, and the line that says what Continue is waiting for sits on its own line above the buttons.

Related

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