Custom permissions
Configure role-based access for your organization.
Sales & business operations
Give the next person a clear start.
Give each team member the tools and guidance they need.
For operations managers and workspace administrators
Access follows responsibility
Example permission setup, not fixed system roles.
A working day · example scenario
Giving everyone broad access is easy until someone reaches a task they should not change. Sending a long manual is not enough either. People need the right permissions and guidance that relates to the work in front of them.
Use custom roles and permissions to decide which operations a team member can perform in the organization. The role should match the responsibility.
Use available guided walkthroughs, contextual help and the IEMSuite Academy to orient the teammate. Documentation provides the detailed reference when they need it.
Use recorded actions and stock transaction history to investigate a change. When help is needed, follow the support request from the workspace.
A teammate can learn the available workflow without being handed unrelated operational permissions.
Access and guidance belong in the same workspace. We want a team member to understand the task they are allowed to perform, and an administrator to have records to consult when a change needs explaining.
Explore the stock receiving workflow →Configure role-based access for your organization.
Review recorded actions and stock transactions when investigating a change.
Use contextual help, documentation and available guided walkthroughs.
Follow support requests from the workspace.
No. Organization roles use configurable permissions. Set access around the responsibilities in your team rather than assuming every operator needs the same controls.
The workspace provides contextual help, documentation and available guided walkthroughs through IEMSuite Academy. Support requests can also be followed from the workspace.