Fit Console into your mail infrastructure, identity services and operator workflows, with controlled customer access for shared installations.
Give customers tenant-scoped views and policy controls within provider-defined limits. Providers retain control over shared infrastructure while customers can handle the operations delegated to them.
Connect supported OIDC identity services, including Microsoft Entra ID, for operator sign-in. Plan identity, roles and traffic attribution together so access matches the organisation and tenant boundaries you intend to enforce.
Connect operational tools through supported REST endpoints and scoped API access. Role and tenant boundaries let integrations work with the data and actions assigned to them; subscriber guides describe available operations.
Connect trusted operator agents or give customer agents tenant-scoped access. Provider automation and customer integrations have separate access boundaries; delegate only the data and operations each agent needs.
Example workflow
Supported operations and access boundaries differ between integrations. For air-gapped systems, identity and automation services must be reachable within the permitted network. Confirm the integration plan before onboarding customers or agents.