Keeping your access
Make a key to a place you were let into, use it on any device, and see every device that can open the place as you.
When somebody lets you into a workspace, the credential lives in the browser you accepted it in. Lose that browser, or open a new phone, and you used to have to ask the host for a fresh link. Now you can keep a key yourself.
A key is to a door, never "your account": two nights on one workspace are two keys, on purpose. The workspace stores only a hash of it; nobody but you ever sees the key again.
Make a key
Open any thread you can read. Under what this is, members and guests see keep this access. Press make a key and Studio shows one line, once:
KRMRW-PEERZ-RHMSW-AH8Y9-1V9S7-K@btw.syncropel.com/<who you are there>Three parts, left to right: the key (26 letters and digits, grouped in fives so it reads aloud), the place, and who the key re-opens the place as (a long identifier, shortened here). Copy it somewhere you will find again. It is not a link; pasting it into a browser's address bar does nothing.
The floor is stated beside it and is not softened: lose the key and this browser, and whoever let you in has to let you in again.
Get back in on any device
Open Studio on the new device, press + add a connection, and paste the whole line into the field. Studio recognises it and offers open with this key. You land in the place as the same person, with the same threads.
The key you pasted is spent by using it. Before you land, Studio shows you a new key, once. Keep that one; the old one no longer opens anything.
Typing is forgiving: case does not matter, spaces and hyphens are ignored, and
a photographed O or I is read as 0 or 1.
Turn the key
On a thread where you already kept a key, keep this access says so and offers make a new one. It asks for the current key first (paste the bare code or the whole line), then shows the replacement once. The old key stops working. Nobody holding a stolen browser can quietly replace your key, because they do not have the current one.
Your keys, and every device that can open this as you
Under + add a connection, when you are reading a place, two lists appear:
- your keys to this lists the keys bound to you here. remove deletes one; you can make another from any thread.
- keys in the wild lists every device that can open this place as you, with the one you are on marked. If one is not yours, revoke it. The others keep working, and your standing in the place is untouched; only that device is out.
What the workspace refuses
The door that turns a key into a credential answers every wrong attempt the same way, in the same time, whether the person named does not exist, has no key, or typed the wrong one. Studio shows that refusal in the door's own words and adds no diagnosis of its own. Attempts are rate limited: three in a burst, then one every five seconds, per person named and per network address.
Two more ways back, where the workspace accepts them
The recovery key is the floor: no vendor, no account, works for a party guest. Two more ways to come back ride the same doors, and Studio shows each only on workspaces that accept it.
Link to your account
Signed in to a hosted account, keep this access also offers link to your account. Press it and your account can find this key again on any device: under + add a connection, shared with you lists the places your account knows, and open as you re-opens one without a line to paste. The account is a way to find the key, never the key itself: the workspace sees a salted hash, not who you are to the account provider.
Hosted workspaces accept it. A self-hosted workspace accepts it only if the person running it declares a verifier (operators). Signing out on a shared device clears what that device held and leaves your account's list untouched.
Use a passkey
Where the workspace declares a relying party, keep this access offers use a passkey. One gesture registers a passkey that your phone or laptop keeps for you and your platform carries between your devices. On another device, paste a kept line into + add a connection and choose use a passkey instead: the line only names the place and who you are there, its code is never sent, and the passkey signs the workspace's challenge.
A passkey is the safest key here. It is still one key to one door, and a passkey made on one kind of phone does not travel to every laptop, so keep a code as well; Studio says so when a passkey is the only key you hold.
For operators
Nothing to configure for the recovery key; every workspace on a current version accepts it. The doors behind this page are in the API reference.
Universal traversal — your reach
See everything you reach across all your workspaces as one continuous view, ask graph questions about the people and threads connected to you, and understand how shared threads appear with exactly the access that was granted.
Agent Credentials
Two honest ways to credential an AI agent — an instance-level service account that survives personnel changes, or an attenuated sub-grant of a member that dies with the member. When to use which, and what is enforced today.