> 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/reporting-and-analytics/daily-and-weekly-summaries-are-retiring-rebuild-your-digest-with-the-siit-mcp-server.md). # Rebuild your daily digest with MCP Replace the Daily and Weekly summaries that stop on October 7, 2026 by rebuilding the same admin digest with the Siit MCP server in Slack, Microsoft Teams or email \*Starting October 7, 2026, Siit no longer sends the Daily summary and Weekly summary reports. This guide explains what changes and how to rebuild the same digest with the Siit MCP server, delivered in Slack, Microsoft Teams or by email.\ \* ### What is changing? On **October 7, 2026**, we are retiring the **Daily summary** and **Weekly summary** reports sent to admins in Slack. The **Activity** section of your notification settings is removed at the same time. This includes the toggles that controlled what the summaries contained: **Newcomers**, **Departure**, **Probation end**, **Birthdays** and **Work Anniversaries**. What does not change: * Your request notifications keep working as before. * Your people data (start dates, departures, probation end dates, birthdays) stays in Siit and remains available. * Your analytics dashboards are not affected. ### Why are we retiring them? The summaries had a fixed format, a fixed schedule and were only delivered in Slack. Most teams wanted something slightly different: other metrics, another channel, Microsoft Teams, or email. The Siit MCP server gives you that flexibility today. You decide what goes in your digest, how it looks, when it runs and where it is sent. ### What should I use instead? Use the **Siit MCP server** with the AI assistant your team already uses (Claude, Cursor, Codex, Mistral and more). Your assistant reads your Siit data through the MCP server, writes the digest, and posts it to Slack, Microsoft Teams or email through its own connectors. In practice, you need three things in the same AI assistant: 1. **The Siit MCP connector**, to read your requests and people data. 2. **A connector for your destination**: Slack, Microsoft Teams, Gmail or Outlook. 3. **Scheduled tasks** (optional), if you want the digest to run every day or every week without you. ### Before you start * **Connect the Siit MCP server.** Follow the [MCP server setup guide](/guides/integrations/mcp-server-setup-guide.md). * **Check your permissions.** Your role needs the **Public API** permission enabled in `Settings → Role & permissions → Public API`. The MCP server only sees the data your account can see. * **Connect your destination** in your AI assistant (Slack, Microsoft Teams, Gmail or Outlook). * **Pick where the digest goes.** We recommend a shared channel your whole IT team follows, for example `#it-notifications`, rather than a direct message. ### How to rebuild your digest, step by step 1. Open your AI assistant and make sure the Siit connector and your destination connector are both enabled. 2. Copy the prompt below. 3. Edit the lines marked **\[edit]**: period, timezone, destination and the sections you want. 4. Run it once and review the result. Adjust the wording until the digest looks right. 5. Schedule it. If your assistant supports scheduled tasks, run it every weekday at 9:00 for a daily digest, or every Monday at 9:00 for a weekly digest. Otherwise, save the prompt and run it manually. > **Tip:** Start with the weekly version. Once your team is happy with the format, create a lighter daily version focused on open requests and today's arrivals and departures. ### The prompt Copy and paste this prompt into your AI assistant: ``` You prepare the [edit: weekly] IT support digest for our Siit workspace. Use the Siit MCP tools to READ data only. Never create, update or archive anything in Siit. SETTINGS [edit] - Period: the last 7 days, ending now (for a daily digest: the last 24 hours) - Look-ahead window: the next 7 days (for a daily digest: today and tomorrow) - Destination: post one message in the Slack 1. REQUESTS (tool: list_requests, mode=flat) - New requests: count requests with created_after = start of the period (use per_page=1 and read meta.total). - Resolved requests: count requests with completed_after = start of the period. - Backlog: count requests with status_in = open, then in_progress, then waiting. - Oldest open requests: list the 5 oldest requests not resolved, with ID, title, requester, assignee and age in days. - Top services and top assignees: for requests created in the period, show the top 5 of each. 2. PEOPLE (tool: list_people, per_page=200, go through every page, skip archived people) - Newcomers: job_start_date in the period or in the look-ahead window. - Departures: job_leave_date or last_working_date in the period or in the look-ahead window. - Probation ends: probation_end_date in the look-ahead window. - Birthdays: birthday_date (month and day only, ignore the year) in the look-ahead window. - Work anniversaries: job_start_date (month and day only) in the look-ahead window, with the number of years. Skip people who started this year. 3. FORMAT - Title: "IT digest" followed by the date range. - One short section per block above, in that order, using bullet points. - Show each person as full name, job title and department when available. - Link people and requests to Siit when a link is available in the data. - If a section is empty, write "Nothing to report". - Keep the whole message short and easy to scan. 4. DELIVERY - Send the digest as a single message to the destination above. - Do not ask for confirmation before posting. ``` To change the destination, replace the **Destination** line: * **Microsoft Teams:** `post one message in the IT team channel in Microsoft Teams` * **Email:** `send one email to it-team@yourcompany.com with the subject "IT digest" and the date range` * **Slack direct message:** `send one direct message to me in Slack` To remove a section, delete it from the prompt. For example, remove the Birthdays and Work anniversaries lines if your HR team already covers them. ### What's next: AI actions in Workflows We are working on bringing AI actions into Siit **Workflows**, so you can build and automate this kind of digest directly in Siit, without an external AI assistant. In the meantime, the Siit MCP server is the best way to replace your Daily and Weekly summaries. --- # 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/reporting-and-analytics/daily-and-weekly-summaries-are-retiring-rebuild-your-digest-with-the-siit-mcp-server.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.