Avnology ID
API ReferenceGovernance

Separation of Duties

Static rules that prevent toxic combinations of permissions.

RPCs

MethodPath
CreateSoDRulePOST /v1/governance/sodRules
ListSoDRulesGET /v1/governance/sodRules
DeleteSoDRuleDELETE /v1/governance/sodRules/{id}
CheckSoDViolationPOST /v1/governance/sodRules:check
ListSoDViolationsGET /v1/governance/sodViolations

Base URL: https://<Domain id="api"/>

Authentication: Bearer token with governance.sod:write (create/delete) or :read (list/check).

Rule shape

An SoD rule defines two sets of permissions that cannot both be held by the same identity:

{
  "id": "sod_01H7X3K9Q1",
  "name"






enforcement options:

  • WARN -- violation recorded, Keto write proceeds.
  • BLOCK -- violation recorded, Keto write rejected with AVNOLOGY_AUTH_102.
  • REQUIRE_APPROVAL -- write converted into an access request.

Create a rule

Pre-flight check

POST /v1/governance/sodRules:check lets you test a proposed permission grant against every SoD rule without writing it. Response includes a violations[] array with rule IDs and severities.

Review Campaigns

Periodic access reviews -- managers certify their reports' access.

Privacy

End-user data-export, account-deletion, and CCPA opt-out requests.

On this page