One tap into
Utilizatorii tăi intră autentificați ca ei înșiși — fără împerechere, fără tokenuri copiate.
One tap for them,
O intrare rezistentă la preluare pentru partenerii cu propria bază de utilizatori — o acțiune de admin, zero tokenuri schimbate.
Un tap pentru ei
Utilizatorul tău apasă un buton în produsul tău și ajunge în dashboard deja autentificat. Fără flux de onboarding, fără credentiale de administrat, nimic de explicat în documentația de suport.
O acțiune de admin pentru tine
Înregistrarea unui singur client de federare este întreaga integrare. Nu există cod per-partener de scris, găzduit sau întreținut — partea ta rămâne exact cum e.
Backend-ul tău, în felul tău
Merge cu sesiuni Directus, backend-uri custom semnate HMAC sau aplicații care rulează deja propriul proiect Supabase. Brokerul se adaptează la autentificarea ta — nu invers.
Imun la preluare, prin design
Identitățile se leagă de provider plus subject — niciodată de un simplu email. Fuzionarea într-un cont existent cere trecerea a patru garduri stricte, iar fuzionarea într-un admin e pur și simplu imposibilă.
Limitat implicit
Fiecare utilizator provizionat ajunge într-un rol plafonat, fiecare client are propriile limite de rată și există un kill switch instant dacă ceva pare în neregulă. Generos cu utilizatorii, zgârcit cu privilegiile.
How one tap
A short-lived, single-use code with proof-of-possession — the same shape as OAuth PKCE, minus any token in your hands.
Register one client
01An admin registers your federation client: the verify mode, a redirect allowlist, per-client rate limits, and the capped role every signed-in user receives.
Your backend vouches
02Your button calls the broker with a PKCE challenge. The broker verifies against YOUR auth — a live Directus session check, an HMAC-signed assertion, or your own Supabase JWT.
A 60-second code
03The user gets a link carrying a single-use code that expires in 60 seconds. Only its hash is stored, and the redirect target is decided server-side, at start time.
We mint the session
04The Busymate app or dashboard redeems the code with the PKCE proof and receives a real session for a real account. Your app never sees or stores a Busymate token.
Who can see
Defaults enforced by row-level security in the database — and the one explicit action that changes each of them.
| Question | The default | What changes it |
|---|---|---|
| Who sees a device? | Its owner, plus roles holding the devices-view capability — checked by the database on every read. | An admin-created access grant scoped to one device, service group, or user — with an optional expiry. |
| Who sees captured traffic? | The account that captured it. Traffic follows its captor, not the device it came from. | Nothing implicit — a device grant does not quietly widen traffic reads. |
| What role does a federated user get? | The client's capped role — a configurable least-privilege role. The database refuses an admin role at write time. | You edit the client's capped role. Role hints inside partner assertions are ignored by design. |
| Can an assertion take over an account? | No. Identity keys on client plus subject; a colliding email gets a private no-merge address instead of the existing account. | Email linking is a per-client opt-in — and even then it refuses admin and protected accounts. |
| Where can the flow redirect? | Busymate hosts plus the client's registered allowlist — exact host match; anything else collapses to the dashboard root. | The client's redirect allowlist, editable only by an admin with a confirmed write. |
| What if a client misbehaves? | Per-client rate limits that fail closed, and denial events written to the audit trail before the response is sent. | Flip the client's kill switch — it is re-checked on every sign-in start, so it takes effect immediately. |
Three real
Delegation and handover are explicit, scoped rows — not tribal shared passwords.
“Give our contractor the three staging phones”
One access grant: a non-admin role scoped to that service group, with an expiry date. Revoking deletes the row — the contractor's reach evaluates to nothing on the very next database check.
“Hand this device to a teammate”
An admin-confirmed transfer moves ownership in one transaction. Captured history stays with whoever captured it and device-local settings are wiped — a clean handover, not a data migration.
“Let our platform's users debug from inside our product”
Each user's button-tap lands them in their own real Busymate account, homed in your client's tenant, clamped to your capped role. Your product keeps its auth; ours keeps its tokens.
Partner
Utilizatorii mei au nevoie de un login Busymate separat?
Nu — un tap îi duce în Busymate DevTools deja autentificați ca ei înșiși, fără împerechere, fără token copiat și fără un al doilea ecran de login.
Cât cod trebuie să scriu pentru integrare?
Niciunul pentru transfer în sine. Înregistrarea unui client de federare e toată configurarea — nu există cod per-partener de scris sau întreținut.
Ce furnizori de identitate sunt suportați?
Sesiuni Directus, backend-uri custom semnate HMAC sau aplicații care rulează deja propriul proiect Supabase.
Ce împiedică un partener rău-intenționat să preia un cont existent?
Identitățile se leagă de (provider, subject) și nu fuzionează niciodată într-un cont existent pe bază de email decât dacă trec patru garduri stricte — și niciodată într-un cont de admin.
How long does the sign-in link live, and can it be replayed?
The code in the link is single-use and expires in 60 seconds. Redeeming it requires the PKCE proof-of-possession, only its hash is ever stored, and HMAC assertions carry a single-use nonce checked atomically.
What happens when I disable a client or revoke a grant?
Disabling a client is re-checked on every sign-in start, so it bites immediately. Revoking an access grant deletes it — existing sessions keep their own expiry, but the delegated reach evaluates to nothing on the next database check.
Is there an audit trail for federated sign-ins?
Yes. Every start and exchange lands in the shared audit trail with the client, verify mode, outcome and denial reason — and denied events are written before the response goes out, so a probe can't outrun its own record.
Can a federated user ever become an admin?
No. A database trigger refuses an admin capped role on any client, the broker ignores role hints inside assertions, and email linking never merges into an admin or protected account.
Become
Înregistrează un client. Utilizatorii primesc un cont real și un rol limitat — aplicația ta nu atinge niciodată un token.