Integration permissions control your access to different connection pages. These permissions are located in the Group-Connect section of your role settings. These roles are specifically for Warehouse User Accounts.
Check your integration permissions
If you cannot access an integration page, your role doesn't have the required permission ticked. To check your permissions:
Ask an admin to go to Settings then Warehouse User Accounts.
Search for a user then click Actions then Manage Roles.
Navigate to the Group-Connect section.
Review which integration permissions are ticked.
Types of integration permissions
Single permission integrations
Some integrations use one permission that grants all access rights. When ticked, you can view, add, and edit the connection.
Example:
Integration: Connect-Magento.
Role: AdminMagento.
Multiple permission integrations
Other integrations separate permissions by action. Each permission controls a specific function. Example:
Integration: Connect-BigCommerce.
Roles:
AdminBigCommerceAddAccount.
AdminBigCommerceDeleteAccount.
AdminBigCommerceEditAccount.
AdminBigCommerceViewAccounts.
Integration: Connect-Shopify.
Roles:
AdminShopifyAddAccount.
AdminShopifyDeleteAccount.
AdminShopifyEditAccount.
AdminShopifyViewAccounts.
Understanding the role naming convention
Integration role names follow a consistent pattern you can use to identify the correct role for any integration, even if it is not listed as an example above.
Single-permission integrations: Admin[IntegrationName] — for example, AdminMagento or AdminEbay. Multi-permission integrations: Admin[IntegrationName][Action] — for example, AdminShopifyAddAccount or AdminShopifyEditAccount.
Common action suffixes include: AddAccount, EditAccount, DeleteAccount, and ViewAccounts. If you are unsure which role applies to a specific integration, contact the Mintsoft support team with the integration name and the action you need to perform.
API access and 403 Forbidden errors
If you are using the Mintsoft API and receiving a 403 Forbidden error, this means the API key being used belongs to a user account that does not have the required permission for the requested endpoint.
Note the API endpoint returning the 403 error and the HTTP method used (GET, PUT, POST).
Ask a system administrator to go to Settings then Warehouse User Accounts, find the user account associated with the API key, and click Actions then Manage Roles.
In the Group-Connect section, enable the permission that corresponds to the endpoint. API endpoint permissions follow the same structure as the integration page permissions described above.
In a 3PL environment, also confirm the user account is assigned to the correct client account, as client-level access is required for client-scoped API operations.
Note: For a full guide to API user access and permission configuration, see the API - User access and permissions article.