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

Block a frontend user

Shut a frontend user out of all your frontends, and let them back in.

Studio roles: "Owner", "Administrator" and "Frontend user manager".

Blocking shuts a frontend user out of all of your organisation's frontends, for example when an account is misused. Their organisation membership stays, and unblocking lets them sign in again.

Block a frontend user

  1. Open "Frontend users" and find the person.
  2. In the list, choose "Block" in their row, or open their page and choose "Block" at the top.
  3. Read what happens in the dialog "Block …?" and choose "Block".

The list shows the "Blocked" badge. From now on:

  • the person cannot sign in to any of your frontends: the sign-in surface says "We could not sign you in" and offers "Request support", without saying why;
  • every session they have ends at once, on every frontend and device;
  • frontends get no new tokens for them, and their tokens cannot be refreshed. Access tokens already issued stay valid for up to an hour;
  • a password reset is refused.

Their organisation membership, frontend activations and data are kept. The person is not notified.

Unblock a frontend user

  1. Find the person; "State" "Blocked" in the filters lists every blocked frontend user.
  2. Choose "Unblock" and confirm with "Unblock".

The person can sign in again. No session comes back: they sign in anew. They are not notified.

Both appear under "History" on the person's page, with who did it.

Blocking, deactivating, disconnecting

  • Blocking shuts out one frontend user from every frontend. Their membership stays.
  • Deactivating a membership in the members directory makes the membership count for nobody, but the frontend user can still sign in to frontends without "Membership mandatory".
  • Disconnecting a frontend shuts one frontend off for everyone.