Review change requests

Review change requests

Change requests are part of the same early access as maintenance programs. Reach out to your Slite contact to have them turned on for your workspace.
Every change the Slite Agent suggests through a maintenance program arrives as a change request. Nothing changes in your docs until someone approves it.
A run groups its suggested changes by topic into change requests, and a request can cover several docs. A doc can also have several change requests open at once, for example from separate runs or from requests created through the API or MCP.

Assignment & notifications

For programs set on docs, Slite assigns each change request to the admin or maintainer who knows its subject best, based on what the Agent read in your docs and sources. If none of them knows it well, it goes to the closest fit. Workspace programs, such as Check docs most used by AI, assign each change request to the doc's owner instead.
When a run finishes, everyone with change requests assigned to them gets one notification with how many there are, so the inbox stays readable. You’re also notified when someone hands you a change request, when a change request is created for you through the API or MCP, and when you’re mentioned or someone replies in one you’re part of.


Review a change request

Each change request comes with an approval card. From it, you can:
    Preview the changes as a diff, including title changes.
    Apply each set of changes on its own.
    Reject a proposed change if it's not needed or needs improving.
    Reply to the Agent to ask a follow-up question.

Permissions

You review and apply changes with your own permissions. If you don't have access to a doc a change request touches, the approval card shows a restricted row instead of the body and preview, and its pending actions become a Request access button.
When you reply to the Agent in a change request, it answers with your permissions.

Who can see a change request

A change request is shared with its assignee, its audience, and, for program runs, the maintainers who took part in the run. People outside that group can’t open it. Audience members must be active members with Agent access who can read every doc the request edits.
Maintainers see the runs and change requests they took part in. Someone who joins a program later does not see its earlier runs.
Over the API, the audience is set with audienceUserIds when the request is created. In the app, it is set from the controls at the top right of the request.

Create change requests yourself

Change requests don't only come from maintenance programs. Your own routines or external systems can create and read them through the public API or the Slite MCP.