Limosaidentity

PLATFORM / ACCESS REVIEWS

Make every review a meaningful decision.

Review access with a captured scope, clear responsibilities and the context to keep or revoke it. Follow removal decisions through remediation.

Review campaigns, with a defined scopeEXAMPLE WORKSPACE
Review campaigns, with a defined scope in the populated Acme example workspace
Actual Limosa Identity interface · Synthetic example data · Signed in as John Doe. Select image to enlarge.

Review campaigns, with a defined scope

Create campaigns around role and direct entitlement assignments. Select the people and applications in scope, assign reviewers and set a deadline before launch.

WHAT YOUR TEAM CAN DO

01

Give reviewers context

Show the person, assignment and affected access so reviewers understand the impact of their decision.

02

Keep decisions deliberate

Record keep or revoke decisions. Revocation includes confirmation of the affected person and access.

03

Follow remediation

Retain the review decision alongside removal and fulfillment evidence. Launch campaigns manually when your organization is ready.

HOW IT FITS TOGETHER

A workflow you can follow.

01

Scope

People, roles and entitlements

02

Launch

Capture and assign reviews

03

Review

Keep or revoke with context

04

Remediate

Track removal and fulfillment

CAMPAIGN PREPARATION

Define scope before asking for a decision.

Choose the assignments, people and applications to review, assign reviewers and set a deadline. Draft campaigns let administrators prepare the scope before launch captures the review records.

Campaigns launch manually. Reviewers see existing assignment context; keep and revoke decisions are recorded separately from downstream access removal.

Active, draft and completed campaigns in the populated John Doe example workspace
Active, draft and completed campaigns · Actual product interface with synthetic data. Select to enlarge.
02 / THE EVIDENCE MODELFour questions. Four distinct records.
01

Intended access

What should this person have?

Role assignments and configured policies define the desired state.

02

Approval decision

Who authorized the change?

Requests and review decisions capture the human or policy decision.

03

Execution result

What action was attempted?

Provisioning operations and manual tasks record progress and outcomes.

04

Observed access

What does the application report?

Aggregation and read-back provide evidence of the target state.

A recorded approval does not establish that provisioning succeeded. Compare the execution result with observed access.

FULL AI SUPPORT

Your workflow.
Your AI assistant.

Operate and configure Limosa through an MCP-compatible AI assistant. The full management interface is available to AI, with the same permissions, validation and audit trail as the web workspace.

Start with https://identity.limosa.io/mcp. No existing Limosa account needed: sign in and create your workspace when prompted.

Connect your assistant ↗

YOUR NEXT STEP

See governance in practice.

Explore the public demo or bring your applications and governance questions to a guided conversation.