Skip to content

Follow a guided experience in the Experience Center

See for yourself what ANKASecure© does, on prepared data in your own tenant: pick one of five guided experiences, follow its guide across the console's own screens, and keep the evidence of each step.

Who can do it

A tenant administrator or a tenant key manager, in their own session. Your progress is yours: it is saved in the tenant for you, and nobody else's progress changes when you work.

  • A platform administrator (any platform role) working in the tenant through support access is not offered the Experience Center: a support-access session holds no membership of the tenant, so it has no progress and no prepared set of its own there.
  • Crypto-Agility, Cryptographic Sovereignty and Frictionless Migration run real operations in the Cryptographic Playground. A role the Playground is not offered sees those three as unavailable, and no set is prepared for it.

Before you start

  • A tenant set up for the Experience Center: a tenant the evaluation provisioning run created, or an Experience Center sandbox. A customer's ordinary tenant is not set up for it. The Experience Center is offered on a deployment your organization operates, never on an ANKATech-hosted deployment, and not to API Marketplace tenants.
  • Nothing to prepare yourself. The first time you open the Experience Center, the platform prepares your own Experience Center set: an application, Exchange Contexts, keys (one of them, the key that rotates on use, with a rotation schedule), a constraint policy, Cryptographic Actors, capability grants and Exchanges. Every name in it ends with your member suffix, so you rotate and reset your own keys and never move another member's. Its Actors never hold a credential. At most 25 members of a tenant hold a set.
  • Crypto-Agility's rotation changes only your own key. Beyond that, an experience changes your tenant's configuration in one place only, and only when you confirm it: Policy-Driven Governance's algorithm template, which applies to every user of the tenant. Every Playground run is a real operation with its audit record.

Steps

  1. Open Experience Center. The first time, while your set is prepared, the screen says "Preparing your Experience Center keys…" and "Your own keys and Actors are being created. The first time takes a few seconds." in place of the cards; the guide says the same while it waits. Then each experience card shows its status, Not started, In progress or Experienced, plus Revisited once you run an experienced one again, and its Evidence. Crypto-Agility is marked Recommended first.
  2. Optionally, answer What brings you here? with Preparing for post-quantum, Encrypted data we must modernize, Partners or providers use our cryptography, Compliance, audit and regulation or Fitting it into our stack (KMS, SIEM, identity). The answer only orders the experiences for you; the best match is marked Best match.
  3. On a card, select Start, Continue or Revisit, as its status allows. Explore freely opens the experience's first screen without starting the guide.
  4. Follow the Experience guide, the panel shown on every screen while the experience is active:
    1. Read the step, shown as its position and its total, and what to do there.
    2. Select Open the screen for this step, and do what the step says on that screen.
    3. Use Back and Next to move between steps. You may navigate anywhere; the guide follows you. A step completes only when the platform has confirmed its outcome, never because you visited a page. Crypto-Agility's two encryptions and its rotation, and Cryptographic Sovereignty's partner operation, are recorded by the platform itself when the operation succeeds on your own session, whichever screen you run it from. Crypto-Agility's optional rotation on use is recorded when the platform rotates your own usage-rotation key by itself, on reaching a usage limit. It is stored on a fresh installation of this release and, on a deployment upgraded to it, once the upgrade is finalized; a rotation on use before then records nothing. The console records every other step once its screen confirms the outcome.
    4. Minimize the guide folds it away, and closing it keeps your progress.
    5. In Crypto-Agility, when your key was rotated to ML-KEM before its first Encrypt was recorded, the guide says the first step can no longer be proven on it and offers "Reset this experience's keys". It creates fresh RSA-3072 encryption and signature keys of your own in place of your rotated ones, with new grants taking the old grants' place on the same Exchange, and once every key is replaced it starts Crypto-Agility again from its first step. Other members' keys are untouched. It is offered to a session holding admin.keys.orchestrate, admin.tenant.exchange.update, admin.tenant.capability-grant.create and admin.tenant.capability-grant.revoke, never in a support-access session; otherwise the guide says "Resetting the keys needs the key and Exchange grant permissions. Ask an administrator who holds them." If the reset does not complete, the guide says "The keys could not be reset completely. Open the Keys screen to see what changed, then try again."
  5. At the end of an experience, read What you just proved. Do this from your code opens the screen that shows the run's HTTP exchange and its cURL.
  6. To run an experience again from its first step, select Restart on its card, then Restart in the confirmation, or Cancel. Its milestones are cleared; the other experiences keep their progress.

What you see when it worked

Each confirmed outcome appears under the card's Evidence, with an Audit trace link to the correlation trace of the operation behind it, where that operation has one. When every required milestone is recorded, the card shows Experienced.

The screen states where your progress is kept: "Your progress is saved in this tenant, for you, and kept until your membership or the tenant ends. This deployment's platform administrators can see each member's progress on their Experience progress screen."

If it fails

