Productivity & Workflows
1Password Team Vault Permissions: Separate Viewing, Editing, and Managing Shared Work Secrets
Complete three-role fictional vault matrix and direct/group removal handoff separate content read, maintenance, access administration, client safeguards and service credential decisions.
Before adding someone to a shared work vault, separate three questions: may they read its items, change its contents, or administer access? Check direct grants and group memberships together for the same person and vault. A vault manager does not automatically receive item viewing or editing permissions, and removing a vault grant does not make a password already copied from it stop working at the connected service.
This LandOffer guide uses two complete fictional reviews to make those boundaries concrete. Official 1Password documentation was checked on October 25, 2026. No real secrets, vaults, permissions, reports, accounts, or security settings were accessed or changed. All proposed grants, review outcomes, and handoffs below are authored examples, not product tests or organizational approvals.

Start with the task and account type
Describe the assigned work before choosing permissions. “Help with support” may mean reading a service address, signing into a test account, updating an outdated runbook note, or deciding who receives access. Separating those activities helps avoid granting access administration for a sign-in task; the service account may also reach beyond that assignment.
The current vault management documentation distinguishes Teams from Business. Teams uses Allow Viewing, Allow Editing, and Allow Managing. Business separates item actions more granularly and provides additional client settings. Check the actual subscription and controls rather than treating this article's Business example as a Teams configuration recipe.
The same page says managing a vault covers access grants, permission changes, and vault deletion; it does not itself include viewing or editing items. This is a statement about the permissions included in that grant. A manager's ability to change permissions still needs trusted ownership and review; “manage only” should not be described as an absolute inability to influence who can read the vault.
Identify the specific vault, service environment, item inventory, proposed person or group, and expiry of the task. A development credential, production administrator login, and recovery document should not be bundled together merely because they belong to one product. If the current vault's contents are broader than the assignment, leave sharing pending while the owner reviews an appropriate separation.
Understand what the controls actually enforce
1Password's permission enforcement guidance distinguishes cryptographic, server, and client enforcement. View Items is cryptographically enforced; item-changing and vault-management actions include server-enforced permissions. Client controls such as concealed-password viewing, export, and copy/share affect what trusted users can easily do in the apps.
That distinction matters when someone proposes “let them fill the password, but make it impossible to retain.” The documentation warns that client-enforced restrictions should not be relied on against hostile behavior. Disabling export is a useful safeguard, not proof that someone who can read the vault cannot preserve information outside it. This article provides no instructions for bypassing those safeguards.
Treat the connected service as a separate authority. Editing a Login item's saved password is not the same as changing the password accepted by that service. Likewise, a person may retain a service session or a previously copied credential after a vault-access change; the responsible service owner must review the applicable service controls. Do not promise that a single vault action completes offboarding everywhere.
Use meaningful labels in a review record: “may read staging items,” “may update staging notes,” and “may administer membership.” Avoid “read-only means harmless.” Read access to an operational secret can itself be significant, even when item edits and external sharing are disabled in the application.
Case one: a three-role matrix narrows a sharing request
In this fictional Business account, the Sandbox Support vault contains three invented item descriptions: a staging service Login, a test integration key, and a troubleshooting note. No secret values are written here. The staging Login can change synthetic test records, so access is not equivalent to viewing documentation alone. Production credentials belong outside the proposed scope.
Mara develops the staging integration and needs to maintain item details. Jules handles a two-week support exercise and needs approved staging sign-in information, without changing the vault contents. Inez administers access but has no current task requiring item contents. The matrix below records the owner's proposed choices, not default role bundles or actual saved settings.
| Proposed capability | Mara — developer | Jules — support | Inez — vault administrator |
|---|---|---|---|
| Read vault items | Yes, staging inventory only | Yes, staging inventory only | No item-read grant proposed |
| View/copy concealed passwords | Yes for assigned staging work | Yes for approved staging sign-in | No grant proposed |
| Create and edit items | Yes, maintain integration details | No | No |
| Archive or delete items | No; owner review required | No | No |
| Manage vault access | No | No | Yes, under access-review responsibility |
| Export, external copy/share, print | Not proposed | Not proposed | Not proposed |
| Item-history access | Not proposed for this exercise | Not proposed | Not proposed |
The owner deliberately avoids describing Inez as the person who “can do everything.” Inez's management responsibility and Mara's maintenance responsibility are different, although both require trust. The proposed matrix also avoids assigning Jules content editing merely because a support task may expose outdated instructions.
The completed scope review finds a problem: the test integration key belongs to a separate automation that Jules does not need. The fictional owner, Nessa, therefore withholds the invitation and requests a narrower support vault or another approved access arrangement containing only the staging Login and support note. No item has actually been moved or copied, and no new vault has been created.
Nessa's decision reads: “Mara's maintenance scope is reasonable in principle; Jules's proposed read access is too broad for the current inventory. Inez retains management responsibility without a proposed content-read grant. Final permissions and client settings require account verification after the narrower inventory is approved.” The inventory and proposed permissions review is complete; provisioning and actual account verification remain pending.
If this organization instead used Teams, Nessa would have to reassess its broader permission categories. For example, Teams Allow Viewing includes concealed-password viewing and clipboard copying. The Business matrix cannot be implemented by assuming an identically granular set of Teams checkboxes exists. If available controls do not fit the trust requirement, the scope decision must change.
Case two: direct removal leaves a group path open

