Experience progress
What this screen is for
How the members of this deployment explore the Experience Center: what brought them, how far they got and where they stopped. A visit alone is never counted.
The screen is in the platform context, under Monitoring & audit, as Experience progress. It reads the progress each member's Experience Center records; it changes nothing.
What must exist first
- The
admin.platform.experience-progress.readpermission. The platform super administrator, platform operator and platform auditor roles hold it; the platform viewer does not. Without it the screen says: "Your role does not read experience progress." - Members who have explored the Experience Center. Until one has, the screen says: "No member has explored the Experience Center yet."
Decisions you make here
Reading a tenant's members
The screen shows a block per tenant, for the platform tenant and for customer tenants, with one row per member. Tenants are paged 20 per page. Each row shows:
- Member.
- Reason: the member's answer to What brings you here?, shown with the answer's own label, such as Encrypted data we must modernize.
- First started: when the member first started an experience.
- To first experienced: the time, in minutes, from that first start to the first experience the member completed.
- One column per experience, with its status: Not started, In progress or Experienced.
- Depth: "{inspect} inspected · {screens} screens · {docs} docs". An inspection is a Do this from your code link opened in an experience's result; a screen is a step's screen opened from the guide's Open the screen for this step; a doc is API documentation opened from an experience, which is not yet counted and reads 0.
- Last activity.
- Stopped at: the experience the member last worked on, with its next missing step.
On ANKASecure© SaaS and dedicated SaaS
Customer tenants are shown as one block, Customer tenants (aggregated), naming no tenant or person. The screen states why: "On this deployment the platform reads customer member data only inside a Support Access session, so customer tenants are shown as one total with no tenant or person named."
The block shows "{members} members with progress", then a table of counts per experience: Not started, In progress and Experienced. The platform tenant's own members still appear as a block of members.
What you can verify afterwards
- A visit alone records nothing: an experience's status changes only when the member reaches a milestone, and Depth counts only the links and screens it names.
- When the read fails, the screen shows the standard error state; Retry reads it again.