What you see Cause What to do
The Experience Center is not offered here, with Go to the dashboard The tenant is not set up for the Experience Center, the deployment is hosted by ANKATech, the tenant is an API Marketplace tenant, you work in the tenant through support access, or you are a platform administrator acting on the tenant directly Use the console's screens directly; your dashboard and every screen stay available
"This experience runs operations in the Cryptographic Playground, which your role is not offered." Your role cannot run Playground operations Ask a tenant administrator or key manager to run it, or follow the other experiences
Your Experience Center keys could not be prepared., with "This tenant already has 25 members with their own Experience Center keys. Ask a tenant administrator." 25 other members of the tenant already hold a set. A member's set keeps its place until the tenant is closed, even after the membership ends Ask a tenant administrator; Try again is not offered
Your Experience Center keys could not be prepared., with "Names your Experience Center needs are already used in this tenant. Ask a tenant administrator." An object the platform did not create for you holds a name of your set, or a key of your set was deleted. A deleted key's name stays taken, so the set cannot be prepared again in that tenant Ask a tenant administrator; Try again is not offered
Your Experience Center keys could not be prepared., with "The cryptographic service did not answer. Try again in a moment." The cryptographic service did not answer, or the platform was busy Select Try again
Your Experience Center keys could not be prepared., with the platform's own sentence The platform refused another part of the preparation Select Try again where it is offered; it is not offered for a refusal that asking again cannot change
"This tenant has no prepared leg for this step: its Experience Center resources are missing. You can still explore the screen freely." Your own set holds nothing for that step Explore the screen freely, or ask a tenant administrator
A step stays open after you visited its screen No outcome has been confirmed yet Do what the step says on that screen; the step completes when the platform confirms it

A change the platform refuses is not kept on screen: the console reads your progress again, so the screen always shows what is stored.

Without the console

Surface How
API GET /api/v3/admin/tenants/{tenantId}/experience-progress/me (operation getTenantExperienceProgress) reads your own progress
API POST /api/v3/admin/tenants/{tenantId}/experience-progress/me/prepare (operation prepareTenantExperienceSet) prepares your own set; it resumes a set left incomplete and answers created: 0 once the set is prepared. A 26th member is refused 409 experience-set-capacity, a name held by another object 409 experience-set-name-taken, and a second preparation while one runs 409 experience-set-prepare-in-progress
API PUT /api/v3/admin/tenants/{tenantId}/experience-progress/me/intent with intent (operation setTenantExperienceIntent)
API PUT /api/v3/admin/tenants/{tenantId}/experience-progress/me/landing with exploreFreely (operation replaceTenantExperienceLanding) chooses where you land when you sign in
API POST /api/v3/admin/tenants/{tenantId}/experience-progress/me/experiences/{experienceId}/start (operation startTenantExperience) and .../restart (operation restartTenantExperience)
API PUT /api/v3/admin/tenants/{tenantId}/experience-progress/me/experiences/{experienceId}/milestones/{milestoneId} (operation recordTenantExperienceMilestone); the first record of a milestone wins. encrypt-v1, rotated, encrypt-v2, usage-rotation and partner-operation are recorded by the platform and refused here with 422
API POST /api/v3/admin/tenants/{tenantId}/experience-progress/me/depth/{counter} (operation countTenantExperienceDepth)
API POST /api/v3/admin/tenants/{tenantId}/experience-progress/me/import (operation importTenantExperienceProgress), accepted once, only while nothing is stored for you; a milestone the platform records is skipped
API DELETE /api/v3/admin/tenants/{tenantId}/experience-progress/me (operation resetTenantExperienceProgress) clears your own progress; it is refused with 409 while a preparation of your set runs

Every write is refused with 403 in a support-access session and to a platform administrator acting on the tenant directly. Every write but the reset is refused with 409 in a tenant not set up for the Experience Center. In a support-access session the read answers the empty progress.

What else to know

  • Your progress stores no payload, plaintext, ciphertext, key, token or credential: only which milestones you reached and when, the correlation identifier of the operation behind each one, the figures Policy-Driven Governance read, your answer to What brings you here?, when you first started and were last active, and three counts: the Do this from your code links you opened, the screens you opened from the guide, and the API documentation you opened from an experience.
  • Until you complete an experience, you land on the Experience Center when you sign in. Explore freely beside the headline takes you to the dashboard and makes it where you land from then on; Land on the Experience Center again undoes that choice.
  • Where the guide stands is kept in this browser, and only that is cleared when you sign out.
  • Progress a browser kept before your progress was saved in the tenant is moved to the tenant once, the next time the console reads your progress in the tenant, when nothing is stored for you there yet. A milestone the platform records itself is not moved.
  • Presenter mode, for showing the platform to an audience, is shown to a member the Experience Center is offered to who may also run the Cryptographic Playground: a tenant administrator or a tenant key manager. It is switched on in this browser only and works on your own set. When it is on, it shows a preflight, talking points in the guide and Reset for the next audience:
    • the preflight marks each experience as ready to run here, or Cryptographic Sovereignty as needing an Exchange with a partner on a SIMPLE tenant, and says what it does not check: the prepared keys, the partner and the integrations;
    • Reset for the next audience resets only what is yours: fresh RSA-3072 agility keys of your own, with new grants on the same Exchange, take the place of your rotated ones, leaving other members' keys untouched, and then every experience returns to Not started for you. Your progress is cleared only once every key step succeeds. The keys are replaced only in a session holding the key and Exchange grant permissions, once your own set is prepared; otherwise the reset clears your progress alone, and names the permissions when they are what is missing;
    • the tenant's algorithm availability policy is not part of the reset: if the audience applied a template in Policy-Driven Governance, restore the policy on Policies › Algorithm Availability, which asks for its own confirmation because it applies to every user of the tenant.