Map & correlate
Choose stable identifiers, map source attributes and link accounts to the right governed identities.
Standards & custom · CONNECTOR GUIDE
Configure HTTP operations and isolated request/response transforms.
HOW IT FITS TOGETHER
Import observed accounts and access, then use configured policies and approved requests to drive supported changes.
Mapped API resources
Authenticate · read · normalize
Inventory · policy · review evidence
Configured target operations execute after the relevant policy and approval steps. Subsequent reads provide observations of the result.
Conceptual architecture, not a product screenshot. Approval, execution and observed access remain distinct.
SUPPORTED FEATURES
These operations are configurable. Enable only the operations supported by your target and validate their mappings.
Read the connector’s supported records into Limosa.
Create accounts using required target attributes and mappings.
Update the account attributes supported by this connector.
Apply the provider-specific enable or reactivation operation.
Apply the provider-specific disable, suspension or unlicensing operation.
Apply the provider-specific removal or deprovisioning operation.
Add a supported direct entitlement membership.
Remove a supported direct entitlement membership.
PREPARE YOUR CONNECTION
Configure endpoints, authentication, paginated reads, mappings and any write operations. Custom JavaScript runs in the isolated transform runtime.
Application credential
Configure the application connection, credentials, account schema and operation mappings in the application editor.
Store credentials through the application’s credential controls or an approved external secret reference. Confirm roster visibility and review import policy before the first full import.
FROM CONNECTION TO GOVERNANCE
Choose stable identifiers, map source attributes and link accounts to the right governed identities.
Check imported records and memberships. Resolve unexpected gaps before relying on the connection for governance.
Configure supported writes, test the target behavior and follow provisioning history separately from approval decisions.
FULL AI SUPPORT
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.
YOUR NEXT STEP
Explore the public demo or bring your applications and governance questions to a guided conversation.