Control & Trust·production

IAM.Identity

Unified identity for users, tenants, roles and product sessions.

Landing Application
IAM.Identity interface
Current public IAM.Identity surface. The screenshot was verified when the documentation was published.

Key capabilities

  • SSO and user-session federation
  • Tenant membership and roles
  • Shared authentication context for IAM products

Role in the ecosystem

IAM.Identity forms the trusted context of the user and organization. Products get the subject identifier, tenant membership, roles and session restrictions, without creating incompatible authorization models for each surface.

Main scenario

sign-in → identity session → tenant selection → product session → scoped action

After authentication, the user selects an available tenant. Product checks session context and applies its own domain permissions. Absent tenant or the role is not replaced by a silent default scope.

Entities

  • User — user identity;
  • Tenant / organization — isolated organizational scope;
  • Membership — connection between user and tenant;
  • Role — set of allowed actions;
  • Session — time-limited login context;
  • Service credential—separate machine identity.

Integrations

Identity context is used by IAM.Core for tool discovery, IAM.Router for quotas and policy lookup, Marketplace for separation of user installations, and IAM.Bot - for tenant administration.

Safety

  • session tokens are not published in the URL and documentation;
  • changing the role or disable the user invalidates active access;
  • service credentials are not replaced by the user session;
  • tenant owner operations require separate verification;
  • audit associates an action with a subject and tenant without revealing the secret.

Operation

Check login/logout, session expiration and refresh, tenant change, disable/enable, invitations and downstream behavior after recall. Required for critical products separate regression for stale session and cross-tenant access.

Limit of responsibility

Identity confirms the subject and scope, but the domain decision remains with the product. For example, the right to enter the Marketplace does not mean the right to manage any hosted agent or change fleet-level settings.