> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/getting-started/quick-start-onboarding.md). # Set up your workspace Configure a working Siit setup on your own: connect chat, HRIS, IdP, MDM and knowledge tools, create inboxes and a service catalog, then open Slack, Teams and the portal {% hint style="info" %} #### What is this guide? This guide is designed to help you **configure your Siit MVP independently**, step by step. By the end of this setup, you will: * Centralize your internal data in Siit * Enable employees to submit requests * Allow teams to process them efficiently * Start measuring activity from Day 1 No advanced configuration required β€” just the essentials to go live quickly and start generating value. {% endhint %} ### STEP 1 β€” Connect Your Integrations ### 🎯 Objective Bring your company data into Siit so requests are enriched with the right context (people, apps, equipment, knowledge). Before employees can submit requests, Siit needs to understand: * Who your employees are * What tools they use * How your organization is structured That’s why we start with integrations. #### 1. Connect your core tools Go to **Settings βš™οΈ β†’ Integration Library** and connect your main tools.
We recommend prioritizing: ### πŸ’¬ Communication tools Slack / Microsoft Teams This is where employees will interact with Siit. ### πŸ‘₯ HRIS Examples: Hibob, BambooHR, Lucca, ADP, Rippling This ensures employee data (department, manager, start date, etc.) is synced. ### πŸ” Identity Provider (IDP) Examples: Okta, JumpCloud, Entra ID, Google Required if you plan to automate access provisioning. ### πŸ’» MDM Examples: Kandji, Intune, Jamf Useful for equipment visibility and lifecycle processes. ### πŸ“š Knowledge Base Notion, Confluence Enables AI replies and knowledge suggestions. ### 🎫 Ticketing / Project Management Jira, Asana, Trello, Freshdesk Optional β€” only if you want to sync requests externally. πŸ’‘ If a tool isn’t natively supported, you can connect it via API or webhooks. #### 2. Choose your source of truth for employee data ### 🎯 Objective Ensure employee data is reliable so routing, automation, and permissions work correctly. Go to **Settings βš™οΈ β†’ People fields** and define the priority source for employee attributes.
This is essential for: * Routing requests by department * Restricting services by audience * Triggering onboarding/offboarding workflows Top commonly used fields: * Department * Manager * Start date * End date * Location * Job title Once completed, check the **Resources section** (People, Apps, Equipment, Articles) to confirm data is syncing properly.
### STEP 2 β€” Structure Your Internal Support Model ### 🎯 Objective Define how requests are organized, owned, and processed internally. Now that your data is centralized, the next step is to design how your teams will operate inside Siit. This includes: * Creating inboxes (who handles what) * Defining services (what employees can request) #### 1. Create your team inboxes Go to **Settings βš™οΈ β†’ Team inboxes**
Create inboxes for the teams handling requests: * IT * HR * Finance * Operations * Workplace πŸ’‘ Keep it simple to start. Many companies launch with just **one inbox** and expand later. This defines ownership and visibility for incoming requests. #### 2. Build your Service Catalog ### 🎯 Objective Design the employee-facing request experience. The Service Catalog defines: * What employees can request * How requests are routed * What information is collected * What SLAs apply ### Key concepts * **Category** β†’ Logical grouping (IT, HR, Finance…) * **Service** β†’ The actual request type (App Access, Equipment, Payroll, Onboarding…) ### Create categories Go to **Settings βš™οΈ**\*\*β†’ Service catalog β†’ Manage categories\*\* Create your main categories (IT, HR, Finance, etc.).
### Create your first services Go to **Settings βš™οΈ**\*\*β†’ Service catalog β†’ Add\*\*
For each service: 1. Give it a clear name 2. Add a short employee-friendly description in the "About" (both used in the employee portal and by the AI for Triage) 3. Choose a category
4. Assign it to the right inbox 5. Set SLAs if needed
6. Build the service form (collect only essential information)
7. Save Your service is now live. ### πŸ’‘ Best Practice Start with your **top 5–10 most frequent requests**: **IT** * App access * Equipment request * Password issues * Onboarding * Offboarding **HR** * Internal mobility * Sick Leave * Time off * Payroll **Finance** * Contract question * etc You can expand later based on Analytics. ### STEP 3 β€” Configure your Communication Channels ### 🎯 Objective Decide where and how employees interact with Siit. Now that: * Your data is synced * Your services are created * Your inboxes are structured You’re ready to enable employee interaction. #### 1. Slack (Prerequisite: Slack integration connected) Add Siit to your Slack workspace and relevant channels. Then go to **Settings βš™οΈ β†’ Channels β†’ Slack**
For each channel, define: ### WHEN Should Siit respond to every message or only when mentioned?
### THEN Choose the behavior: * **AI Reply** β†’ Answers automatically (Pro plan) * **Submit button** β†’ Suggests opening a request * **Auto submit** β†’ Creates a request for every message
### AGENT Select which AI Agent handles the channel.
### REQUEST VISIBILITY Choose whether activity appears: * In public threads * In the private Siit app
*⚠️ Remember that if sent on a public Slack channel, the first message of the requester (before the request is created) will always be visible in the channel.* #### 2. Microsoft Teams Pre-requisite : the [*Teams integration*](/guides/integrations/integrations-communication/microsoft-teams-integration.md) must be done before this step. Once Microsoft Teams is connected to Siit, you can configure how Siit behaves both in the **Siit app** and in your **Teams channels**. If you plan to use Siit in specific channels, start by [***adding the Siit bot to those channels***](https://support.microsoft.com/en-us/office/chat-with-a-bot-in-microsoft-teams-9c7bab5e-b1a2-4e35-801a-80d076e26f3f). ⚠️ the IT Agent is not yet available on the Siit app in Teams, but only on channels.
Go to: **Settings βš™οΈ β†’ Channels β†’ Microsoft Teams** Configuration logic is the same as Slack: * Interaction trigger * Behavior * Assigned agent * Request visibility #### 3. Siit Portal You can also enable the Employee Portal for a structured, self-serve experience. Here is [*how to set up the Employee Portal*](/guides/getting-started/getting-started-for-admins/setup-employee-portal.md) This is ideal if: * You prefer a centralized request hub * You want stronger service catalog visibility You’ve now completed the core configuration needed to launch your Siit MVP. Your data is synced, your support model is structured, and your employee entry points are ready. ### πŸŽ‰ You’re Live! --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.siit.io/guides/getting-started/quick-start-onboarding.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.