NEWFreshservice is now a Ploy integrationSee what shipped
INTEGRATIONSCLOUD INFRASTRUCTURE
Incident.io28 OF 28 CAPABILITIES ASSESSED

Responders and on-call schedules, read into Ploy

Responders and on-call schedules read into Ploy, so who is carrying the pager is part of the access picture.

TYPE · INFRA
Incident.io connectorHOURLY SYNCCAPABILITIES
WHAT PLOY DOES
Sync Incident.io usersEveryone with an Incident.io account lands in Ploy as an identity. Every user is reported active: suspended or deactivated state is not read.
READ
Import on-call schedules and their shiftsThe rota arrives with its shifts, so who is on call is part of the access picture rather than a separate spreadsheet.
READ
Track app-level access to Incident.ioThe access recorded is app level: who can reach Incident.io itself, not what they can do once inside it.
READ
2.1WHAT IT UNLOCKS

Three jobs this connector does on day one

ON CALL

The rota is part of the access picture

Incident.io schedules and their shifts land in Ploy, so a reviewer can see who was carrying the pager at the time rather than reconstructing it from a calendar.

RESPONDERS

Every responder has a record

Incident.io users are synced as identities, so an account that outlived its owner shows up in the same list as every other tool.

REVIEWS

A read-only tool still gets reviewed

Ploy has no write access to Incident.io. A review here ends in a flagged row and a named owner to act on it, not an automatic revocation.

2.3

SETUP

TYPICALLY 10 MINUTES
STEP 01

Connect with least privilege

Grant Ploy a scoped, read-only role in Incident.io to begin with.

STEP 02

Watch the first sync

Identities, roles and keys land in the graph.

STEP 03

Turn on writes

Choose which roles Ploy may grant and revoke, and who approves.

2.4OFTEN CONNECTED TOGETHER
OktaIDENTITY SOURCEGitHubSOURCE CONTROLSlackAPPROVALS
BROWSE ALL 62 INTEGRATIONS

Connect Incident.io, see it in 10 minutes.