LimosaIdentitybox

Who has access?
Ask your own assistant.

Connect Limosa Identitybox to the AI assistant your team already uses. Ask why someone has access, compare the answer with your team’s policy, and prepare a review in the same conversation.

Explore the populated demo without signing in. Create your own workspace to configure and try changes.

Why bring your own assistant? →

An employee badge branches toward a folder stamped with a checkmark and a locked ledger. A speech bubble with a sparkle sits above the fork.

An access question, traced

Why can Maya open the finance workspace?

Start with the person. Follow the account to the assignment that grants access, then check what the application reports.

Explore the inventory →
Example access record
Person
Maya Chen Finance analyst
Assignment
Finance reporting Granted through her analyst role
Observed access
Workspace reader Membership reported by the application

Platform capabilities

From the first account to the next review.

Explore the controls your team uses as people join, change roles and leave.

Explore roles and policy →

SEE THE WORK, STEP BY STEP

A decision is the beginning.
Follow what happens next.

Set who can request access and which roles they can request. Follow each request through approval, fulfillment and verification.

Access request configuration
Access request configurationSynthetic example workspace · View full size
01

Request

A person asks for business access

02

Approve

Assigned reviewers decide

03

Fulfill

A connector or owner carries out the change

04

Verify

Target observations establish the result

Conceptual workflow. Approval, successful execution and observed access are separate evidence.

Follow the access request walkthrough →

ENTERPRISE CONNECTIONS

Workforce context.
Application reach.

Bring HR sources, directories and business applications into governance. See the supported inventory and write operations for each connection.

Explore the connector catalog →

BRING YOUR OWN ASSISTANT

Keep the tools your team already knows.

Keep the assistant and model your team uses. Connect Identitybox alongside your policy library and project tools to investigate access with the business context already at hand.

See how a reviewer uses these connections →
What connects to your assistant?
Your language modelThe LLM available in your chosen client
Your dataPolicies, documents and team knowledge
Your assistantOne conversation
Your applicationsTickets and project tools you connect
Limosa IdentityboxAccess evidence and actions via MCP

Each connected source uses its own permissions. You choose which connections to authorize.

01 / CONFIGURE

From intent to configuration.

“Help me connect our HR source and map worker records to identities.”

Your assistant can discover the connector, gather settings, validate configuration and test the saved connection before importing.

Explore the connectors →
02 / OPERATE

Get governance work done.

“Show my pending access reviews and the context for each decision.”

Your assistant can retrieve your assigned work and submit permitted decisions through the same governed operations as the workspace.

Explore access reviews →
03 / INVESTIGATE

Follow the evidence.

“Find failed provisioning operations and help me understand what happened.”

Your assistant can read task progress and operation histories, then help you distinguish an approval from the actual target outcome.

Explore the architecture →

Illustrative requests, not a transcript or autonomous execution guarantee. Available actions follow the connected user’s permissions and the application’s configured capabilities.

Explore full AI support and client setup →

START WITH YOUR AI ASSISTANT

One URL.
Your first workspace.

Add Identitybox to your assistant, then sign in when prompted. No existing Identitybox account or workspace ID needed.

Use an email magic link, or Google or GitHub when offered. Create or choose your own workspace and approve the connection. Your assistant can then help you configure the platform.

Choose your assistant →

REMOTE MCP SERVER URL

For demo and testing only. Use synthetic data and review the demo terms before connecting.

https://identity.limosa.io/mcp

  1. Add the URLUse a remote MCP connection with OAuth.
  2. Sign in & choose a workspaceNew here? Create your workspace during sign-in.
  3. Approve & start a conversationTry: “Help me set up my first application.”

An account is created through sign-in; data access always requires authentication and your explicit approval. Assistant plans and organization policies may restrict custom connections.

An architectural loop of glass and ceramic stations illustrating ideas, AI-assisted building, inspection and iteration
Original AI-generated concept illustration · development and iteration

AI IN HOW WE BUILD

Built with AI.
Improved continuously.

AI is the main driver behind our fast development cycles.

We use AI to turn product ideas into implementation, tests and improvements. Human direction, review and validation remain part of the process.

The result is a product that can evolve quickly around real governance needs. Follow the release journal to see the concrete capabilities each update brings.

See what we’re building →

Evaluating Identitybox

Plan your pilot.

Choose a source, a team and an access workflow to test together.

YOUR NEXT STEP

See governance in practice.

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

How would you like to try Identitybox?

This hosted environment is for demonstration and testing only. Use synthetic data and isolated test systems. Read the demo terms and conditions before continuing.

RECOMMENDED

Use your own AI assistant

Work in the assistant you already know. Add the MCP server below, then sign in to choose or create your workspace.

See assistant setup instructions →

NO SIGN-IN NEEDED

Explore the web interface

Browse sample identities, roles and access reviews in a populated workspace.

Open the web demo ↗