Inside AccessEdge
From access
to accountable
outcomes.
Six connected capabilities. See the source, the decision and the proof in the same review cycle.
Actual screens from the interactive demo. Fictional data and scripted AEGIS briefs. Production SaaS is in development.
Explore the app01 / Source coverage & ownership
Start with the right population.
See which systems supplied a source, whether it is current and which accounts still need an identity match.
- What the sample shows
- A draft campaign with missing and stale source data, reconciliation and launch gates.
- Why it matters
- A complete-looking review should not conceal gaps in the population.
02 / AEGIS decision context
Know what you are deciding.
Read the permission, business context, dated sources and missing information. Previous testing sits beside the current review.
- What the sample shows
- A scripted AEGIS brief, changed-access context and Keep, Remove or Change decisions.
- Why it matters
- Prior approval is a reference. The current reviewer still records a fresh reason.
03 / Questions in the review
Ask before you approve.
Keep the conversation attached to the access grant, with an owner, a due date and the full response history.
- What the sample shows
- A reviewer asks the application owner for context and follows up on the same thread.
- Why it matters
- Clarification should travel with the decision, not disappear into a separate email chain.
04 / Change proof & verification
A request is only the start.
IT records the requested change, a dated source and the observed result. A different person checks the proof and accepts it or asks for rework.
- What the sample shows
- Before-and-after access context, implementation notes and independent verification.
- Why it matters
- A closed ticket alone is not proof that the intended access is gone.
05 / Time-bound exceptions
Make temporary decisions explicit.
A temporary exception needs a reason, an expiry, compensating measures and a separate approval. Its remaining exposure stays visible.
- What the sample shows
- Exception request and approval, with a distinct closure policy.
- Why it matters
- An approved exception never becomes a verified removal. Expiry creates fresh work.
06 / Closure & the next cycle
Retain the why and the proof.
Bring scope, decisions, questions, change evidence and sign-off into one readable assurance record. Draft the next cycle without overwriting the past.
- What the sample shows
- Closure gates, a sample retained report and a fresh-cycle handoff.
- Why it matters
- A new cycle needs new sources and decisions. Future publication to CertEdge will be explicit and optional.
Explore at your own pace
The whole cycle, explained.
New to access reviews? Watch the narrated walkthrough, jump to a chapter or follow the five workflow tabs.
Sample interactions only. A real-data pilot needs agreed access, security and processing arrangements.