Repository access
Alex · inherited grant
Jo · deactivated Session ended
Carry that authority into agent work. Federate sign-in, provision groups and remove access through the identity systems you already operate.
Connect an identity provider so enterprise sign-in can establish the employee identity.
Your identity provider owns membership. Fabriq resolves the corresponding organization, team and member grants when an agent acts.
Alex · inherited grant
Jo · deactivated Session ended
Priya · team grant
Member override No delete scope
Okta and Microsoft Entra ID support sign-in, provisioning, groups and offboarding. Other OIDC providers support sign-in.
Grants follow organization, team and member settings, including per-user overrides. These access grants are distinct from a policy’s configurable fallback.
The platform admin plane has separate authentication, TOTP and recovery codes.
Okta and Microsoft Entra ID support sign-in, provisioning, groups and offboarding. Other OIDC-compatible providers support sign-in.
Organization, team and member grants bound tool access. Agent permissions and access assignments are configured separately.
Platform administration uses a separately hardened authentication plane with TOTP and recovery codes.
Session revocation takes effect immediately. Disabling an agent covers the non-human side of access.
People and groups are provisioned from the IdP and removed through the same lifecycle. Fabriq applies grants to those identities rather than creating an independent source of membership.
Revocation ends the session immediately instead of waiting for token expiry. Removing group membership also removes the authority that group supplied.
No. An agent acts within the signed-in user’s identity and its own scope. It cannot create authority that the person does not hold.