Membership check
How the Studio decides whether a person is an eligible member, and what its answers mean.
Studio roles: "Owner", "Administrator" and "Community manager" see its results in the members directory and the check lookup. Nobody starts a membership check in the Studio: it runs when a person or a frontend asks.
The membership check is the Studio's answer to whether a member code, and the facts that go with it, belong to an eligible member of your organisation. It walks your membership definition from top to bottom and answers in one of three ways:
- "Valid": a register that qualifies decided about the person.
- "Not valid": a register refused them, or none decided.
- "Unavailable": a register could not answer, so the Studio cannot tell.
When it runs
- Onboarding: when a person becomes a member through Login with appsolut, with their member code, names, birth date and, where required, their challenge code.
- Login: at every sign-in of a member, with their stored member code.
- Eligibility: when a frontend's backend asks about someone, for example before it books a trip for them.
Check modes explains each.
Reasons stay in the Studio
Every answer that is not valid has a reason, such as "Not found in any register" or "Names or birth date do not match". The Studio shows it to you, in the check lookup and on a member's page. It never tells the person or the frontend: they get the answer only, and a support request a person sends from the sign-in surface does not say why their check failed. That way nobody can find out by trying what a register holds.
What it changes
A valid onboarding check creates the person's organisation membership. Each later check updates it: its status, the register entry it is linked to, the names, groups and claims it stores, and so its communities. Every check is written to the check log.