> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qwacks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Single sign-on

> How one Qwacks login carries you into Flock, Protokite, and Data Duck.

Qwacks is the **identity provider** for everything it makes. You sign in once with your Qwacks
account, and that same identity opens [Flock](/introduction), Protokite, and Data Duck — there's no
separate username or password for each app.

## Opening an app

Launch an app from the Qwacks hub and it opens already signed in. Behind the scenes it's a standard
OAuth handoff: the app asks Qwacks to authorize you, Qwacks sends you back with a short-lived
authorization code, and the app trades that code for the tokens that keep you signed in. You see
none of it beyond a brief "completing sign-in" moment.

Go straight to an app without signing in first and it bounces you to Qwacks to authenticate, then
returns you to where you were headed — the same handoff, started from the app's side.

## Your studio comes with you

The handoff carries your **active studio** along with your identity, so an app opens in the same
studio you had selected in the hub — its games, data, and team, not another's. Switch studios in the
hub before opening an app and you'll land in the one you picked; [Studios &
switching](/qwacks/studios) covers how that works.

Your **role** travels too. What you can see and change inside an app follows the admin, manager,
editor, or viewer role you hold in that studio — and because roles are per-studio, the same account
can have more reach in one studio than in another. [Team & roles](/qwacks/team) has the details.

## Staying signed in

Once you're in, Qwacks keeps your session alive and refreshes it quietly in the background, so you're
not asked to log in again each time you move between apps. Signing out from the hub's settings menu
ends your session there.