Start Here
Start with identity and ownership, not a secret copied into a configuration file. Every B5 integration should be anchored to an enterprise, project, application, environment, audience, scope set, owner, and callback policy.
Create the integration record
Continue
Implementation steps
Control details
Enterprise Tenant
The enterprise tenant is the root customer identity used for policy, licensing, entitlement, audit, and evidence partitioning.
Project
A project groups applications and environments around one bounded product, service, or integration objective.
Application
An application receives its own identity, credential lifecycle, callback rules, and evidence trail.
Environment
Credentials and data never cross environment boundaries. Test Mode must have no production reach.
Audience Scopes
Audience limits where a credential is accepted. Scopes limit what it can request. Both are enforced independently.
Owners Callbacks
Every integration needs accountable owners, approved redirect and webhook destinations, and a documented incident contact.
Record these values before a credential is issued
| Object | Required values | Why it matters |
|---|---|---|
| Enterprise | Tenant ID, legal customer, owners | Root identity, commercial boundary, and evidence partition. |
| Project | Project ID, product/workload, security owner | Bounds applications, policy, and deployment ownership. |
| Application | Application ID, type, audience, scopes | Creates a distinct software identity and credential lifecycle. |
| Environment | Development, test, staging, production | Prevents credential and data crossover. |
| Callbacks | Exact redirect URIs and webhook targets | Prevents open redirects and unapproved event delivery. |
Continue to a real implementation page
Every destination below is a published B5 page with additional guidance or a concrete implementation surface.
Talk to a human.
Get architecture guidance, Test Mode access, integration review, or help choosing the right B5 identity and authorization pattern.