Roles and Access Basics
Understand how admins, supervisors, accountants, contractors, clients, and vendors each see a different part of TaameerPro.
Use this when: You need to understand who can see and do what, or you are deciding which role to give someone.
Access in TaameerPro is permission-based. A person can hold one or more roles, and each role unlocks specific actions in specific modules. The system always re-checks permissions, so people only ever see what they are allowed to.
How Access Works
Each role is a bundle of permissions such as “view projects”, “approve payments”, “manage users”, or “update settings”. The menu and buttons a person sees are shaped by the permissions their role gives them.
Hiding a button is only there to reduce confusion. The real protection is on the server: every action is checked again before it is allowed, so access cannot be bypassed by changing the screen.
Roles grant permissions, permissions shape the screen, and the server confirms every action before it runs.
| Role | Typical focus | Common boundaries |
|---|---|---|
| Admin | All modules, users, roles, settings, approvals | Full access; the admin role cannot be locked down |
| Project manager | Projects, stages, schedules, reports | Finance and settings depend on the permissions granted |
| Supervisor or site engineer | Daily reports, inspections, attendance, requisitions | Usually limited to assigned projects |
| Procurement or store | Materials, vendors, orders, deliveries, inventory | Payment approval is often a separate role |
| Finance or accountant | Payments, costs, payroll, reports | Creating purchase orders is often a separate role |
| Client | Read-only project portal | No internal access and no sensitive cost detail |
| Vendor | Their own orders, deliveries, documents, rate proposals | Only the projects and orders that belong to them |
Role-Specific Guidance
Company owner or admin
Own user onboarding, custom roles, settings, approval policies, maintenance windows, and review of high-risk actions.
Supervisor or site engineer
Use projects, daily reports, inspections, requisitions, and attendance to record what happens on site each day.
Accountant or finance manager
Review payments, payroll, cost tracking, budget alerts, and project profitability before money goes out.
Contractor or workforce lead
Work inside assigned projects: attendance, labourer records, agreements, and milestone payment status where allowed.
Client or vendor
Use the secure portal link to see only what is meant for you — project updates and documents for clients, orders and deliveries for vendors.
Important Boundaries
Grant field teams just the actions they need to work quickly; keep payment approval, settings, and role changes to trusted roles.
When you change someone's role or permissions, their access updates almost immediately — older sessions are refreshed automatically.
Client portal links are tied to a single project and are completely separate from your internal accounts.
Vendor portal access is limited to that vendor's own projects, orders, deliveries, documents, and rate proposals.
Least privilege matters
Avoid handing out admin access to solve a single missing permission. Add the specific permission instead — it keeps your company safer and your audit trail clean.