For the complete documentation index, see llms.txt. This page is also available as Markdown.

Assist

Assist is the assistant built into your Siit admin dashboard. Ask it a question about Siit and it answers from the documentation. Ask it to do the work and it builds the configuration for you

► Assist can only see and do what you can

This is the whole design. Assist runs on your behalf, with your role and your permissions. It cannot read a request, a person, or an inbox you cannot already open in the dashboard, and it cannot perform a write you could not perform yourself in the UI. Scoping is identical to the Siit MCP.

On top of that, every action that changes your workspace pauses and asks you first. You approve or reject it in the conversation before anything is written.

What you can do

Assist opens on three starting points, each with ready-made prompts.

What it does
Ask it

Build my setup

Creates and edits your configuration: services, service forms, workflows, inboxes, knowledge articles

"Suggest three workflows I should set up based on my requests." / "Create a service catalog based on past requests." / "Create an onboarding workflow."

Ask the docs

Answers product and setup questions from Siit's public documentation, Help Center, and API reference

"Where do I set up my app access policies?" / "How do I set up SSO?" / "How do SLA rules handle business hours?"

Analyze requests

Reads your live request data and turns it into answers, summaries, and drafts

"How many requests last week, by service?" / "Find open requests older than 7 days with no assignee." / "Write my inbox weekly update from last week's requests."

Assist reaches your workspace through the same toolset as the Siit MCP, so anything the MCP can read or write, Assist can too: requests, people, apps and equipment, services, workflows, app access roles, knowledge base articles, and your organization structure. See MCP for the full tool list.

How it works

  1. Open Assist from the top bar of the admin dashboard. It opens in a side panel and the page behind it stays usable.

  2. Ask in plain language, or pick one of the suggested prompts.

  3. Assist works out loud. You see each step as it reads your workspace, checks the documentation, and prepares changes.

  4. Before any write, Assist stops and asks for approval. The conversation stays paused until you approve or reject.

  5. Stop a run at any point with the stop button. Nothing already approved is rolled back.

  6. Conversations are saved. Reopen a past one from the history icon to pick up where you left off.

Where its answers come from

Assist has two sources, and it separates them:

  • Your workspace, for anything about your own requests, people, and configuration.

  • Siit's public knowledge, for anything about how the product works: docs.siit.io, help.siit.io, and the API reference at developer.siit.io.

Nothing from your workspace is sent to the documentation, and nothing from the documentation is treated as configuration.

Attachments

Drop a file or a screenshot into the conversation and Assist reads it. The common case is migration: paste a screenshot of your current setup in another tool and ask Assist to build the equivalent in Siit.

Common workflows

  • Trial day one : "Create a service catalog based on my past requests" turns an empty workspace into a working catalog in one prompt.

  • Migration : screenshot your existing intake form from your old tool and have Assist rebuild it as a Siit service with the same fields.

  • Find the automation gap : "Which services get the most requests but no automation?" then have Assist draft the workflow it just recommended.

  • Weekly reporting : "Write my inbox weekly update from last week's requests."

  • Setup questions without a support ticket : "How do SLA rules handle business hours?" answered from the docs, in context, in the product.

Tips

  • One task per conversation. Assist replays the full thread on every turn, so a long conversation that has drifted across three topics is slower and less accurate than a fresh one.

  • Say which object you mean. "Update the Onboarding workflow" beats "update the workflow."

  • Read the approval prompt before approving. It names the exact action and its parameters.

  • When Assist is wrong about the product, it is usually because the documentation is wrong. That is worth reporting.

Availability

Assist is included on all plans, with a fair use policy applied per account. There is no AI add-on and no per-seat AI upgrade. If you hit your fair use limit, contact your Account Manager and they will move you to the right plan.

Coming soon. Custom playbooks and instructions per workspace, and connecting external MCP servers so Assist can act in your other tools.

Last updated