Documentation

Guided setup & features

Everything to go from zero to governed identities in under an hour — plus the full feature reference and the Idenzo public API.

Concept documentation for the Idenzo rebuild. Endpoint shapes mirror public industry conventions so the guide stays realistic.

Guided setup

1

Create your workspace

Sign up at /signup, verify email, and name your workspace. Enable 2FA when prompted — admins can enforce it for everyone later under Settings → Security. The workspace URL becomes your identity: https://<workspace>.idenzo.io.

2

Connect your identity provider

Idenzo reads your directory through the IdP you already run. Supported out of the box:

  • Google Workspace — OAuth admin consent; scope admin.directory.user.readonly minimum for discovery, read/write if you want provisioning.
  • Microsoft Entra ID — delegated Graph permissions (User.Read.All, AuditLog.Read.All); admin consent on first login.
  • Okta — classic API token with okta.users.read; scoped least-privilege service user recommended.

Go to Settings → Identity providers → Connect, choose your IdP, and finish the consent screen. Users sync within minutes; the initial run imports profile, department, employment status, and group memberships.

3

Ingest SSO & audit logs

Discovery of shadow apps starts with SSO activity. Enable log ingestion per source:

  • Google Workspace audit logs — one toggle; Idenzo back-fills the last 30 days and keeps a rolling window.
  • Entra ID sign-in logs — requires Entra ID P1/P2 on your tenant.
  • Okta system log — user.authentication.sso events are consumed via the same API token.
  • Idenzo Browser Extension — optional; detects usage of apps outside your SSO. Deployable by policy (Chrome/Edge).
4

Review your first discovery

Within an hour, Discovered apps fills with every SaaS your people touch. Each app gets a risk level (Cloud Confidence Index-style scoring), category, and status. Classify: Approved → integrate, Unapproved → monitor or block. Convert an app to Integrable to pull accounts, licenses, and usage; convert to Trackable for manual tracking.

5

Set policies once

Under Governance → Policies, start from the least-privilege templates per department and edit to taste. Three policy types:

  • Provisioning — which apps a new hire gets by department, location, and role.
  • Review — scheduled access reviews with yes/no + short-answer questions.
  • Response — what happens on triggers: leak detected, account dormant 30 days, agent without owner (suspend, notify Slack/Teams, open a ticket).

Every enforcement is previewed before it runs. Nothing acts on your stack without your approval flow.

6

Govern agents & devices

AI agents (Copilot Studio, Claude workspaces, Gemini apps) appear in the Agents inventory with owner, permissions, and blast radius — set an owner policy so nothing is unowned for more than 24 hours. Devices sync from your MDM (Intune, Jamf) as an external data source; wipe and remote-lock are gated by admin role.

Done? Your workspace now runs the continuous loop: discover → classify → govern → monitor → respond. The rest of this page is the feature reference.

Features

Identity & app discovery

A complete inventory of human, machine, and AI-agent identities plus every SaaS they touch. Sources combine IdP directories, SSO/audit logs, browser signals, and native integrations. Risk scoring, compliance attributes, and categories arrive pre-labeled; CSV export included.

Access governance

Attribute-based provisioning (department × location × role), scheduled access reviews with owner responses tracked in-product, approval workflows for access requests, and a full audit trail on every action — human or autonomous.

Credential monitoring

Idenzo watches breach corpora for your corporate domains. On a hit: identify affected accounts, enforce MFA, block sessions, and open an incident — median leak-to-block 12 seconds in benchmarked tenants.

License optimization

Per-app license counts (assigned/unassigned), underutilized-account detection (30-day inactivity), shadow accounts, and subscription-renewal alerts. One-click downgrade or reclaim flows into the offboarding workflow.

AI agent governance

Agents from Microsoft Copilot Studio, Anthropic Claude workspaces, and Google Gemini apps are governed as first-class identities: owner assignment, permission scoping, blast-radius view, shadow-agent alerts with creator context, and usage-based cost signals.

Integrations

350+ native connectors across IdPs, HR, MDM, finance, CRM, dev tools, and AI vendors — plus a no-code builder for apps without public APIs. Webhooks and Slack/Teams notifications ship with every plan.

Public API

Authentication

OAuth 2.0 client_credentials. Create an API pair under Settings → Developer → API credentials (the secret is shown once). Tokens live for 1 hour.

POST https://api.idenzo.io/v1/oauth/tokens
Content-Type: application/json

{ "grant_type": "client_credentials",
  "client_id": "idz_live_xxx",
  "client_secret": "••••••" }

Use the returned access_token as a bearer token.

Endpoints

EndpointWhat it does
GET /v2/identitiesList/filter identities (type, department, status, last-active). Paginated.
POST /v2/identitiesCreate an identity; supports bulk import up to 1,000 rows.
PATCH /v2/identities/{id}Update profile fields, status, or app assignments.
GET /v1/appsIntegrated apps with accounts, spend, and license data.
GET /v1/apps/discoveredDiscovered (shadow) apps with risk level and status.
GET /v1/devicesDevice ledger; POST /v1/devices/search for filtered queries.
GET /v1/agentsAI-agent inventory incl. owner and blast radius.
POST /v1/webhooksRegister event sinks (leak.detected, agent.created, review.due).

Limits & permissions

Guideline of 4 requests/second per workspace. API keys inherit the permissions of the issuing admin — mint a read-only admin for reporting keys. All responses are JSON; cursors paginate lists.

Need a connector that isn't listed? The no-code builder records the workflow once and Idenzo schedules it — see Integrations → Build.