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
    • Claims
    • 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
    • Released claims
    • Sign-in settings
    • Guest access
    • 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

Guest access

Decide whether a frontend's backend may commit transactions for people who are not signed in.

Studio roles: "Owner" and "Administrator", and Studio users with the permission set "Frontends: manage". With "Frontends: read" you see whether guest access is on, without changing it.

A frontend's backend usually commits a transaction, such as a redemption, for a frontend user who is signed in. A guest call is one without a signed-in frontend user: the backend sends its frontend key alone and commits for an applicant, for example a person who proves their membership with their member code. Guest access decides whether that frontend may make guest calls. A new frontend starts with it off, and each frontend has its own switch.

Which frontends can take guest calls

Only a frontend with a backend of its own, which keeps its frontend key secret: the app type "Web app" or "Server". A single-page app, a mobile app or a desktop app runs on the person's device and cannot keep a key secret, so guest access stays off for them. A frontend gets its app type with its sign-in settings; a frontend without one, such as an external frontend, cannot switch guest access on either.

Switch guest access on

  1. Open "Frontends" and choose the frontend.
  2. Under "Guest access", switch on "Allow guest calls".
  3. Choose "Save guest access".

From then on, the frontend may make guest calls. Switch it on only for a frontend whose backend checks who it calls for: anyone who holds its frontend key may then commit transactions for people who are not signed in.

Switch guest access off

  1. Under "Guest access", switch off "Allow guest calls".
  2. Choose "Save guest access".

From then on, the frontend may make no guest calls. Calls for signed-in frontend users are not affected. Every change is recorded with who made it.

A disconnected frontend keeps its switch, but makes no guest calls, as its frontend keys are refused until you reconnect it.