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 and test before saving
    • Save and version history
  • Communities
    • Create, rename and delete a community
    • Filter by register, status, groups and claims
  • Members directory
    • Find a member
    • Look up the checks of a member code
    • Deactivate a membership
  • 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

Disconnect a frontend

Switch a frontend off for everyone, and reconnect it.

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

Disconnecting switches one frontend off: it signs no one in, and its frontend keys are refused. Use it when a frontend is retired or compromised, or when a test website must stop. Everything is kept, so reconnecting restores it. Pannoniqa AG, for example, could disconnect a preview of the "Pannoniqa Portal" once the real one is live.

Disconnect a frontend

  1. Open "Frontends" and choose the frontend.
  2. Under "Disconnect frontend", choose "Disconnect frontend".
  3. Read what happens in the dialog "Disconnect …?" and choose "Disconnect".

This happens at once:

  • The frontend signs no one in from now on. The sign-in surface refuses its sign-ins.
  • Its sign-in sessions end: everyone signed in to it is signed out of it.
  • Its frontend keys stop working: its backend's calls to the Studio are refused.

The frontend may keep using the access tokens it already holds for at most 1 hour. Frontend users stay signed in to your other frontends.

The frontend shows the badge "Disconnected", and its page says since when and by whom. Its settings, keys and sign-in client stay editable.

Reconnect a frontend

  1. Open the disconnected frontend.
  2. Under "Frontend disconnected", choose "Reconnect" and confirm with "Reconnect".

The frontend signs users in again, and its keys work again at once. Frontend users who were signed out must sign in again; ended sessions are not restored. Their frontend activations were kept, so nothing else changes for them.

Disconnecting or blocking

Disconnecting affects everyone who uses one frontend. To shut out one person from all frontends, block the frontend user.