​

Workspace Guide

The workspace is the private operating area of ProjectDesk. It is where users coordinate organization workspaces, projects, field evidence, reporting, access, and service support.

​

Workspace Header

The header confirms that the user is in the ProjectDesk workspace. It also shows the signed-in user’s name and the Sign out action. The header description explains the main structure: select a client workspace, then use the tabs available to your role.

​

Organizations Panel

The Organizations panel lists every client workspace the user can access. Each organization card shows:

• Organization name
• The user’s role or access type in that workspace

Selecting an organization changes the active context for the rest of the page. The workspace tabs refer to the selected organization. The Account tab refers to the signed-in user.

​

How This Workspace Is Used

This guidance panel is tailored to the signed-in user’s role. For example:

• Platform administrators see workspace setup, access, delivery check, and release readiness guidance.
• Organization owners and HQ managers see governance, coordination, access, and reporting guidance.
• MEL leads see evidence definition, validation, indicator, and reporting guidance.
• Field supervisors see assignment, evidence, blocker, and review follow-up guidance.
• Field staff see activity, evidence submission, submission status, and account guidance.
• ProjectDesk services users see case triage, evidence support, coordination, and access support guidance.
• Donor viewers see stakeholder review guidance.
• Auditor viewers see assurance review guidance.

It exists so users understand what to do next without seeing responsibilities that belong to another role.

​

Overview Tab

The Overview tab answers: “What is happening in this workspace?” It includes:

• Active client workspace details
• Role badge
• Sector, country, region, primary contact, and contact email
• Managed services status
• Workspace metrics
• Next workspace workflows

Use Overview at the start of the day, before a status meeting, or whenever you need a quick orientation.

​

Operations Area

The operations area is where most work happens. Its name and sections change by role. Depending on the role, it may be called Operations Console, Delivery Control, Delivery Management, MEL Workspace, Field Operations, Field Work, Service Console, Stakeholder View, or Assurance View. A user may see some or all of these sections:

• Setup or work planning sections for users who manage project structure.
• Evidence sections for users who submit, review, or inspect approved evidence.
• Reporting sections for managers, MEL users, services users, donors, and auditors.
• Services or escalation sections for users who can raise or resolve ProjectDesk support cases.

Field staff only see My Evidence in this area. Donors and auditors see read-only evidence and reporting sections.

​

Workspace Access

The Workspace Access or Client Access tab controls workspace membership. This area is only shown to platform administrators, organization owners, HQ managers, and ProjectDesk services users. Users with permission can add people to the active workspace and choose their role. If the email address already belongs to a ProjectDesk account, the user is added without changing their password. If the email address does not belong to an account yet, ProjectDesk creates the account and shows a temporary password. The workspace manager should copy the credentials and send them to the person through an appropriate secure channel. The member list shows:

• Name or email
• Email address
• Workspace role

Use Workspace Access whenever a new person needs access or a user’s role needs to be changed.

​

Account Tab

The Account tab lets the signed-in user update their own name, email address, and password. Users added with a temporary password should open Account after first sign-in and change that password.

​

Setup Tab

The Setup tab is mainly for platform administrators. It includes:

• Pilot workspace creation
• New workspace creation

Use Setup when onboarding a new organization or creating a realistic pilot environment for demonstration or training.

​

Empty States

ProjectDesk uses empty states when there is no data yet. An empty state is not an error. It usually means the next setup step has not been completed. For example:

• “No client projects yet” means a project should be created.
• “No field evidence submitted yet” means activities exist but no evidence has been submitted.
• “No managed service cases open” means there are no active support issues.