IMPLEMENTATION
Start with a clear scope.
Expand with evidence.
Choose a source, a small set of applications and one governance outcome. Validate the full process with your owners before extending automation.
Define the pilot and its owners.
Choose a lifecycle, request or certification scenario. Agree the people, applications, access items and acceptance evidence. Identify source owners, application owners, reviewers and deployment operators.
Output: agreed scope and success criteriaPrepare source and target access.
Check each connector’s supported operations. Arrange test endpoints, required provider permissions and credentials or approved secret references. Confirm source completeness and stable identifiers.
Output: connection prerequisites and source ownershipEstablish trustworthy inventory.
Import accounts and entitlements. Validate schemas and identity mappings, review correlation and resolve unexpected gaps. Confirm what a missing source record means before enabling automated consequences.
Output: reviewed inventory and correlation exceptionsConfigure and exercise governance.
Set up roles, request workflows, reviewers and conflict policies for the pilot. Use the web interface or a compatible AI assistant. Check permissions and decisions with the intended user roles.
Output: repeatable governance scenarioEnable supported writes deliberately.
Validate account types and mappings, then enable provisioning policies for the pilot. Test a grant and removal, manual fulfillment, failed operations and target verification.
Output: execution and verification evidenceAgree ongoing operation.
Assign responsibility for scheduled imports and evaluations, failed jobs, unresolved accounts and review campaigns. Agree deployment monitoring, backups, recovery, support arrangements and change control before production use.
Output: operating responsibilities and expansion criteria
Who brings what?
| Owner | Responsibilities to agree |
|---|---|
| Identity team | Mappings, correlation, role rules, workflows and governance scope. |
| HR and application owners | Source quality, API access, test environments, entitlement meaning and target validation. |
| Security and audit stakeholders | Policy requirements, review responsibilities and required evidence. |
| Deployment operator | Hosting, network access, worker and isolated runtime operation, monitoring, backups and recovery. |
| Your Limosa contact | Confirm the requested implementation assistance, commercial scope and support arrangements. |
Fit the rollout to your environment.
The application uses an API, web interface, PostgreSQL-backed workers and a separate isolated runtime for customer JavaScript. Connectivity to sources and targets must be planned for your deployment. Hosting and operational responsibilities should be agreed during evaluation; this guide is not a managed-service or availability commitment.
YOUR NEXT STEP
See governance in practice.
Explore the public demo or bring your applications and governance questions to a guided conversation.