Team, in the app you already have.
A Team code adds your organization to HybridCipher. Create groups, share protected folders, approve the devices people use, and remove access by rotating keys. Files are encrypted on each device, and keys are shared only between members' devices.
How Team Works
Personal and Team are the same app. Owners and admins run the Team; members see only the groups they belong to.
Activate your Team
The owner opens Settings → Activate Team and enters the organization name and a single-use Team code. Personal stays available on the same account.
Create groups
Make one group for each set of people who share files, such as a department or a client project. Groups have their own owners, admins, and members.
Add and invite people
Add someone by email. People already in your Team get access right away; anyone else is invited, which uses one seat. Invitations expire after 7 days.
Protect a shared folder
A group's folder is protected with the group's keys, so everyone in the group can open its files on their approved devices.
Approve devices
New devices wait under To do until an owner or admin approves them. Team administration works only from a verified device.
Remove access
Removing someone from a group rotates the group's keys in the same step, so they can't open files added from now on.
Step-by-step with screenshots: Team admin guide.
Seats & Licensing
Licensing decides how many people your Team can hold. It is kept separate from the keys that decide who can open files.
One code, one organization
Each Team code is single-use and creates one organization. Members never need a code; they join by invitation.
Seats
The owner's seat counts toward the limit, and a pending invitation holds a seat until it is accepted or cancelled. Removing someone from the Team frees their seat.
No expiry date
A Team license does not expire unless it is revoked. The app keeps a signed copy that works offline for 30 days and refreshes while online.
Your files stay yours
If a license lapses or is revoked, changes are blocked but you can still open and export your files.
Get a Team code
Tell us your organization and how many seats you need. We'll reply with a single-use Team code that you enter in Settings → Activate Team.
Architecture Layers
Team separates identity, key delivery, file encryption, and auditability.
Device-bound membership
Users authenticate without sending passwords to the server. Authorized devices receive wrapped epoch material, not plaintext file keys.
Epoch-based group keys
Removing someone, or an admin rotating keys, advances the group epoch. New file keys are wrapped for the current epoch, and each member's app moves older files to the new key in the background.
Client-side encryption
File contents are encrypted before they reach storage. The coordination service handles metadata and key-delivery envelopes, not plaintext.
Tamper-evident events
Membership, key-delivery, and rekey events can be committed into hash-chained logs and Merkle roots for later verification.
Revocation Flow
Removal changes cryptographic state, not just a permission. A removed member stops receiving new keys at once. Access to files they could already open depends on whether those files have been re-encrypted under the new keys.
Read Architecture NotesAn owner or admin clicks Remove access on the group's People tab.
The group's keys rotate to a new epoch in the same step, and the removed person's devices stop receiving new keys.
Files added from now on use the new keys, so the removed person can't open them.
Older files they could already open are covered once they are re-encrypted under the new keys.
Membership and key events are recorded for later review.
Design Tradeoffs
The model favors explicit cryptographic guarantees over vague claims about server-side control.
Cryptographic revocation is not just an ACL
Removing access requires key evolution and, for older files, a rekey operation. The model makes that work explicit instead of pretending a server-side permission change is enough.
Offline work needs cached authority
Authorized devices can continue using cached epoch keys, while new devices or membership changes require coordination when connectivity returns.
Auditability adds state
Transparency logs and coverage proofs improve accountability, but they also introduce verification data that must be stored, synced, and checked.