Documentation/Studio
Back
  • Getting started
    • Key concepts
    • Sign in
    • Create and switch organisations
  • Registers
    • Create and change a register
    • Upload and download entries
    • Add, edit and deactivate entries
    • Groups
    • Challenge codes
    • Connect and test an external register
    • Register activity
  • Membership definition
    • Add and order register assignments
    • Filters and outcomes
    • Preview before saving
    • Save and version history
  • Member code query
  • Members directory
    • Find a member
    • Look up the checks of a member code
    • Deactivate a membership
  • Communities
    • Create, rename and delete a community
    • Filter by register, status, groups and claims
  • Frontends
    • Create a frontend
    • Frontend keys
    • Sign-in settings
    • Sign-in branding
  • Login with appsolut
    • Sign-up and onboarding
    • Sign-in and sign-out
    • Support requests
  • Frontend users
    • Find a frontend user
    • Membership and activations
    • Block a frontend user
    • Export a frontend user's data
    • Disconnect a frontend
  • Membership check
    • Check modes
    • Results and the check log
    • Rate limits
    • Grace rule
  • Organisation settings
    • Organisation profile
    • Studio users and roles
    • Billing
    • Roadmap and feature requests

Challenge codes

Make onboarding ask for a personal secret, generate the codes and send them to your people.

Studio roles: "Owner", "Administrator" and "Community manager".

A member code alone is often easy to guess or to find on a payslip. A challenge code makes sure the right person onboards with it: a personal secret your organisation sends to the person on a second channel, for example by letter. The person enters it once, when they become a member through Login with appsolut. After that, they sign in without it.

The Studio never keeps a challenge code readable: it stores only a hash. Nobody can look a code up later, not even an "Owner".

Require a challenge code

  • Internal register: each entry has "Challenge required". "Onboarding asks for the entry's challenge code. Switching this off keeps a stored code for when you switch it back on." A new entry requires one. In an upload, the column for it reads yes or no; an empty cell means yes.
  • External register: its connection has "Challenge code required": "Onboarding asks for the person's challenge code." Your system checks the code. See Connect and test an external register.

Generate challenge codes for an internal register

  1. Open the register. The "Generate challenge codes" button shows how many entries need a code: those that have none, require one and are not deactivated.
  2. Choose "Generate challenge codes".
  3. Read the warning, then choose "Generate and download".

The Studio generates a code for each of those entries and downloads them as an Excel file, ready for a mail merge. "The codes are only in the file that downloads now, and it can be downloaded once: the Studio keeps no copy." Keep the file safe, and delete it once the letters are out. If the download fails, generate new codes for the entries concerned.

Replace the codes of some entries

When a person has lost their letter:

  1. Select their entry in the list. To select every entry a search found, choose "Select all … matching entries".
  2. Choose "Generate challenge codes".
  3. Choose "Generate and download".

"The selected entry gets a new challenge code, whatever its code, flag or deactivation." A code it had before stops working at once.

Set codes by upload

If you create the codes yourself, map a column of your file to the challenge code when you upload. A code in the file sets or replaces the entry's code; an empty cell keeps the stored one. A challenge code can be at most 72 bytes long.