Try a product name, choose another category or clear the filters. SCIM, CSV and Web services offer paths for custom integrations.
Capabilities depend on the provider edition, administrative permissions and configured scope. A listed connector does not imply vendor certification or endorsement.
A CONNECTED PROCESS
From a worker record to an accountable decision.
Joining systems is the starting point. Connect their data to policy, human review and evidence of what actually happened.
01
Import
Read HR records and application inventory through configured connections.
02
Correlate
Link accounts to governed identities using matching rules or manual review.
03
Decide
Evaluate configured roles and lifecycle policies; route requests for approval.
04
Deliver & verify
Run supported provisioning or manual fulfillment, then follow outcomes and observations.
Conceptual workflow. HR import, identity refresh, approval and provisioning are separate operations; each requires its own configuration.
ACTUAL PRODUCT · EXAMPLE WORKSPACE
A dedicated setup for each connection.
Choose the application type, review its supported scope and configure the endpoint and credentials. Account schemas, operations, correlation and import policy each have a focused place.
Authenticated John Doe example workspace. Synthetic endpoint; no provider connection or live provisioning is demonstrated.
FOR THE REST OF YOUR LANDSCAPE
A path for custom and legacy systems.
Use standards, structured files or configurable API connections when a dedicated connector does not fit.
SCIM
Connect supported user and group operations through a standards-based endpoint.
Web services
Configure API requests, mappings and supported operations for a tailored integration.
CSV
Import structured files, map fields and correlate accounts when an API is unavailable.
CREDENTIALS WITH CONTROL
Connect applications. Keep secrets in your vault.
Link deployment-approved Azure Key Vault, AWS Secrets Manager and Google Secret Manager providers. Select secret aliases in application editors without exposing their values.
Actual Limosa Identity interface · Synthetic example data · Signed in as John Doe. Select image to enlarge.
Product names identify compatible systems. No partnership or endorsement is implied. WORKDAY® is a trademark of Workday, Inc., registered in the United States and elsewhere. SAP and SAP SuccessFactors are trademarks or registered trademarks of SAP SE or its affiliates. Microsoft and Microsoft Entra are trademarks of the Microsoft group of companies. All other trademarks are the property of their respective owners.
PLAN YOUR INTEGRATION SCOPE
Choose the operation, not just the application name.
Need
What to confirm
Authoritative source
Record completeness, stable identifiers, required attributes and missing-record policy.
Access inventory
Account and entitlement types, memberships, API permissions and correlation rules.
Available SCIM or web-service endpoints, file imports and which work needs manual fulfillment.
For example, SAP SuccessFactors provides the documented HR source import. It does not imply SAP ERP or S/4HANA role provisioning. Each guide describes its own supported scope.
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.