​

Roles and Permissions

ProjectDesk uses roles to keep each user focused on the work they are responsible for.

​

Platform Role

​

Platform Administrator

Platform administrators manage the overall ProjectDesk environment. They can:

• Create client workspaces.
• Create pilot workspaces.
• Access setup tools.
• Assign users to workspaces.
• Manage workspace operations.

​

Workspace Roles

​

Organization Owner

The organization owner is the primary client-side owner of a workspace. They can typically:

• Review workspace progress.
• Manage workspace team access.
• Coordinate project setup.
• Review evidence.
• Track reporting records.

​

HQ Manager

HQ managers coordinate project execution and management oversight. They can typically:

• Create project structure.
• Track activities.
• Review evidence.
• Manage risks.
• Publish stakeholder updates.
• Create reporting records.
• Add workspace members where permitted.

​

MEL Lead

MEL leads focus on evidence quality, indicators, and reporting. They can typically:

• Review evidence.
• Track indicators.
• Monitor data quality.
• Import field data.
• Create reporting records.
• Add risks and stakeholder updates.

​

Field Supervisor

Field supervisors coordinate field execution. They can typically:

• View assigned project structure.
• Submit evidence.
• Review or help correct field submissions where permitted.
• Track field risks and blockers.

​

Field Staff

Field staff are responsible for submitting evidence from field work. They can typically:

• View assigned activities.
• Submit evidence.
• Add field notes.

​

ProjectDesk Services

ProjectDesk services users support client operations. They can typically:

• Review workspace health.
• Assist with evidence and data quality.
• Manage service cases.
• Resolve service cases.
• Support setup and reporting workflows.

​

Donor Viewer

Donor viewers have restricted visibility for stakeholder review. They can typically:

• View workspace progress.
• Review reporting records.
• Inspect stakeholder-facing information.

They should not edit operational records.

​

Auditor Viewer

Auditor viewers have restricted visibility for compliance review. They can typically:

• Inspect reporting records.
• Review evidence status.
• Confirm that records are visible and organized.

They should not edit operational records.

​

Choosing the Right Role

Use the least powerful role that lets the user do their job. For example:

• A person who only needs to inspect progress should be a viewer.
• A person who submits field records should be field staff.
• A person who manages indicators should be MEL lead.
• A person who owns the client relationship should be organization owner or HQ manager.