How It Works

From shadow AI to governed AI in four steps.

Every employee AI request flows through the gateway — identity-bound, policy-checked, logged, and routed to a centrally governed provider.

Setup to governance

Four steps, one governed path.

Connect identity, define policy, route requests through the gateway, and govern from the record.

1Connect identity 2Define policy 3Route through the gateway 4Audit & govern
STEP 01

Connect identity

Integrate LDAP and Active Directory for user and group management, and OpenID Connect single sign-on, including Microsoft Entra ID configuration.

OpenID Connect LDAP / Active Directory Groups & roles
STEP 02

Define policy

Control model access by user and group, including token limits, set budgets at organizational, group, and user levels, and configure the sensitive-data policies applied before requests reach AI providers.

Model access Data controls Budgets
STEP 03

Route through the gateway

Employee requests pass through policy enforcement and sensitive-data controls, then route to an approved, centrally governed provider.

Policy enforcement Sensitive-data controls Approved model
STEP 04

Audit & govern

AI usage, policy decisions, and relevant administrative activity are recorded and searchable — ready for export, retention settings, and configurable audit-event forwarding.

Searchable audit Export & forwarding Reporting
The request path

What happens to a single request.

Select a stage to follow one request from identity to an approved provider. Illustrative — not a live operational trace.

Employee request
Approved provider

Your directory verifies the user, role, and permissions.

Get started

Let your workforce use AI — on your terms.

See how Frame360 brings employee AI usage under policy, audit, and budget — in an environment you control.