Skip to main content

Change owners

There are actually two kinds of owners per asset

There are actually two fields in Atlan that capture the owners of an asset: ownerUsers and ownerGroups.

The examples below illustrate how to change individual (user) owners. To change group owners, replace ownerUsers with ownerGroups.

Change existing asset

Could create a new asset

Remember that Atlan matches the provided qualifiedName to determine whether to update or create the asset.

To change owners on an existing asset:

Change owners on existing asset
models:
- name: TOP_BEVERAGE_USERS # (1)
meta:
atlan:
attributes: # (2)
ownerUsers: ["jsmith", "jdoe"] # (3)
  1. You must of course give the name of the object.

  2. The usernames must be nested within the meta.atlan.attributes structure.

  3. You must provide valid usernames, or email addresses, as a list.

    Users must be valid

If the user doesn't exist in Atlan, there will be no updates to the asset. Please verify the usernames or email addresses in Atlan before assigning them to assets. :::

Remove from existing asset

To remove owners from an existing asset:

Remove owners from existing asset
models:
- name: TOP_BEVERAGE_USERS # (1)
meta:
atlan:
attributes: # (2)
ownerUsers: [ "jdoe" ] # (3)
  1. You must of course give the name of the object.

  2. The details for the owners must be nested within the meta.atlan.attributes structure.

  3. Specify only the usernames or email addresses of the users you want to keep as owners. (Compared to the other examples, this would remove jsmith and keep jdoe.)

    Users must be valid

If the user doesn't exist in Atlan, there will be no updates to the asset. Please verify the usernames or email addresses in Atlan before assigning them to assets. :::

When creating asset

To add owners when creating an asset:

Add owners when creating asset
models:
- name: TOP_BEVERAGE_USERS # (1)
meta:
atlan:
attributes: # (2)
ownerUsers: ["jsmith", "jdoe"] # (3)
  1. You must of course give the name of the object.

  2. The usernames must be nested within the meta.atlan.attributes structure.

  3. You must provide valid usernames, or email addresses, as a list.

    Users must be valid

If the user doesn't exist in Atlan, there will be no updates to the asset. Please verify the usernames or email addresses in Atlan before assigning them to assets. :::

Was this page helpful?