Does a company role automatically unlock every feature?
No. Module entitlements, company context, project scope and action-specific checks also matter.
MPANDO HUB / Platform
Give the right people the right scope of work.
A construction trade network needs clear boundaries between companies, projects and individual responsibilities. MPANDO HUB includes membership, capability, authentication, device and sensitive-action paths. Access decisions depend on the user's company context, enabled modules and project authority; a role label alone does not grant every action.
Who works in the network
- Company administrators assigning user access
- Project managers controlling project teams
- Finance and platform operators handling sensitive workflows
A practical workflow
- Establish the company membership and account identity.
- Assign the relevant organisational role and module scope.
- Grant access to the appropriate project or business process.
- Apply additional authentication or approval to sensitive actions where configured.
- Review support and activity records under the applicable access policy.
What the workflow helps clarify
- Clarify which company and project a user is acting for.
- Reduce ambiguity between a visible screen and permission to change a record.
- Give administrators a basis to review sensitive access.
Scope and limits
- MFA and device controls depend on account and company configuration.
- Source-level security features are not a security certification or penetration-test result.
- Backup interfaces do not prove a completed restore rehearsal.
- Private account, customer and project records are excluded from public search pages.
Questions and answers
Can MPANDO HUB claim a security certification?
No certification is asserted in this content. Specific security evidence can be provided through the appropriate review process.