Repository navigation
Teams and Session Sharing
English · Русский
Teams share hosts, snippets and runbooks between accounts on your sync server, end-to-end encrypted. The server relays ciphertext and never holds a team key. Teams require sync: without a connected account the section says so.
New team generates the team key on your device. Inviting a member looks up their published public key by account id and shows its fingerprint — verify it with the invitee over a trusted channel before sending, because the fingerprint is what guards against key substitution by the server. The invitee sees the inviter's fingerprint before accepting, and an invite whose sender cannot be verified says so.
An account that has never opened Teams has published no key yet, and cannot be invited until it does.
| Role | What it can do |
|---|---|
| Owner | everything, including deleting the team |
| Admin | manage members, roles and access scopes |
| Editor | share and change records |
| Viewer | read shared records |
Removing a member revokes server access at once. The team key is not rotated for you — rotate shared secrets if the person should no longer be able to read what they already had.
A team can be split into areas (scopes). Records shared into a scope get their own key and stay unreadable for members without access. Granting and revoking access is per member; revoking rotates the scope key. A record can live in one scope at a time.
Whole team is the default area — everything a member of the team can read.
Share host / Share snippet moves a record into the team's shared vault. The shared vault card shows how many items it holds, the encryption model (per-member key wrap) and when the key was last rotated.
Team → History shows who did what, filterable by Records, Members, Access and Sessions: team created, members invited/removed/joined, roles changed, keys rotated, scopes created and granted, records shared/changed/removed, sessions opened and recorded.
Session events are reported by member apps — the server takes no part in a connection and cannot confirm one. Reporting sessions on shared hosts is a per-device setting (Settings → Security); sessions on your own hosts are never reported.
Share session streams a running terminal to the team over an end-to-end encrypted channel; the relay carries encrypted frames only.
- Viewers watch by default; Let viewers type hands over the keyboard.
- A viewer can Request control, and the host allows or denies it.
- On a production session viewers can only watch — input is locked.
- The Team section lists live sessions with who started them and how many are watching.
Failure reasons are stated plainly: not connected to sync, the team key has not arrived on this device yet, the relay is unreachable, or the server refused the share.
Leave team removes the team key and shared records from this device. Delete team (owner) removes shared records from the server for everyone.
User guide
- Installation
- Getting started
- Hosts and connections
- Vault and credentials
- Terminal
- Files (SFTP)
- Port forwarding
- Remote desktops
- Snippets and runbooks
- Monitoring and guard
- AI assistant
- Sync and devices
- Teams and sharing
- Settings and shortcuts
- Android
- Troubleshooting
Development
- Architecture
- Building and running
- Connections and transports
- Terminal engine
- Vault and crypto
- Sync protocol
- Remote desktop stacks
- UI layer
- Testing and the gate
- Contributing and releases
Русский — оглавление