Team User Permissions Overview

Check out the three functions available to users on a team:

Member Permissions:

  • Organization-wide read-only.
  • Example: A member can view data, but cannot create, edit, or delete any content.

Admin Permissions Without Team Membership:

  • Permissions to create, edit, or delete, except associated products and items.
  • Example: An admin can modify organization settings and manage users, but cannot change product details without being associated with a corresponding team.

Admin Permissions With Team Membership (Member):

  • If you are an admin in the organization and a member of a team, you have limited permissions regarding products.
  • Example: An admin is also a member of a team that is associated with a product. He cannot change product information unless he is an admin or owner on that specific team.

Admin Permissions With Team Membership (Admin or Owner):

  • If admin in the organization and admin or owner in a team associated with the product, you have full permissions for mutations in the product and related items.
  • Example: An admin is also an owner of a team that manages a product. It can make any mutations like releasing an update or discontinuing the product.

Owner Permissions on Team Associated with the Product:

  • Complete freedom to carry out reading and mutation actions in all aspects of the organization.
  • Example: The org owner has complete permission over the entire org without needing to be a member of the team.

If the user is added or removed from a team, or their Role is changed both in the team and in the org, these changes only take effect after they log in to OnePlatform again.

Below is a diagram representing the actions described above:

Check out the three functions available to users on a team:

Member Permissions:

  • Organization-wide read-only.
  • Example: A member can view data, but cannot create, edit, or delete any content.

Admin Permissions Without Team Membership:

  • Permissions to create, edit, or delete, except associated products and items.
  • Example: An admin can modify organization settings and manage users, but cannot change product details without being associated with a corresponding team.

Admin Permissions With Team Membership (Member):

  • If you are an admin in the organization and a member of a team, you have limited permissions regarding products.
  • Example: An admin is also a member of a team that is associated with a product. He cannot change product information unless he is an admin or owner on that specific team.

Admin Permissions With Team Membership (Admin or Owner):

  • If admin in the organization and admin or owner in a team associated with the product, you have full permissions for mutations in the product and related items.
  • Example: An admin is also an owner of a team that manages a product. It can make any mutations like releasing an update or discontinuing the product.

Owner Permissions on Team Associated with the Product:

  • Complete freedom to carry out reading and mutation actions in all aspects of the organization.
  • Example: The org owner has complete permission over the entire org without needing to be a member of the team.

If the user is added or removed from a team, or their Role is changed both in the team and in the org, these changes only take effect after they log in to OnePlatform again.

Below is a diagram representing the actions described above: