> 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/introducing-siit.md).

# Announce Siit to your employees

Announce Siit to your employees with ready-to-use templates: a short post for Slack, Teams or Siit communications and a full rollout email explaining why and how to use it

**Before You Start**

When rolling out **Siit** internally, it’s helpful to prepare two levels of communication:

1. **Short announcement** – a quick, friendly post to grab attention and explain the basics.
   * Best used in the **Communication section of Siit** or directly in a **Slack/Teams channel**.
   * Great for a first touchpoint to let employees know “Siit is here.”
   * This can be combined with our guide [*Send your first communication*](/guides/getting-started/getting-started-for-admins/send-communication.md) to show you how to publish it directly in Siit.
2. **Full rollout message** – a more detailed announcement explaining the “why” and “how.”
   * Best used via **company-wide email (all@)** or in **#general / announcement channels**.
   * Ideal when you want to explain the context, benefits, and give employees practical instructions on using Siit.

👉 We recommend sending both: first the **short announcement** to spark awareness, then the **full rollout message** to provide all details.

**Short Announcement (for Siit Communication section or Slack/Teams channel)**

👋 Hi everyone!

We’re now using **Siit**, our new employee support tool, to submit and track all your requests in one place:

* Request access to a software
* Ask for a new computer or accessory
* Report IT issues
* … and much more!

💬 **Why?**

Siit makes it easier to manage requests and ensures nothing gets lost. Once a request is received, it’s tracked and you’ll always be updated on its progress.

🤔 **How to use it?**

You don’t need a new login and you don’t have to leave Slack/Teams:

* Just send a message to **Siit** in Slack/Teams to create a request.
* Or, if relevant, mention **@Siit** in this channel for non-sensitive requests.

That’s it! 🎉 Check out the FAQ below for more tips, and feel free to reach out if you have questions.

**Full Rollout Announcement (for Email or #general announcement)**

**Subject:** New way to submit your requests to 🚀

Hi everyone,

We’ve made a small change in how you should submit questions and requests to the **team**.

From now on, we’ll use **Siit** (<https://siit.io>) to handle your requests. This will help us respond faster, stay organized, and keep you informed along the way.

✅ The good news: You can continue using **Slack/Teams and Email** – no new account is needed.

**How to create a request with Siit**

**On Slack/Teams:**

1. Find **Siit** by searching “Siit” in the search bar.
2. Add Siit as a favorite ⭐ so you can access it quickly.
3. Send your request to **Siit** and follow the instructions.
4. For non-sensitive requests, you can also mention **@Siit** in #.

**Examples of requests you can submit**

* How can I use my education budget?
* Can I get a new computer?
* I’d like to update my bank details
* Access to a software

🙏 Please always use Siit to submit your requests—it helps us keep everything organized and make our daily work smoother.

If you have feedback or questions, let us know. You can also check the FAQ to learn more about Siit.

Thanks,

The Team 💜


---

# 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/introducing-siit.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.