Skip to main content

Managing Permissions by Role

Configure what each role can access and manage across SubBase.

Written by Andrew Rapinchuk
Updated over 3 months ago

This article explains how Admins control role-based permissions across Orders, Invoices, Commitments, Inventory-related actions, Mobile, and Other platform areas using the Permissions tab.


Overview

Permissions allow you to define what different roles can view, create, edit, or manage across SubBase. Permissions are configured by role and applied consistently across projects, ensuring users only have access to the actions they need.

If you have questions about what a specific permission does or whether it should be enabled, first check whether the permission includes a built-in definition by hovering over the information icon. If you still need clarification, use the in-app help to get assistance before making changes.


Who Can Do This

  • Admin โ€“ Full access to view and update all permission settings. The Permissions sub-tab is only visible to Admins.

  • Purchaser, User, Material Requester โ€“ Permissions are assigned to these roles but cannot be viewed or edited by them.


Before You Start

  • You must be logged in as an Admin

  • Permission changes do not take effect until Save Changes is selected


Steps to Manage Permissions by Role

Step 1: Open the Permissions page

From the User Profile Menu, select Company Settings.

Note: The Permissions sub-tab is only available to Admin users.

Select the Permissions tab.


Step 2: Select a permission category

Use the category tabs to switch between permission groups:

  • Orders

  • Invoices

  • Commitments

  • Mobile

  • Other

  • Inventory

  • Material Requests

Note: Permissions only exist for features that are enabled for your company. If a feature is not enabled, its permissions will not appear.

Each category displays a matrix of permissions by role.


Step 3: Configure Orders permissions

Orders permissions define what actions each role can take on orders and RFQs, such as creating drafts, sending RFQs or orders, editing delivery details, managing materials, approving requests, and viewing pricing.

Use this section to ensure users have the appropriate level of access based on their responsibilities.


Step 4: Configure Invoice permissions

Invoice permissions control how users interact with invoices, including viewing, editing, deleting, posting, syncing with ERP systems, and managing invoice workflow.

Assign these permissions carefully to limit access to sensitive financial actions.


Step 5: Configure Commitment permissions

Commitment permissions determine who can view, create, edit, cancel, or reopen material commitments, including access to commitment history and versions.

Use these permissions to control responsibility for commitment lifecycle management.


Step 6: Configure Mobile permissions

Mobile permissions control which actions users can perform within the SubBase mobile experience, such as submitting delivery receipts or editing mobile requests.


Step 7: Configure Inventory permissions

Inventory permissions control access to inventory stock, warehouse management, and inventory-related requests.

Use these permissions to manage who can view and update stock levels, maintain warehouse locations, and create or manage consumable and asset requests.


Step 8: Configure Other permissions

Other permissions control visibility of key platform areas, such as the Calendar and Dashboard tabs.

Use these permissions to tailor the navigation experience by role.


Step 9: Save your changes

Select Save Changes to apply updates across your organization.


Troubleshooting

Changes did not apply

Ensure Save Changes was selected after updating permissions.

A user still cannot perform an action

Verify the userโ€™s assigned role and confirm the relevant permission toggle is enabled.

I am unsure which permissions to enable

If you are unsure about the impact of a permission or how it should be configured, use the in-app help to get guidance before making changes.


FAQs

Do permission changes affect existing projects?

Yes. Permissions apply across all projects immediately after saving.

Can permissions be customized per user?

No. Permissions are assigned by role, not by individual user.

Did this answer your question?