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

Sign-up and onboarding

How a person creates their account on the sign-in surface and becomes a member.

Studio roles: none. Frontend users sign up on the sign-in surface themselves. This page explains what they see, so that you can set up your frontends and help when someone gets stuck.

Sign up

Thomas Fuchs, who sits on Pannoniqa's works council, opens the "Pannoniqa Portal" for the first time and chooses to sign in.

  1. On "Sign in", he enters his "Email address" and chooses "Continue". The address has no account at Pannoniqa AG yet, so the sign-in surface opens "Create your account".
  2. He enters his "First name" and "Last name", a "Password" and "Repeat password".
  3. Under "Membership", he enters his membership details: "Member code", "Date of birth" and, if the field is shown, his "Challenge code".
  4. He chooses "Continue". The sign-in surface sends a 6-digit verification code to his email address.
  5. On "Check your email", he enters the "Verification code" and chooses "Create account".

The account exists only once the code matches. Until then it is a pending sign-up, which expires after 15 minutes. A code works for 15 minutes and becomes void after 5 wrong attempts; "Send a new code" sends another one, at most once a minute. A new code makes the previous one invalid.

The password needs at least 8 characters, an uppercase letter, a number and a special character such as !, ?, # or %. A password that has appeared in a data breach is refused.

Onboarding: becoming a member

When the account is created, the Studio runs the membership check in onboarding mode with the member code and facts Thomas entered. It asks your registers in the order of the membership definition:

  • Valid, and in the frontend's community: Thomas is now a member. He continues to the frontend, which knows he is a member.
  • Not valid: on a frontend with "Membership mandatory", the sign-in surface says "We could not sign you in" and offers "Request support". On other frontends he continues as a frontend user without membership.
  • Valid, but not in the frontend's community: Thomas becomes a member of the organisation, and the membership appears in the members directory. This frontend does not treat him as a member, though. On a frontend with "Membership mandatory", the sign-in surface says "We could not sign you in" and offers "Request support". On other frontends he continues, and the frontend learns that he is not a member of its community.
  • A register cannot be asked right now: on a frontend with "Membership mandatory", the sign-in surface says "Please try again later". On other frontends he continues without membership.

The sign-in surface never says why a check failed, so nobody can find out from it what a register holds.

The membership fields

  • The "Challenge code" field appears only when your membership definition contains a register that can require one. It is optional on the screen, with a hint that the code came by letter.
  • On a frontend with "Membership mandatory", the membership details are required: "Only members can use this service."
  • On other frontends it is optional. A person can leave it empty and confirm the membership later.

Confirm the membership later

A frontend user without a membership, or whose membership was deactivated, sees "Confirm your membership" after signing in with their password. They enter "Member code", "First name", "Last name", "Date of birth" and, where shown, "Challenge code", and choose "Confirm membership".

  • On a frontend with "Membership mandatory", the section is required, and "Get support" is the only other way out. It leads to the "Request support" page.
  • On other frontends, "Skip for now" continues without membership. The section comes back at a later sign-in.

They can do this from any frontend of the organisation: the membership belongs to their account, not to one frontend.

When onboarding cannot finish

Some results lead to "Request support" on every frontend, whether membership is mandatory or not: the member code already belongs to another frontend user, or the person already holds a membership with a different member code. Too many failed checks lead to "Please try again later" on every frontend. A support request reaches your support address with the person's details.

A person whose membership was deactivated wins it back by confirming the membership again with the same member code.