Who on my team can see and do what?
Six roles from director to driver: the menu that follows the role, the direct link that stays closed, the invoice sales can issue but only the accountant can record a payment on, and no shared passwords.
What you get
- The menu follows the role and the active modules
- Issue and collect, prepare and approve: separate rights
- Everyone sets their own password
Transcript
Your team has six roles, from director to driver. Each person's menu is built from their role and the modules you have switched on: the mechanic doesn't see the bank, and sales doesn't see costs and margins.
And it isn't cosmetic. Paste a direct link to such a page, and it stays closed. The data comes from the server, and the server checks the rights itself instead of trusting the screen.
Key operations are separated. Sales can issue an invoice, but cannot record its payment: that right belongs to the accountant. Preparing a payment order and approving it are separate rights, and with two-person approval switched on, whoever prepared an order can no longer approve it.
Only the director can activate a module. And nobody shares passwords: the director sets their own through the link in an e-mail, and a driver signs in to the app with a phone number and a single-use, six-digit code.
Everyone sees their own work and answers for it.