For administrators
For the person who runs Varqeni for your team: access, approvals, the kill switch and the autopilot policy.
- Single sign-onLet people sign in to Varqeni with Microsoft Entra ID, Okta, Google, GitLab or any OpenID Connect provider.
- Audit logWho did what in Varqeni: pages, approvals, sign-ins, settings, rules, tickets and dashboards, in one list.
- SCIM provisioningLet Entra ID or Okta add, change and remove the people and teams in Varqeni.
- Set up the status pageChoose what the people who use your services see: a title and components, each with the systems behind it.
- What Varqeni may do on its ownEvery action Varqeni can take on each system, in plain words: runs on its own, asks first, or analyze only.
- The weekly briefOne message a week for leaders: incidents, how fast they were handled, fixes, model use and gaps.
- Use Varqeni from Claude, Cursor or Copilot (MCP)Let a coding assistant read Varqeni's incidents, timelines, system health and who is on call.
- Add or remove peopleSign-ins come from your identity provider. What each person may do is set in Users and access.
- Approve a fix on the Varqeni hostApprovals run on the machine that runs Varqeni, with the approver's name.
- Stop every action at onceThe kill switch stops all fixes, by a person or the autopilot, immediately.
- Silences and maintenance windowsHold pages back on purpose while you work on a system, for a set time, and have Varqeni say so in every incident it covers.
- Change the autopilot policyThe autopilot policy is a reviewed file on the host. Changes are checked before they take effect.
- Set up on-callWrite the rota, the escalation steps and who may approve fixes. Varqeni reads the file every 15 seconds.
- Custom operations: write a runbookA runbook turns one cause into one fix Varqeni already knows, with a person approving each run or, after its own trials, on its own.
- Schedules, overrides and escalation policiesSeveral on-call schedules, people covering for each other for a while, and the escalation each page follows, chosen by system, cause and source.
- Choose who is toldNotices go to the Teams channel set up for your pipeline. The policy can also tell nobody.
Still stuck? Contact support or email info@fortisdatagroup.com.