​

Getting Started

This page explains the first user interaction with ProjectDesk, from visiting the public site to entering the authenticated workspace.

​

First Visit

Most users first encounter ProjectDesk through the public landing page at: https://projectdesk.nywezalabs.com The landing page introduces ProjectDesk as a workspace for field execution, MEL operations, evidence validation, stakeholder reporting, and managed services support. When a user is ready to access the app, they continue to the authenticated app at: https://projectdeskapp.nywezalabs.com

​

Sign In

ProjectDesk is a private workspace. Users sign in before they can see client workspaces or operational data. After a successful sign-in, the app opens the workspace area. If sign-in fails, check that:

• The account exists.
• The email address is entered correctly.
• The password is entered correctly.
• The browser can reach the ProjectDesk API.
• The user has been assigned to at least one workspace, unless they are a platform administrator.

​

First Workspace Experience

After sign-in, the user lands in the ProjectDesk workspace. The screen has these main parts:

• Top actions: user identity and sign out.
• Organizations panel: available client workspaces.
• How this workspace is used: role-specific next steps for the signed-in user.
• Main tabs: a role-specific set of workspace sections.

If the user has access to one or more organizations, the first organization is selected automatically. If no organization is available:

• Platform administrators can create the first workspace.
• Other users should ask a workspace owner or administrator to add them to a workspace.

​

Role-Specific Navigation

ProjectDesk changes the workspace labels and tabs based on the user’s role. This keeps each user focused on the work they are responsible for:

• Platform administrators see platform setup, workspace access, and the full operations console.
• Organization owners and HQ managers see management, access, evidence review, reporting, and escalation tools.
• MEL leads see validation, indicator, evidence, and reporting tools.
• Field supervisors see field planning, field evidence, field status, and escalation tools.
• Field staff see Field Work and Account. Their operations area is focused on their own evidence submissions.
• ProjectDesk services users see a service console, client setup support, evidence support, reporting support, and client access support.
• Donor viewers see a Stakeholder View focused on approved evidence, stakeholder updates, visible risks, and shared reports.
• Auditor viewers see an Assurance View focused on approved evidence and assurance records.

The Team or Workspace Access area is only shown to roles that manage access. Field staff, MEL-only users, donors, and auditors do not see workspace member lists.

​

Creating the First Workspace

A platform administrator can create a client workspace by entering:

• Organization name
• Sector
• Country
• Region
• Primary contact
• Contact email

After creation, the new workspace becomes the active workspace. The recommended next step is to open the Operations tab and create the project structure.

​

Using a Pilot Workspace

Platform administrators can create a pilot workspace from the Setup area. The pilot workspace contains realistic example data for:

• A client organization
• A project
• Field activities
• Evidence submissions
• Indicators
• Risks
• Stakeholder updates

Use a pilot workspace when demonstrating ProjectDesk, training a team, or checking the product flow before setting up a real client workspace.

​

Signing Out

Use the Sign out button in the top actions area. Signing out ends the browser session. The user must sign in again before returning to the workspace.