Member code query
Ask your published membership definition how it decides one member code right now.
Studio roles: "Owner", "Administrator" and "Community manager". The other Studio roles do not see "Member code query" in the sidebar.
A member code query asks your published membership definition how it decides one member code right now, as a login check would: by status only, without names, birth date or challenge code. It tells you, for example, whether PQ-10017 is still let in after the change you saved this morning, without anyone having to sign in.
The query always asks the saved definition. Changes you have not saved yet in the editor are not part of it: a query reflects them only once you choose "Save and publish", which publishes them at once. To see what unsaved changes would do, use the preview before saving.
Query a member code
- Open "Member code query". The page is called "Query a member code".
- Enter the "Member code", for example PQ-10017.
- Choose "Query".
From the check lookup, "Query this member code" opens the member code query with that code filled in. The query runs only when you choose "Query".
If your definition has no register assignments yet, the page shows "Your membership definition has no registers yet." with a link to "Membership definition" instead of the form.
Read the result
The result shows:
- the outcome: "Valid", "Not valid" or "Unavailable", with the reason, such as "Not found in any register";
- which register decided, at which position, and the entry it found;
- "Register by register": what each register answered, for example "Found, filtered out: this register does not count the status Inactive", or "Not reached: a register above decided";
- which communities the person would land in;
- "Decided under definition version N": the version of the definition the query asked, linked to that version in the version history.
In Pannoniqa AG, PQ-10017 is the retiree Johann Gruber. "SAP HR" is asked live and does not find him, nor does "Works council". "Retirees" at position 3 decides: the result is "Valid", and he lands in the communities "All staff" and "Retirees".
Nothing is saved or logged
External registers are asked live, as at a real check. Otherwise a query leaves no trace: nothing is saved, and neither the member code nor the claims a register returns are logged.
- It is not a membership check. A query never appears in the check log, so the check lookup never shows it. The check lookup shows the checks that already happened; a member code query asks what would happen now.
- It is never a failed check. A "Not valid" answer does not count towards the rate limits, and queries are not limited by them.
- It changes no membership. The member's status and communities still change only at their next membership check.
When to use it
After you save a change to the membership definition, for example a new order of the registers or a register that refuses, query a member code you know should stay valid, and one you expect to be refused. If an answer is not what you expected, change the definition and save it again.
It also helps with support: when the check lookup shows why a past check failed, a query tells you whether the same member code would be decided differently now, for example after you changed the status in the person's entry. A query does not compare names or birth date, so it cannot tell whether "Names or birth date do not match" would happen again.