Machine access

API Keys

Manage server-to-server access with scoped API keys, rotation workflows, revocation controls, and audit evidence.

Scoped access

Create keys for specific services or operational tasks so integrations receive only the access they need.

Controlled lifecycle

Create, rotate, expire, and revoke credentials from a central administrative experience.

Safe display model

Credential material is treated as sensitive and should only be handled through secure creation and rotation flows.

Audit-ready operations

Key lifecycle events can be reviewed by operators and exported for compliance investigations.

Business outcomes

What teams should be able to achieve with this capability.

Support backend automation without sharing human accounts.

Reduce long-lived credential risk with rotation and expiry discipline.

Give security reviewers a clear machine-access governance story.

Who this helps

Public overview pages are written for evaluation and security review.

Product leadersSecurity reviewersPlatform engineersHealthcare and SaaS teams

Public documentation security posture

This public page intentionally avoids internal endpoint inventories, secret names, infrastructure-specific values, role identifiers, cryptographic tuning constants, and tenant-specific examples. Detailed implementation guidance belongs inside the authenticated dashboard where examples can be scoped to the signed-in tenant.