Check modes

Onboarding, login and eligibility: the three ways a membership check is asked.

Studio roles: "Owner", "Administrator" and "Community manager" see each check's mode in the check lookup. The checks themselves run without a Studio user.

A membership check is asked in one of three check modes. The check lookup shows the mode of each check under "Check mode": "Onboarding", "Login" or "Eligibility".

Onboarding

A person becomes a member. On the sign-in surface of Login with appsolut, when they sign up or first sign in to one of your frontends, they enter:

their member code;
their first name, last name and birth date, which the deciding register must confirm where it holds them;
their challenge code, where your organisation may require one (see Challenge codes).

A valid result creates their organisation membership, or takes over a deactivated one with the same member code. If another person already holds the membership of that member code, the result is "Another person holds the membership".

Pannoniqa's retiree Johann Gruber onboarded at the Pannoniqa Portal with PQ-10017, his name and his birth date. The register "Retirees" confirmed him.

At every sign-in of a member, the Studio checks their stored member code again: by status only, without names, birth date or challenge code, as nobody types anything. The result updates their organisation membership:

Valid: the membership stays or becomes valid, with the names, groups and claims of the deciding register. If another entry or register decided than last time, the membership is relinked.
Not valid: the membership is not valid, with the reason. It stays linked, and the next valid login makes it valid again.
Unavailable: the last result stands, under the grace rule.

Eligibility

A frontend's own backend asks about a person who need not be signed in or even have an account, called the applicant: for example the Pannoniqa Portal's backend, before it accepts a booking for a member code. It sends the member code and the facts, never a challenge code, with its frontend key.

The answer is given for that frontend's community: valid means the person passes the check and lands in the frontend's community. A person who passes but is not in that community gets not valid, with the reason "Valid, but outside the frontend's community". A check in eligibility mode creates no organisation membership.

How a backend asks is described in the developer documentation.

Onboarding

A person becomes a member. On the sign-in surface of Login with appsolut, when they sign up or first sign in to one of your frontends, they enter:

their member code;

their first name, last name and birth date, which the deciding register must confirm where it holds them;

their challenge code, where your organisation may require one (see Challenge codes).

Pannoniqa's retiree Johann Gruber onboarded at the Pannoniqa Portal with PQ-10017, his name and his birth date. The register "Retirees" confirmed him.

Valid: the membership stays or becomes valid, with the names, groups and claims of the deciding register. If another entry or register decided than last time, the membership is relinked.

Not valid: the membership is not valid, with the reason. It stays linked, and the next valid login makes it valid again.

Unavailable: the last result stands, under the grace rule.

Eligibility

How a backend asks is described in the developer documentation.