How to use this documentation
Use this page as an end-user workflow guide. It explains who should use the page, what setup is needed, what steps to follow, what fields matter, and what to check when something looks wrong.
Who should use it
Before you start
- The owner has decided staff responsibilities.
- A trusted admin can manage users and roles.
- Required documents and verification details are available.
- Sensitive permissions such as delete, payment, invoice undo, settings, and reports are understood.
Step-by-step workflow
- 1
Plan role types
Use web for role planning because permission groups and access review are easier on a larger screen.
- 2
Create users
Create or edit users with role, status, contact details, login details, documents, and verification flags.
- 3
Verify web and mobile menus
Ask users to check both platforms after role assignment so missing menus can be corrected early.
- 4
Protect sensitive actions
Restrict settings, role management, password reset, delete, payment, invoice undo, and report access to trusted roles.
- 5
Review access changes
Review active users, inactive users, role changes, documents, agreements, and permissions when staff responsibilities change.
Important fields
Best on web
Role design, permission audit, and full user review.
Best on mobile
Quick user review, status checks, role checks, and troubleshooting menu visibility.
Downstream records
Menus, actions, settings access, invoices, payments, reports, tasks, user documents, and accepted agreements.
Owner review
Active users, owner/admin access, protected roles, document status, and sensitive permissions.
Common mistakes
- Creating users before planning roles.
- Granting broad permissions for convenience.
- Assuming mobile and web menus always use the same visible grouping.
- Forgetting to deactivate users when staff leave.
Troubleshooting
A user can log in but cannot see a menu.
Check active status, assigned role, permission groups, and whether the menu is web-only or mobile-visible.
A sensitive action is visible to the wrong user.
Review the role permissions and remove delete, payment, settings, role, or report permissions as needed.
A role cannot be deleted.
Check whether it is a protected system or default role, then create a custom role instead.
Related documentation
Web dashboard docs
Mobile app equivalents
- Mobile Users and Roles
- Mobile Role-based Access
- Mobile Profile Documents and Agreements
- Mobile Troubleshooting
Screenshot note
- Uses roleBasedAccess from the existing static image set.
Plan roles before creating users
Decide which users are owners, admins, managers, employees, customer users, auditors, and custom role users. Web is best for planning and reviewing permission groups.
Create users and assign access
Create users with role, status, contact details, login details, verification flags, and documents. Mobile can support quick user review and updates when permitted.
Protect sensitive actions
Restrict delete, payment, invoice undo, settings, role management, password reset, and report access to users who should perform those actions.
Review access regularly
Owners should review active users, inactive users, role changes, documents, accepted agreements, and permission scope when staff responsibilities change.
Access control checklist
How Petrodweep connects access control
- Petrodweep uses role permissions to control both web and mobile menus, making access control a platform-wide workflow.
- The workflow helps admins avoid over-permissioning staff while still allowing daily work to happen smoothly.
- User documents, status, password reset, and accepted agreements are included because access control is more than menu visibility.
Frequently asked questions
Why does a user see a menu on web but not mobile?
Check whether the mobile menu uses a separate permission or whether the user's role does not include that action.
Where should roles be managed?
Use web for careful role design and audit. Mobile can support user and role updates when an admin has permission.
What should be reviewed when staff changes?
Review active status, role, permission groups, documents, accepted agreements, password access, and menu visibility.