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

Login with appsolut

The one sign-in for all of an organisation's frontends, and the sign-in surface that frontend users see.

Login with appsolut is the one sign-in your organisation's people use for all of its frontends. Someone who signs up on the "Pannoniqa Portal" signs in to the "Pannoniqa App" with the same email address and password, and is not asked for their membership again. Their first sign-up also checks them against your registers and makes them a member.

One account per organisation

A person's account is a frontend user of one organisation. The same person at two organisations has two unrelated accounts, each with its own password. A frontend user is never a Studio user: the Studio and the frontends have separate accounts, and signing in to a frontend does not sign anyone in to the Studio.

The sign-in surface

When a frontend user chooses to sign in on a frontend, the frontend sends them to the sign-in surface: the screens for sign-in, sign-up, onboarding, support and sign-out, served by the Studio for all organisations, in your organisation's sign-in branding.

  • It shows your logo and colours, the frontend's name ("Sign in", "to continue to Pannoniqa Portal") and, if you set them, your privacy policy and imprint links.
  • It is in German or English, following the browser's language. Frontend users can switch with the language switch.
  • It follows the visitor's light or dark setting.
  • A security check (CAPTCHA) and limits on failed attempts protect it from automated attacks.

You decide how it looks under Sign-in branding, and which frontends may use it under Sign-in settings.

Membership at sign-in

The membership definition decides who is a member, and the frontend's community and membership rule decide who may use the frontend:

  • At the first sign-up, the person proves their membership: member code, name, date of birth and, where your registers may ask for it, their challenge code. The Studio runs the membership check in onboarding mode, and a valid result makes them a member.
  • At every later sign-in, the Studio checks the stored member code again (login mode). The person enters nothing.
  • On a frontend with "Membership mandatory", only members of its community get in. On other frontends, everyone with an account signs in, and the frontend learns whether they are a member of its community.

The frontend gets the result as the frontend role of the sign-in: "member" or only "authenticated". The sign-in surface never shows why a check failed.

What the Studio user does

The Studio does not sign anyone up: frontend users create their own accounts on the sign-in surface. In the Studio you:

  1. keep the registers and the membership definition up to date;
  2. create the frontend with its community and membership rule, and set up its sign-in settings;
  3. set the sign-in branding, with the support address;
  4. answer the support requests that reach that address;
  5. look after the frontend users.

In this section

  • Sign-up and onboarding: how a person creates an account and becomes a member.
  • Sign-in and sign-out: signing in, single sign-on, a forgotten password and signing out.
  • Support requests: what a person sends when sign-up or onboarding fails.