Skip to Content
How-to guidesChange the owner of a resource

Change the owner of a resource

Hand a resource to the right owner in seconds. Someone leaves the team and their credentials need a new home. A prototype manifest becomes something the whole team relies on. Move it, and the people who should manage it can. Credentials, manifests, stacks, and similar resources have one owner: a person, a team, or the organization. The owner decides who can edit, rotate, or delete the resource.

Before you start

  • Role: you manage the resource’s current owner and the new owner. You can pick yourself, teams you lead (every live team, if you are an org admin), and the organization (org admins only).
  • Stacks move from their card in Stacks, by admins and owners.

Steps

Move a credential

  1. In the left rail, open Connections.
  2. Click Share on the credential’s row.
  3. In Who has access, find the first row, the one with the Owner label. Click Change.
  4. In the Change owner of window, choose the new owner: You, Team plus a team name, or Organization.
  5. Click Move to followed by the owner’s name.

Credentials from a Vault connection and HTTP secrets use the same window. A connection you made by signing in acts as you, so it stays yours.

Move a manifest

  1. In the left rail, open Manifests.
  2. Open the row menu (More actions) and choose Move. You only see Move on manifests you can manage.
  3. Choose the new owner and click Move to followed by the owner’s name.

A manifest owned by one person is private to them. To give a colleague a copy of a personal manifest instead, use Send a copy in the same menu.

Move a stack

On the stack’s card in Stacks, click Move. Choose the new owner and click Move to followed by the owner’s name.

What you should see

  • The window closes and the resource appears in its new owner’s group on the list page. Lists are grouped by owner: you, your teams, then the organization.
  • The window states what happens next: after the move, only the new owner’s managers can edit, rotate, or delete it. Existing shares stay.

Next

Share a credential with a team: give other teams use of it without moving it.

Share a credential with a teamCreate an API key