Federation and local auth
Portal supports passkeys, password fallback policies, Portal-native OIDC for first-party apps, and tenant-managed upstream SAML or OIDC sign-in.
Cadres Portal
Enterprise-grade identity and IGA without legacy sprawl.
Portal is the Cadres identity layer for workforce access, federation, provisioning, governed collaboration, and lifecycle controls. It is designed for teams that want enterprise-grade identity administration without scattering policy, approvals, and audit history across separate tools.
Federation
SCIM
Guest access
IGA
Migration tooling
Portal Scope
Built for the identity work teams actually own.
Provisioning and app access
SCIM setup, managed applications, client credentials, and tenant-safe application controls live in the same admin surface.
Governance that can execute
Access bundles, requests, approvals, grants, access reviews, and JML flows are durable runtime features, not presentation-only screens.
Migration without overclaiming
Portal includes workspaces, inventory, compatibility assessment, and bounded cutover support for migration away from incumbent identity estates.
Why Teams Start Here
Portal answers the executive question and the operator question at the same time.
01
Who can get in?
Centralize federation, sign-in policy, and service credentials on a tenant-scoped platform that understands context and assurance.
02
How does access move?
Bundle-based requests, approvals, grants, reviews, and JML runtimes turn identity governance into a system of record.
03
How do we leave incumbents cleanly?
Migration tooling gives operators a truthful boundary for inventory, assessment, cutover planning, and post-cutover evidence.
Evaluation
Evaluate Portal directly, or alongside Keystone and Meridian.
Portal is included as the identity layer for the other Cadres products. Broader workforce IdP or IGA rollout is where Portal becomes its own dedicated evaluation.