Team access, rights and profile transfers

An owner or admin, or a member they have given the share right, can share profiles, proxies and folders with workspace members. Access is view, launch, edit or manage, each including the one before, and a member's role caps it: a viewer gets at most view, a member at most edit, and an admin or owner manage. Workspace roles also carry rights, such as create, share and edit-proxy, that an owner or admin grants.

1. share-access-denied: the record is shared with you at a lower access than the action needs, or only its owner can change it. The message names who shared it and the access required. Ask them for more access.
2. team-right-denied: your workspace role does not include the right named in the message. Ask an owner or admin.
3. purge-forbidden: only a workspace owner or admin can delete profiles permanently. Trashed profiles are removed automatically after 30 days.
4. profile-limit: you have reached the number of profiles your workspace allows you. Profiles in the trash count until they are purged. Ask an owner or admin for a higher limit.
5. profile-access-denied: the profile was shared with you below launch access, or is no longer shared with you, so it cannot be started.
6. profile-transfer-pending: the profile is being transferred to another member and cannot be started until the transfer is accepted, rejected or expires.

Only an owner or admin can transfer a profile to another member. The recipient has 48 hours to accept or reject it. On acceptance the profile, and its newest browser session, becomes the recipient's own; its proxy goes with it only if the transfer included the proxy.

Transfer refusals carry one of these codes. The message after the code is the server's own.

1. team.transfer_forbidden: only a workspace owner or admin may transfer a profile. Ask one of them.
2. team.transfer_pending: this profile already has a transfer in progress. Wait for it to be accepted, rejected or to expire, or cancel it.
3. team.transfer_expired: the 48 hours to accept passed. Ask the sender to transfer the profile again.
4. team.transfer_closed: the transfer was already accepted, rejected, cancelled or completed, as the message says. Refresh the transfers list.
5. team.transfer_preparing: the sender's Browz has not yet packaged the profile. It does so when it is next online; try again later.
6. team.transfer_not_synced: the profile has not reached your account yet. Choose Sync now, then try again.
7. team.transfer_recipient_key_missing: the recipient has not published an encryption key yet. Ask them to open Browz and sign in once.
8. team.transfer_recipient_key_changed: the recipient's encryption key changed after the transfer started, for example after a password reset. Cancel the transfer and send it again.
9. team.transfer_stale_key: the profile's key changed while the transfer was being prepared. Try the transfer again.

Workspace keys and rights are signed on the owner's and managers' devices, and the server checks the order of those changes. These codes usually clear on their own when Browz retries; if one persists, refresh the screen or sign in again.

1. team.identity_key_mismatch: this computer's workspace signing key does not match the identity key the server holds for you. Sign in again so Browz publishes your identity key first.
2. team.roster_conflict: someone signed a newer member list for the workspace. Refresh, then repeat the change.
3. team.grant_conflict: another manager changed this member's rights first. Refresh, then repeat the change.
4. team.rekey_not_mintable or team.rekey_claimed: the record is not waiting for a new key from you, or another manager is already re-keying it. Nothing needs doing.
5. team.encryption_required: the record's owner uses end-to-end encryption, so the server refused a change that was not encrypted. Update Browz on the computer that made the change.
6. team.seats_in_use: a plan change would leave fewer seats than the people in your workspaces and their pending invitations. Remove members or revoke invitations first.

Open a profile: the server and the one-device lock →

Still stuck? Export diagnostics and contact support.