> 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/getting-started/quickstart.md).

# Quickstart

Create and resolve your first access request from Slack or Teams in minutes, then turn it into an automated workflow so the next one resolves itself

> Goal: create and resolve your first Access request from Slack/Teams, then turn it into an automated workflow

### <mark style="color:$info;">Minute 0–2:</mark> Install Siit in Slack or Microsoft Teams

{% content-ref url="/pages/3DBkm0PqS2BmkJMziY4P" %}
[Connect Slack](/getting-started/connect-slack.md)
{% endcontent-ref %}

{% content-ref url="/pages/0YlhNc1S76jnuRZ7eClB" %}
[Connect Microsoft Teams](/getting-started/connect-microsoft-teams.md)
{% endcontent-ref %}

### <mark style="color:$info;">Minute 2–4:</mark> Submit your first request

In Slack/Teams, open the Siit app and choose “New request.”

* Pick “App Access” service.
* Submit. You’ll see a request thread and an inbox card created.

<figure><img src="https://451675063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz9xmM8V3atukfr2XaElR%2Fuploads%2FAEAE4YRdiKVbZdf6VLHV%2FCreate%20request.gif?alt=media&amp;token=15433130-04a9-4e42-91b4-f1313745af4d" alt=""><figcaption></figcaption></figure>

### <mark style="color:$info;">Minute 4–6:</mark> Resolve it once manually (see the flow)

* Open the [request](https://app.siit.io/) in the admin console.
* Review the side panel: requester, apps, devices (if any), prior access.
* Add a note, assign to yourself, set status to Resolved.

Outcome: you’ve validated end‑to‑end request flow

### <mark style="color:$info;">Minute 6–8:</mark> Connect your IAM and HRIS

In Settings → Workspace → Integration library, connect one IdP:

* IAM : Okta, Entra ID, Google Workspace, or JumpCloud...
* HRIS : Hibob, Bamboohr, workday...

<figure><img src="https://451675063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fz9xmM8V3atukfr2XaElR%2Fuploads%2F6kbab8lC99BuoHtGTh20%2FCleanShot%202025-10-17%20at%2017.15.52.png?alt=media&amp;token=3bb82a13-8f6f-466a-97d6-7233334c0a61" alt=""><figcaption></figcaption></figure>

### <mark style="color:$info;">Minute 8–10:</mark> Invite your teammates

* Invite your teammate (Settings → Your team → Teammates) and assign them their roles.

### :track\_next: Next steps (recommended)

* Enable the first Workflows → Templates → “Access request – add to group/license.”
* Add Knowledge sources (Notion, Confluence, Slab) with RBAC retrieval and redaction.
* Enable AI Suggest articles for FAQs.


---

# 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/getting-started/quickstart.md?ask=<question>&goal=<user_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.
