Control Access

You do not need any privileges to create a company. Every company you create is private by default. You have admin privileges to that company and all namespaces and schemas within that company. Use PATCH Change Company Permissions to specify who (users) and what (apps) has read, write, and create permission within the company.

Every namespace you create is private by default. As its creator, you have read, write, and delete access to the namespace. Use PATCH Change Company Permissions to specify who (users) and what (apps) has read, write, and create permission within that namespace.

You can grant access privileges to apps by their client ID. You can also grant access to users by:

Directly granting access to their Autodesk ID (Oxygen ID).
Granting access to the Oxygen Group they belong to.
Granting access to the Oxygen Tenant that their Oxygen Group belongs to.

When you grant access, specify the privileges you want the user or the app to have. The following table summarizes the privileges that you can grant.

+--------------------+---------------------------------------------------------------------------------+---------------------------------------------------------------------------------+ | Privilege | Impact on Company | Impact on Namespace | +====================+=================================================================================+=================================================================================+ | Read | - List all namespaces and schema within the company. | - List all schema within the namespace. | | | - Query all namespaces and schema within the company. | - Query all schema within the namespace. | | | - Fetch metadata of namespaces and schema within the company. | - Fetch metadata of schema within the namespace. | | | - Fetch all schema within the company. | - Fetch all schema within the namespace. | | | - Fetch Tags, Tag Categories, and Tag Associations that belong to the | - Fetch Tags, Tag Categories, and Tag Associations that belong to the | | | company and namespaces under it. | namespace. | +--------------------+---------------------------------------------------------------------------------+---------------------------------------------------------------------------------+ | Write | - Update the metadata of the company, and the namespaces and schema | - Update metadata of the namespace and schema within the namespace. | | | within the company. | | | | - Create namespaces and schema within the company. | - Create schema within the namespace. | | | - Delete namespaces and schema within the company. | - Delete schema within the namespace. | | | - Create, modify or delete Tags within the company. | - Create, modify or delete Tags within the namespace. | | | - Create and delete Tag Associations between Tags and schema within the | - Create, and delete Tag Associations between Tags and schema within the | | | company. | namespace. | +--------------------+---------------------------------------------------------------------------------+---------------------------------------------------------------------------------+ | Admin | - All operations possible with Read and Write. | - All operations possible with Read and Write. | | | - Change permissions of the company and namespaces within the company. | - Update metadata of the namespace and schema within the namespace. | | | - Add schema that exists within one namespace to another. | - Create schema within the namespace. | | | - Create, modify, and delete Tag Categories and Tag Collections | - Create, modify, and delete Tag Categories and Tag Collections. | | | that belong to the company. | that belong to the namespace. | | | | | | | | | | | | | | | | | | | | | | | | | +--------------------+---------------------------------------------------------------------------------+---------------------------------------------------------------------------------+ | Delete | - Extra capability to delete a company all the way down to schema-level. | - Extra capability to delete a namespace all the way down to schema-level. | | | Intended for GDPR purposes only. Must be used with caution. | Intended for GDPR purposes only. Must be used with caution. | +--------------------+---------------------------------------------------------------------------------+---------------------------------------------------------------------------------+