Permissions and the API
Who may do what
| To | Permission | Held by |
|---|---|---|
| See services in your units | service.read | Agent, Viewer, Auditor, Service Manager |
| Edit a service's record and the accounts using it | service.write, or being its owner | Service Manager |
| Choose an account's change approvers and notice contacts | service.approvers | Service Manager |
| Set a service's status by hand | service.status, or being its owner | Service Manager |
| Add services and offerings, change a code, the status or what it is an offering of, and delete unused ones | service.settings | Service Manager |
A permission held in one of the service's units is enough. Administrators hold them all. Give them to your own roles under Roles.
For AI assistants and the API
With the plugin on, tokens can get itsm:read and itsm:write (Settings → API tokens). AI
assistants get tools to list and read services (also as they were on a date), to see the people, teams and units a
service can have, to add and change services, the accounts using them and accounts' approvers (and who could approve on a given date),
to read and set the service a case is about, the report by service, to set a service's status by hand, and to read and
change its windows and freezes (and check a planned time against them), within the same permissions. The API is
described in building a plugin.