Enterprise
Use this section for organization governance, project boundaries, roles, enterprise security, and operational notifications.
Use this section for organization governance, project boundaries, roles, enterprise security, and operational notifications.
Availability
Enterprise guides can vary by customer, environment, and rollout stage. Treat this section as the governance map, and confirm account-specific availability with your AnyInt contact before depending on a feature in production.
Choose by responsibility
| Responsibility | Page | Outcome |
|---|---|---|
| Understand the enterprise control layer | Overview | Know how governance fits on top of the public API platform |
| Separate usage by organization or project | Organizations and Projects | Decide how teams, environments, workloads, keys, and usage views should be separated |
| Decide who can manage people, keys, usage, or billing | Roles and Permissions | Assign admin, project, member, and finance responsibilities |
| Plan SSO, sessions, and access controls | Security and SSO | Prepare identity provider inputs, login policy, and rollout testing |
| Send operational events to email or webhook targets | Webhooks and Notifications | Route billing, usage, member, key, and security events into your systems |
Who should read this
| Reader | Most relevant pages |
|---|---|
| Platform or IT admin | Overview, Organizations and Projects, Security and SSO |
| Engineering manager | Roles and Permissions, Webhooks and Notifications |
| Security owner | Security and SSO, Roles and Permissions |
| Finance owner | Roles and Permissions, Webhooks and Notifications, Billing and Invoices |
Enterprise rollout checklist
Before relying on enterprise controls in production, confirm:
- Which organizations and projects should exist.
- Which users need admin, project owner, member, or finance access.
- Which API keys belong to each team, project, or environment.
- Whether SSO should be optional, required, or rolled out gradually.
- Which operational events must go to humans by email and which should go to systems by webhook.
- Who owns billing, renewal, and incident-response contacts.