Limosaidentity

PLATFORM / REPORTING & AUDIT EVIDENCE

Explain who has access.
Show how it got there.

Query identities, accounts, entitlements, roles and request decisions. Save repeatable reports and investigate the histories behind a change.

Ask a focused question.

Start with a dataset or template. Add filters, choose columns and summarize results in the visual report editor.

Repeat and share.

Save report definitions and export CSV results. Server-side search and pagination keep investigation focused on the records you need.

Follow the context.

Inspect request decisions and object history. Follow linked fulfillment evidence to distinguish authorization from execution and observed access.

QUESTIONS FOR YOUR EVALUATION

01

Which accounts are not linked to a person?

Filter the account inventory by correlation and application to find records that need investigation.

02

Who requested and approved this access?

Explore request recipients, requested items, decisions, comments and workflow progress.

03

Was the approved change carried out?

Inspect fulfillment operations and verification separately from the approval outcome.

Build evidence around your controls.

Agree report scope, time period and responsible owners before an audit. Saved report definitions rerun against current data; they are not immutable historical snapshots. Retain exports and supporting records according to your organization’s evidence policy.

Reporting supports your control assessments. It does not certify regulatory compliance or replace an auditor’s judgment.

YOUR NEXT STEP

See governance in practice.

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