Connect an AI assistant
Your AI assistant can read this documentation directly, so it answers from the current content instead of guessing. Add one of the servers below to your client — they use the Model Context Protocol (MCP). Each one covers a different body of content, so add the one you need.
The catalog did not load. Refresh the page to try again.
Loading…
{{server.name}}
{{server.summary}}
{{server.documentCount.toLocaleString()}} pages Not published to this site
- Name
-
{{server.name}} - URL
-
{{mcpServerUrl(server.path)}}
| Tool | What it does |
|---|---|
{{tool.name}} |
{{part.text}}{{part.text}} |
How can we help?
Searching in {{docApp.searchFilterBySpecificBookTitle}}
Searching for:
{{docApp.searchResultFilteredItems.length}} results for:
{{docApp.currentResultsSearchText}}
in {{docApp.searchFilterBySpecificBookTitle}}
Found {{docApp.searchResponse.totalResultsAvailable}} matches. Showing the top {{docApp.searchResponse.results ? docApp.searchResponse.results.length : 0}}. Use a more specific search to further narrow down the results.
No documentation pages match this search, so all content types are shown.
Most matches are in {{docApp.searchDocTypeRescue.best.name}}.
There is no book with the ID "{{docApp.searchBookRescue.bid}}", so the book filter from this link was ignored and results from all books are shown.
You have an odd number of " characters in your search terms - each one needs closing with a matching " character!
-
{{resultItem.title}} {{resultItem.matchedBy === 'semantic' ? 'semantic' : (resultItem.matchedBy === 'both' ? 'keyword + semantic' : 'keyword')}}
{{resultItem.url}}
{{docApp.libraryHomeViewProduct.title || docApp.libraryHomeViewProduct.id}}
{{docApp.libraryHomeViewProduct.description}}
{{group.title || group.id}}
{{group.description}}
The action bar at the top of each request contains the actions you can apply to a request.

- The actions available on a request can be configured within the service they are associated with.
- The supporting workflow that sits behind the request can control the focus of an action when that action is required to be completed.
- Use the Access Control automation to lock or unlock individual actions at any point within a workflow.
- Request settings control which of these options are enabled when an incident is on hold.
Visibility of actions in the timeline
Each time an action is used, an entry is added to the timeline. Each action has a visibility level associated with it that controls who can see the entry in the timeline. This will typically be Team or Customer. The user can select the visibility to decide whether the timeline entry will be customer-facing (Customer visibility) or private to the team working on the request (Team visibility).

While a user can change this at the time of performing the action, the default visibility for each action item is configured in Service Manager settings. To find the default visibility settings, in Configuration Search, enter “visibility”.
- Version {{docApp.book.version}}
- Node {{docApp.node}} / {{docApp.build}}