Organizations & sharing

One identity, several workspaces

A server can host several organizations. Add an HTTPS server in Manage servers, then choose Connect / discover organizations. Complete its authenticator enrollment or sign-in. Saving an address or checking HTTPS alone does not sign you in.

If someone invited you, paste their invitation URL into Join organization and review the server, organization, and intended identity. Joining an organization establishes membership; it does not automatically give you the keys for existing records.

Unlock the organization

Choose the organization and unlock it with a fresh authenticator code, or with Windows Hello after enrolling it for this organization. This enrollment is separate from local identity unlock. Windows Hello may offer a fingerprint, face recognition, or a PIN.

Organization sessions last at most 15 minutes and require another unlock after expiry. Locking the identity locks its organizations too. The current organization unlock flow requires a connection to the server.

Share from the app

1. Make sure the recipient has joined the organization. Compare their full Identity ID through a trusted channel, particularly before the first share. Names are helpful labels, not cryptographic identity.
2. Open the record or group and choose Share. Select the recipient, review their identity and permissions, and set any required expiry.
3. The app prepares fresh keys for the current record or inheriting group contents and delivers an encrypted offer to that recipient.
4. The recipient opens Invitations, reviews the sender and permissions, and accepts. Their app decrypts the delivered key locally and protects it under their own master key.

You send an invitation link to bring someone into an organization. You share the actual records from the app. Neither a membership invitation nor a sharing notification is a plaintext password link.

Understand groups and permissions

Group access includes its inheriting records, subgroups, and future children. Restricted groups have an independent access boundary and need separate sharing. You can also share one record without exposing the rest of its parent group.

Record permissions distinguish reading, editing, deleting, sharing, and ownership. Groups also distinguish adding, editing, and removing records. The sharing screen shows the rights being granted. An organization administrator does not gain password access just by holding that role.

New shares are prepared for current and future versions; they do not deliberately deliver earlier version keys. The app currently requires the cryptographic custodian to prepare a new share. Delegated holders may need that custodian's help even when their grant includes sharing rights.

Change or end access

Use Manage access to inspect or revoke a grant. Changing rights means revoking the old grant and creating a new one. Rotation may generate replacement offers for remaining recipients to accept. Keep the preparing device available until a sharing or rotation operation completes.

Revocation cannot erase passwords someone already copied. If a secret was exposed, replace it at its original service too. Read organization administration for containment, recovery, and access reviews.