A second fictional review concerns Theo, whose temporary staging support assignment is ending. The captured baseline records a direct View Items grant to the Sandbox Support vault and membership in Support Rotation, a group with read access to that vault. Theo has no proposed editing or management responsibility in this case.
The reviewer first suggests removing only the direct grant. The custom groups documentation says that when someone has vault permissions individually and through a group, the most permissive applies. A narrower direct setting is therefore not an override of a broader group grant. The group path needs its own decision.
| Review state | Direct path | Group path | Documentation-based expectation / status |
|---|---|---|---|
| Captured fictional baseline | Read grant | Support Rotation has read access | Two access paths to inspect |
| First proposed removal | Direct grant removed in proposal | Group membership unchanged | Group still provides access; proposal insufficient |
| Revised proposal | Remove direct vault grant | Remove Theo from this task-specific group after owner approval | Both recorded paths addressed; actual verification pending |
| Other possible paths | Must inspect separately | Other groups or privileges not yet checked | Cannot claim all access has ended |
The revised plan names Nessa as the vault owner and Eli as the Support Rotation group owner. Eli must confirm the group is truly task-specific before removing Theo; it could otherwise support unrelated work. If the group has broader responsibilities, the owners need a different approved membership and vault-access design. The article does not prescribe deleting the group or changing access for every member.
The example also contains an explicit prior-use fact: Theo's fictional handoff says the staging password was copied into an approved local work process during the assignment. No password value or real copy event exists in this article. Theo’s stated prior use keeps the staging-service credential review open; removing vault paths cannot erase a previously learned value.
The completed handoff therefore has two separate work items. Nessa coordinates the vault and group-access review. Rafael, the staging service owner, decides whether an authorized password change, session review, or other service-specific action is needed. Rafael must account for the integration that depends on that staging account before approving a change. Nothing has been revoked, rotated, or tested by this fictional review.
Keep revocation and service changes in separate records
The enforcement documentation notes that after read access has been granted, it cannot be taken away cryptographically; revoking read access is server-enforced. Record a vault-access change as that specific change. Do not turn a saved membership screen or a blocked app action into a claim that all historical information and copies have been erased.
For Theo's case, the filled review register is:
| Work item | Responsible owner | Required evidence before closure | Current authored status |
|---|---|---|---|
| Verify all applicable vault grants | Nessa | Direct and group paths reviewed for the correct identity | Two known paths mapped; wider review pending |
| Decide task-specific group removal | Eli | Unrelated responsibilities checked; removal approved | Decision pending |
| Review previously used staging credential | Rafael | Service permissions, dependencies, and prior-use record assessed | Review requested in the fictional plan |
| Plan any approved service change | Rafael with integration owner | Authorized change window, dependents, verification and fallback | No change approved or performed |
| Verify resulting access | Authorized account owners | Actual checks recorded separately from expectations | Untested |
Updating the vault item alone would leave a service password unchanged unless the service itself was also updated through its authorized process. Conversely, changing a service credential without coordinating dependents could interrupt shared work. Name the service owner and the specific change decision, including dependent integrations, before requesting any approved rotation.
Preserve the previous permission baseline, proposed final state, task end date, and item identifiers in approved storage. Keep secret values out of the review document, screenshots, and general support tickets. A record can say “staging Login item reviewed” without reproducing its username, password, recovery data, or integration key.
If an actual incident or suspected misuse exists, use the organization's security process. This routine task-ending example does not establish compromise, and its paperwork is not a substitute for an incident investigation. The uncertainty should remain visible until the appropriately authorized owners resolve it.
Verify the right identity and report only what happened
When account checks are authorized, compare the intended role with the actual person, account, vault, group memberships, and relevant app settings. Use evidence for the intended teammate identity; an owner’s broader access cannot establish what that teammate can do. Separate viewing an item, changing it, administering membership, and using the connected service; each answers a different question and may have different effects.
The Business reports documentation describes usage reports that include access and item activity, with visibility constrained by permissions. Such evidence can assist a review when available. It is not a declaration that no unrecorded copy exists, and report access must not be assumed merely because someone manages one vault.
For both fictional cases, the observed-account-result field remains blank and explicitly marked untested. The completed outputs are the inventory, proposed matrix, rejected broad scope, two-path removal analysis, and named-owner handoff. An owner can review those concrete decisions before any provisioning or security action occurs.
Save the access boundary and open service decisions alongside the task handover. For related workplace coordination guides, return to LandOffer after recording which checks are complete and which require authorized account-side evidence.


