After this article
You’ll be able to connect incident.io to Lumos to see users, on-call schedules, and who is currently on call.Capabilities
- List users. Lumos reads the users in your incident.io organization for visibility and Access Reviews.
- List schedules. Lumos reads the on-call schedules defined in incident.io.
- Find schedules. Lumos maps which users are associated with which schedules, so Access Reviews show schedule membership.
- Validate user on-call. Lumos can check whether a user is currently assigned to a specific schedule.
Required plan and roles
- incident.io access: an administrator who can create an API key in incident.io.
- API key: enter the key shown on the Lumos connection card.
Read-only access vs provisioning
Is read-only possible? Yes, and it’s the only mode this connector offers. The connector only lists users, schedules, and on-call status, there is no capability to create, update, or remove anything in incident.io. What read-only requires. The same API key described above, generated by an administrator in incident.io, then follow the steps below to connect. Watch out for. There is no provisioning variant of this connector. Any user or schedule changes have to happen in incident.io directly, since this connection only ever reads data into Lumos.Instructions
Phase 1: Connect in Lumos- Find the incident.io card in your Lumos integrations.
- Enter the API key shown on the connection card.
- Click Connect.