Skip to main content
Anchor to CustomDataAccessPermissionType

CustomDataAccessPermissionType

enum

Permission Enum that defines level of access to a definition or namespaces a client has.

  • Allows a client to share the field with other clients
  • Allows a client to write or edit data stored in the field on users
  • Allows a client to read data stored in the field on users
  • Allows a client to alias its own keys

If on a Metafield Namespace:

  • Allows a client to share (or revoke) the namespace with other clients
  • Allows a client to delete the namespace (member primitives are not deleted)
  • Allows a client access to any primitive in the namespace at the same level of access given to the namespace
  • Allows a client to read data stored in the field on users
  • Allows a client to alias its own keys

If on a Metafield Namespace:

  • Allows a client access to any primitive in the namespace at the same level of access given to the namespace

Aliased to 'WRITE'

  • Allows a client to write or edit data stored in the field on users
  • Allows a client to read data stored in the field on users
  • Allows a client to alias its own keys

If on a Metafield Namespace:

  • Allows a client to share (or revoke) primitives into the namespace.
  • Allows a client access to any primitive in the namespace at the same level of access given to the namespace

Was this section helpful?

•OBJECT

Defines an AccessGrant by absolute path using Global Identifier (GID) to represent access to a Custom Data Primitive.

•INPUT OBJECT

Defines a single AccessGrant which is one_of(granteeId, grantee, or role) and a grant.

•INPUT OBJECT

Access for Shop Custom Data primitives is composed of AccessGrants and/or a default permission that applies to any client using the API.

AccessInput defines a set of AccessGrants and/or a default permission level.

•OBJECT

Access for Shop Custom Data primitives is composed of AccessGrants and/or a default permission that applies to any client using the API.

•OBJECT

Defines an AccessGrant by relative path using a key a Client has access to, to represent access to a Custom Data Primitive.


Was this section helpful?