Documentation
Permission groups, Module.Resource.Action keys, and access control.
Last updated 31 August 2026
Job roles map users to permission groups. Baseline examples used in the product docs include administrator, sales, finance, and HR-style roles — you should create only what your company needs.
Permissions use a Module.Resource.Action format, with wildcards and prebuilt groups described in the Permission Model Reference (including a module catalog used by the platform).
Authorization is enforced in the application. Company data is filtered by company scope. Users without a permission should not see or mutate that resource.
Do not grant administrator permissions to test users in production companies.
Platform and tenant administration, including a 4-layer access overview and admin checklist, is covered in the Platform Administration guide.
Expected result: The operation completes without errors and data reflects your changes.
Use the navigation paths and steps in this article. If a menu is missing, check module entitlements and permissions.
Your role may lack the required permission, or the module may not be enabled for your company. Contact an administrator.
Contact the Smart Business 360 team if you cannot find the right guide.