Roles, permissions & security

Access control in PMOlikePRO is not a set of hidden buttons — it is enforced where the data lives, at the database layer, for every read and every write.

The four roles

Role	Sees	Changes
Admin	Everything	Everything, including settings & security
Manager	Everything operational & financial	Projects, tasks, schedules, budgets
Member	Their own projects and shared work	Their tasks, their hours
Viewer	What they are explicitly given	Nothing

Member visibility

Members see only what they should:

• Tasks default to titles-only for work outside their assigned projects, with a per-project override for full visibility.
• Documents gained per-file sharing controls and a Workspace Library visible to all roles.
• Schedule shows their own work and shared-project work — never other people’s private allocations.
• Financial data is never delivered to member or viewer sessions at all.

When a member encounters a task they don’t have access to, they can request access — the relevant managers are notified with a one-click grant.

Guardrails on every destructive action

Every action that changes data irreversibly — deleting a project, removing a team member, merging records, archiving a client — asks for confirmation before proceeding. The most consequential ones (deleting a workspace, removing the last administrator) require typing the name to confirm. Settings lists show how many linked records exist before asking. Nothing in the product deletes or changes data permanently without your explicit go-ahead.

Enforceable two-factor authentication

Any account can enroll in TOTP two-factor authentication (authenticator apps). Admins can go further and require MFA for the whole organization — accounts without a second factor are held at the door until they enroll. Security policy stops being a memo and becomes a property of the system.

The audit trail

Actions that matter — sign-ins, permission changes, destructive operations — are recorded in an audit log, so “who did that, and when?” has an answer. Audit history can be exported for compliance workflows.

The quiet layers

Underneath, the platform runs the defenses you would expect of infrastructure: strict tenant isolation between organizations, rate-limited APIs, bot-challenged sign-in, and encrypted transport everywhere. The security page documents the full posture.

Where to go next

Back to the guide index — or request a demo and see the access model live with your own scenarios.