Overview

Project Manager is the planning and delivery workspace in DawnDesk. It is designed for users who need a practical place to manage backlog items, board status, sprints, roadmap dates, project strategies, reports, comments, versions, and workspace settings.

How to use this guide

Read the workflow that matches what you are trying to do, follow the steps in order, then check the confirmation or output before moving to another DawnDesk workspace.

flowchart TD Start[Open Project Manager] --> Input[Enter or select user content] Input --> Review[Review the current panel] Review --> Action[Run the main action] Action --> Save[Save, export, copy, or update] Save --> Confirm[Check confirmation or recent activity] Confirm --> Continue[Continue using project-manager]

Image Placeholders

Replace these URLs with actual DawnDesk screenshots when they are ready.

Project Manager Documentation placeholder 1

Project Manager Documentation placeholder 2

Project Manager Documentation placeholder 3

Quick Start

Open Project Manager from the Dashboard.
Choose the option to initialize a new project environment.
Enter the project name and any required details.
Save the project.
Open the project from the list to start adding work.

Core Workflows

Create a project workspace

Use this workflow when you want to create a project workspace in DawnDesk with a clear beginning, result, and confirmation step.

flowchart TD Start[Open Create a project workspace] --> Input[Enter or select user content] Input --> Review[Review the current panel] Review --> Action[Run the main action] Action --> Save[Save, export, copy, or update] Save --> Confirm[Check confirmation or recent activity] Confirm --> Continue[Continue using project-manager]

#### Steps

Open Project Manager from the Dashboard.
Choose the option to initialize a new project environment.
Enter the project name and any required details.
Save the project.
Open the project from the list to start adding work.

#### What To Check

Step 1: After this step, DawnDesk should show progress toward create a project workspace.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 2: After this step, DawnDesk should show progress toward create a project workspace.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 3: After this step, DawnDesk should show progress toward create a project workspace.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 4: After this step, DawnDesk should show progress toward create a project workspace.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 5: After this step, DawnDesk should show progress toward create a project workspace.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change. #### Completion Checklist

The user knows where to start.
The required data, file, or record is selected.
The action completes without an unresolved error.
The result is visible, saved, exported, copied, or logged.
The user knows what to do next.

Import a project export

Use this workflow when you want to import a project export in DawnDesk with a clear beginning, result, and confirmation step.

flowchart TD Start[Open Import a project export] --> Input[Enter or select user content] Input --> Review[Review the current panel] Review --> Action[Run the main action] Action --> Save[Save, export, copy, or update] Save --> Confirm[Check confirmation or recent activity] Confirm --> Continue[Continue using project-manager]

#### Steps

Open the project list screen.
Choose the import action.
Select a DawnDesk project JSON export.
Review the imported project after DawnDesk maps records into the current workspace.
Open backlog, sprints, issues, versions, and strategies to confirm the import.

#### What To Check

Step 1: After this step, DawnDesk should show progress toward import a project export.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 2: After this step, DawnDesk should show progress toward import a project export.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 3: After this step, DawnDesk should show progress toward import a project export.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 4: After this step, DawnDesk should show progress toward import a project export.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 5: After this step, DawnDesk should show progress toward import a project export.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change. #### Completion Checklist

The user knows where to start.
The required data, file, or record is selected.
The action completes without an unresolved error.
The result is visible, saved, exported, copied, or logged.
The user knows what to do next.

Plan a backlog

Use this workflow when you want to plan a backlog in DawnDesk with a clear beginning, result, and confirmation step.

flowchart TD Start[Open Plan a backlog] --> Input[Enter or select user content] Input --> Review[Review the current panel] Review --> Action[Run the main action] Action --> Save[Save, export, copy, or update] Save --> Confirm[Check confirmation or recent activity] Confirm --> Continue[Continue using project-manager]

#### Steps

Open a project.
Go to Backlog.
Create issues for work that needs attention.
Set type, status, priority, story points, estimate, due date, and rank when available.
Drag or update items to keep the work ordered.

#### What To Check

Step 1: After this step, DawnDesk should show progress toward plan a backlog.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 2: After this step, DawnDesk should show progress toward plan a backlog.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 3: After this step, DawnDesk should show progress toward plan a backlog.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 4: After this step, DawnDesk should show progress toward plan a backlog.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 5: After this step, DawnDesk should show progress toward plan a backlog.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change. #### Completion Checklist

The user knows where to start.
The required data, file, or record is selected.
The action completes without an unresolved error.
The result is visible, saved, exported, copied, or logged.
The user knows what to do next.

Run a sprint

Use this workflow when you want to run a sprint in DawnDesk with a clear beginning, result, and confirmation step.

flowchart TD Start[Open Run a sprint] --> Input[Enter or select user content] Input --> Review[Review the current panel] Review --> Action[Run the main action] Action --> Save[Save, export, copy, or update] Save --> Confirm[Check confirmation or recent activity] Confirm --> Continue[Continue using project-manager]

#### Steps

Open Backlog.
Create a sprint with a name, start date, and end date.
Assign issues to the sprint.
Start the sprint when the team is ready.
Open Board to move sprint issues through workflow columns.
Complete the sprint when finished.

#### What To Check

Step 1: After this step, DawnDesk should show progress toward run a sprint.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 2: After this step, DawnDesk should show progress toward run a sprint.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 3: After this step, DawnDesk should show progress toward run a sprint.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 4: After this step, DawnDesk should show progress toward run a sprint.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 5: After this step, DawnDesk should show progress toward run a sprint.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 6: After this step, DawnDesk should show progress toward run a sprint.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change. #### Completion Checklist

The user knows where to start.
The required data, file, or record is selected.
The action completes without an unresolved error.
The result is visible, saved, exported, copied, or logged.
The user knows what to do next.

Use reports

Use this workflow when you want to use reports in DawnDesk with a clear beginning, result, and confirmation step.

flowchart TD Start[Open Use reports] --> Input[Enter or select user content] Input --> Review[Review the current panel] Review --> Action[Run the main action] Action --> Save[Save, export, copy, or update] Save --> Confirm[Check confirmation or recent activity] Confirm --> Continue[Continue using project-manager]

#### Steps

Open Reports in a project.
Review project health, status totals, priority mix, burndown, velocity, and other available report panels.
Use the report data to decide what needs attention.
Return to Backlog or Board to adjust work based on the report.

#### What To Check

Step 1: After this step, DawnDesk should show progress toward use reports.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 2: After this step, DawnDesk should show progress toward use reports.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 3: After this step, DawnDesk should show progress toward use reports.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 4: After this step, DawnDesk should show progress toward use reports.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change. #### Completion Checklist

The user knows where to start.
The required data, file, or record is selected.
The action completes without an unresolved error.
The result is visible, saved, exported, copied, or logged.
The user knows what to do next.

Write strategy notes

Use this workflow when you want to write strategy notes in DawnDesk with a clear beginning, result, and confirmation step.

flowchart TD Start[Open Write strategy notes] --> Input[Enter or select user content] Input --> Review[Review the current panel] Review --> Action[Run the main action] Action --> Save[Save, export, copy, or update] Save --> Confirm[Check confirmation or recent activity] Confirm --> Continue[Continue using project-manager]

#### Steps

Open Strategies.
Create a strategy page.
Write Markdown or use the configured AI provider to draft a plan.
Review the generated text carefully.
Save the strategy so it stays attached to the project.

#### What To Check

Step 1: After this step, DawnDesk should show progress toward write strategy notes.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 2: After this step, DawnDesk should show progress toward write strategy notes.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 3: After this step, DawnDesk should show progress toward write strategy notes.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 4: After this step, DawnDesk should show progress toward write strategy notes.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change.

Step 5: After this step, DawnDesk should show progress toward write strategy notes.

- If it fails: Read the visible error, check required fields, and retry with the smallest possible change. #### Completion Checklist

The user knows where to start.
The required data, file, or record is selected.
The action completes without an unresolved error.
The result is visible, saved, exported, copied, or logged.
The user knows what to do next.

Workspace Areas

How to use Project list

Project list is part of Project Manager. This section explains how to approach the view, what to check first, how to complete the main action, and how to recover when something looks wrong.

flowchart TD Start[Open Project list] --> Input[Enter or select user content] Input --> Review[Review the current panel] Review --> Action[Run the main action] Action --> Save[Save, export, copy, or update] Save --> Confirm[Check confirmation or recent activity] Confirm --> Continue[Continue using project-manager]

#### How To Use This Area

Use Project list when you need to complete the related DawnDesk task without leaving the Project Manager workspace.
Start by reading the labels on the panel, because DawnDesk keeps the primary action near the current view.
Enter only the information needed for the current step, then save, export, copy, or review the result before moving on.
If a save dialog opens, choose a clear filename and keep the default extension unless your workflow requires a different one.
After completing the action, check the confirmation message or the recent activity log so you know the operation finished.
When the result affects another workspace, return to the Dashboard and open the next module from there.
If the panel appears empty, create the first record, import an existing file, or remove filters that may be hiding content.
For repeated work, use consistent naming so search, reports, and exports stay understandable later.

#### Practical Tips

Tip 1: keep the Project list result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 1: leaving Project list before checking whether the action produced the expected visible result.
Recovery 1: return to Project list, repeat the last action with a smaller change, and check the activity or status message.
Tip 2: keep the Project list result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 2: leaving Project list before checking whether the action produced the expected visible result.
Recovery 2: return to Project list, repeat the last action with a smaller change, and check the activity or status message.
Tip 3: keep the Project list result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 3: leaving Project list before checking whether the action produced the expected visible result.
Recovery 3: return to Project list, repeat the last action with a smaller change, and check the activity or status message.
Tip 4: keep the Project list result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 4: leaving Project list before checking whether the action produced the expected visible result.
Recovery 4: return to Project list, repeat the last action with a smaller change, and check the activity or status message.
Tip 5: keep the Project list result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 5: leaving Project list before checking whether the action produced the expected visible result.
Recovery 5: return to Project list, repeat the last action with a smaller change, and check the activity or status message.
Tip 6: keep the Project list result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 6: leaving Project list before checking whether the action produced the expected visible result.
Recovery 6: return to Project list, repeat the last action with a smaller change, and check the activity or status message.
Tip 7: keep the Project list result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 7: leaving Project list before checking whether the action produced the expected visible result.
Recovery 7: return to Project list, repeat the last action with a smaller change, and check the activity or status message.
Tip 8: keep the Project list result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 8: leaving Project list before checking whether the action produced the expected visible result.
Recovery 8: return to Project list, repeat the last action with a smaller change, and check the activity or status message.

#### Checklist

The correct Project list panel is open.
Required fields are filled in.
The main action button is enabled.
The result has been reviewed before leaving the view.
Any saved file uses the expected extension.
The recent activity log or status message confirms completion.

#### Troubleshooting

If Project list is blank, check whether this workspace needs a created record, selected project, selected file, or cloud sign-in.
If Project list does not save, choose a writable folder and keep the extension DawnDesk suggests.
If Project list shows old information, refresh the workspace or leave and reopen the module.
If Project list uses AI, confirm the provider is configured in Settings before retrying.
If Project list exports a file, open the file after saving to confirm the output is usable.

How to use Project dashboard

Project dashboard is part of Project Manager. This section explains how to approach the view, what to check first, how to complete the main action, and how to recover when something looks wrong.

Project dashboard screenshot placeholder

flowchart TD Start[Open Project dashboard] --> Input[Enter or select user content] Input --> Review[Review the current panel] Review --> Action[Run the main action] Action --> Save[Save, export, copy, or update] Save --> Confirm[Check confirmation or recent activity] Confirm --> Continue[Continue using project-manager]

#### How To Use This Area

Use Project dashboard when you need to complete the related DawnDesk task without leaving the Project Manager workspace.
Start by reading the labels on the panel, because DawnDesk keeps the primary action near the current view.
Enter only the information needed for the current step, then save, export, copy, or review the result before moving on.
If a save dialog opens, choose a clear filename and keep the default extension unless your workflow requires a different one.
After completing the action, check the confirmation message or the recent activity log so you know the operation finished.
When the result affects another workspace, return to the Dashboard and open the next module from there.
If the panel appears empty, create the first record, import an existing file, or remove filters that may be hiding content.
For repeated work, use consistent naming so search, reports, and exports stay understandable later.

#### Practical Tips

Tip 1: keep the Project dashboard result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 1: leaving Project dashboard before checking whether the action produced the expected visible result.
Recovery 1: return to Project dashboard, repeat the last action with a smaller change, and check the activity or status message.
Tip 2: keep the Project dashboard result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 2: leaving Project dashboard before checking whether the action produced the expected visible result.
Recovery 2: return to Project dashboard, repeat the last action with a smaller change, and check the activity or status message.
Tip 3: keep the Project dashboard result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 3: leaving Project dashboard before checking whether the action produced the expected visible result.
Recovery 3: return to Project dashboard, repeat the last action with a smaller change, and check the activity or status message.
Tip 4: keep the Project dashboard result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 4: leaving Project dashboard before checking whether the action produced the expected visible result.
Recovery 4: return to Project dashboard, repeat the last action with a smaller change, and check the activity or status message.
Tip 5: keep the Project dashboard result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 5: leaving Project dashboard before checking whether the action produced the expected visible result.
Recovery 5: return to Project dashboard, repeat the last action with a smaller change, and check the activity or status message.
Tip 6: keep the Project dashboard result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 6: leaving Project dashboard before checking whether the action produced the expected visible result.
Recovery 6: return to Project dashboard, repeat the last action with a smaller change, and check the activity or status message.
Tip 7: keep the Project dashboard result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 7: leaving Project dashboard before checking whether the action produced the expected visible result.
Recovery 7: return to Project dashboard, repeat the last action with a smaller change, and check the activity or status message.
Tip 8: keep the Project dashboard result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 8: leaving Project dashboard before checking whether the action produced the expected visible result.
Recovery 8: return to Project dashboard, repeat the last action with a smaller change, and check the activity or status message.

#### Checklist

The correct Project dashboard panel is open.
Required fields are filled in.
The main action button is enabled.
The result has been reviewed before leaving the view.
Any saved file uses the expected extension.
The recent activity log or status message confirms completion.

#### Troubleshooting

If Project dashboard is blank, check whether this workspace needs a created record, selected project, selected file, or cloud sign-in.
If Project dashboard does not save, choose a writable folder and keep the extension DawnDesk suggests.
If Project dashboard shows old information, refresh the workspace or leave and reopen the module.
If Project dashboard uses AI, confirm the provider is configured in Settings before retrying.
If Project dashboard exports a file, open the file after saving to confirm the output is usable.

How to use Backlog

Backlog is part of Project Manager. This section explains how to approach the view, what to check first, how to complete the main action, and how to recover when something looks wrong.

flowchart TD Start[Open Backlog] --> Input[Enter or select user content] Input --> Review[Review the current panel] Review --> Action[Run the main action] Action --> Save[Save, export, copy, or update] Save --> Confirm[Check confirmation or recent activity] Confirm --> Continue[Continue using project-manager]

#### How To Use This Area

Use Backlog when you need to complete the related DawnDesk task without leaving the Project Manager workspace.
Start by reading the labels on the panel, because DawnDesk keeps the primary action near the current view.
Enter only the information needed for the current step, then save, export, copy, or review the result before moving on.
If a save dialog opens, choose a clear filename and keep the default extension unless your workflow requires a different one.
After completing the action, check the confirmation message or the recent activity log so you know the operation finished.
When the result affects another workspace, return to the Dashboard and open the next module from there.
If the panel appears empty, create the first record, import an existing file, or remove filters that may be hiding content.
For repeated work, use consistent naming so search, reports, and exports stay understandable later.

#### Practical Tips

Tip 1: keep the Backlog result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 1: leaving Backlog before checking whether the action produced the expected visible result.
Recovery 1: return to Backlog, repeat the last action with a smaller change, and check the activity or status message.
Tip 2: keep the Backlog result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 2: leaving Backlog before checking whether the action produced the expected visible result.
Recovery 2: return to Backlog, repeat the last action with a smaller change, and check the activity or status message.
Tip 3: keep the Backlog result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 3: leaving Backlog before checking whether the action produced the expected visible result.
Recovery 3: return to Backlog, repeat the last action with a smaller change, and check the activity or status message.
Tip 4: keep the Backlog result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 4: leaving Backlog before checking whether the action produced the expected visible result.
Recovery 4: return to Backlog, repeat the last action with a smaller change, and check the activity or status message.
Tip 5: keep the Backlog result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 5: leaving Backlog before checking whether the action produced the expected visible result.
Recovery 5: return to Backlog, repeat the last action with a smaller change, and check the activity or status message.
Tip 6: keep the Backlog result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 6: leaving Backlog before checking whether the action produced the expected visible result.
Recovery 6: return to Backlog, repeat the last action with a smaller change, and check the activity or status message.
Tip 7: keep the Backlog result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 7: leaving Backlog before checking whether the action produced the expected visible result.
Recovery 7: return to Backlog, repeat the last action with a smaller change, and check the activity or status message.
Tip 8: keep the Backlog result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 8: leaving Backlog before checking whether the action produced the expected visible result.
Recovery 8: return to Backlog, repeat the last action with a smaller change, and check the activity or status message.

#### Checklist

The correct Backlog panel is open.
Required fields are filled in.
The main action button is enabled.
The result has been reviewed before leaving the view.
Any saved file uses the expected extension.
The recent activity log or status message confirms completion.

#### Troubleshooting

If Backlog is blank, check whether this workspace needs a created record, selected project, selected file, or cloud sign-in.
If Backlog does not save, choose a writable folder and keep the extension DawnDesk suggests.
If Backlog shows old information, refresh the workspace or leave and reopen the module.
If Backlog uses AI, confirm the provider is configured in Settings before retrying.
If Backlog exports a file, open the file after saving to confirm the output is usable.

How to use Board

Board is part of Project Manager. This section explains how to approach the view, what to check first, how to complete the main action, and how to recover when something looks wrong.

flowchart TD Start[Open Board] --> Input[Enter or select user content] Input --> Review[Review the current panel] Review --> Action[Run the main action] Action --> Save[Save, export, copy, or update] Save --> Confirm[Check confirmation or recent activity] Confirm --> Continue[Continue using project-manager]

#### How To Use This Area

Use Board when you need to complete the related DawnDesk task without leaving the Project Manager workspace.
Start by reading the labels on the panel, because DawnDesk keeps the primary action near the current view.
Enter only the information needed for the current step, then save, export, copy, or review the result before moving on.
If a save dialog opens, choose a clear filename and keep the default extension unless your workflow requires a different one.
After completing the action, check the confirmation message or the recent activity log so you know the operation finished.
When the result affects another workspace, return to the Dashboard and open the next module from there.
If the panel appears empty, create the first record, import an existing file, or remove filters that may be hiding content.
For repeated work, use consistent naming so search, reports, and exports stay understandable later.

#### Practical Tips

Tip 1: keep the Board result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 1: leaving Board before checking whether the action produced the expected visible result.
Recovery 1: return to Board, repeat the last action with a smaller change, and check the activity or status message.
Tip 2: keep the Board result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 2: leaving Board before checking whether the action produced the expected visible result.
Recovery 2: return to Board, repeat the last action with a smaller change, and check the activity or status message.
Tip 3: keep the Board result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 3: leaving Board before checking whether the action produced the expected visible result.
Recovery 3: return to Board, repeat the last action with a smaller change, and check the activity or status message.
Tip 4: keep the Board result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 4: leaving Board before checking whether the action produced the expected visible result.
Recovery 4: return to Board, repeat the last action with a smaller change, and check the activity or status message.
Tip 5: keep the Board result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 5: leaving Board before checking whether the action produced the expected visible result.
Recovery 5: return to Board, repeat the last action with a smaller change, and check the activity or status message.
Tip 6: keep the Board result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 6: leaving Board before checking whether the action produced the expected visible result.
Recovery 6: return to Board, repeat the last action with a smaller change, and check the activity or status message.
Tip 7: keep the Board result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 7: leaving Board before checking whether the action produced the expected visible result.
Recovery 7: return to Board, repeat the last action with a smaller change, and check the activity or status message.
Tip 8: keep the Board result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 8: leaving Board before checking whether the action produced the expected visible result.
Recovery 8: return to Board, repeat the last action with a smaller change, and check the activity or status message.

#### Checklist

The correct Board panel is open.
Required fields are filled in.
The main action button is enabled.
The result has been reviewed before leaving the view.
Any saved file uses the expected extension.
The recent activity log or status message confirms completion.

#### Troubleshooting

If Board is blank, check whether this workspace needs a created record, selected project, selected file, or cloud sign-in.
If Board does not save, choose a writable folder and keep the extension DawnDesk suggests.
If Board shows old information, refresh the workspace or leave and reopen the module.
If Board uses AI, confirm the provider is configured in Settings before retrying.
If Board exports a file, open the file after saving to confirm the output is usable.

How to use Reports

Reports is part of Project Manager. This section explains how to approach the view, what to check first, how to complete the main action, and how to recover when something looks wrong.

flowchart TD Start[Open Reports] --> Input[Enter or select user content] Input --> Review[Review the current panel] Review --> Action[Run the main action] Action --> Save[Save, export, copy, or update] Save --> Confirm[Check confirmation or recent activity] Confirm --> Continue[Continue using project-manager]

#### How To Use This Area

Use Reports when you need to complete the related DawnDesk task without leaving the Project Manager workspace.
Start by reading the labels on the panel, because DawnDesk keeps the primary action near the current view.
Enter only the information needed for the current step, then save, export, copy, or review the result before moving on.
If a save dialog opens, choose a clear filename and keep the default extension unless your workflow requires a different one.
After completing the action, check the confirmation message or the recent activity log so you know the operation finished.
When the result affects another workspace, return to the Dashboard and open the next module from there.
If the panel appears empty, create the first record, import an existing file, or remove filters that may be hiding content.
For repeated work, use consistent naming so search, reports, and exports stay understandable later.

#### Practical Tips

Tip 1: keep the Reports result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 1: leaving Reports before checking whether the action produced the expected visible result.
Recovery 1: return to Reports, repeat the last action with a smaller change, and check the activity or status message.
Tip 2: keep the Reports result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 2: leaving Reports before checking whether the action produced the expected visible result.
Recovery 2: return to Reports, repeat the last action with a smaller change, and check the activity or status message.
Tip 3: keep the Reports result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 3: leaving Reports before checking whether the action produced the expected visible result.
Recovery 3: return to Reports, repeat the last action with a smaller change, and check the activity or status message.
Tip 4: keep the Reports result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 4: leaving Reports before checking whether the action produced the expected visible result.
Recovery 4: return to Reports, repeat the last action with a smaller change, and check the activity or status message.
Tip 5: keep the Reports result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 5: leaving Reports before checking whether the action produced the expected visible result.
Recovery 5: return to Reports, repeat the last action with a smaller change, and check the activity or status message.
Tip 6: keep the Reports result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 6: leaving Reports before checking whether the action produced the expected visible result.
Recovery 6: return to Reports, repeat the last action with a smaller change, and check the activity or status message.
Tip 7: keep the Reports result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 7: leaving Reports before checking whether the action produced the expected visible result.
Recovery 7: return to Reports, repeat the last action with a smaller change, and check the activity or status message.
Tip 8: keep the Reports result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 8: leaving Reports before checking whether the action produced the expected visible result.
Recovery 8: return to Reports, repeat the last action with a smaller change, and check the activity or status message.

#### Checklist

The correct Reports panel is open.
Required fields are filled in.
The main action button is enabled.
The result has been reviewed before leaving the view.
Any saved file uses the expected extension.
The recent activity log or status message confirms completion.

#### Troubleshooting

If Reports is blank, check whether this workspace needs a created record, selected project, selected file, or cloud sign-in.
If Reports does not save, choose a writable folder and keep the extension DawnDesk suggests.
If Reports shows old information, refresh the workspace or leave and reopen the module.
If Reports uses AI, confirm the provider is configured in Settings before retrying.
If Reports exports a file, open the file after saving to confirm the output is usable.

How to use Roadmap

Roadmap is part of Project Manager. This section explains how to approach the view, what to check first, how to complete the main action, and how to recover when something looks wrong.

flowchart TD Start[Open Roadmap] --> Input[Enter or select user content] Input --> Review[Review the current panel] Review --> Action[Run the main action] Action --> Save[Save, export, copy, or update] Save --> Confirm[Check confirmation or recent activity] Confirm --> Continue[Continue using project-manager]

#### How To Use This Area

Use Roadmap when you need to complete the related DawnDesk task without leaving the Project Manager workspace.
Start by reading the labels on the panel, because DawnDesk keeps the primary action near the current view.
Enter only the information needed for the current step, then save, export, copy, or review the result before moving on.
If a save dialog opens, choose a clear filename and keep the default extension unless your workflow requires a different one.
After completing the action, check the confirmation message or the recent activity log so you know the operation finished.
When the result affects another workspace, return to the Dashboard and open the next module from there.
If the panel appears empty, create the first record, import an existing file, or remove filters that may be hiding content.
For repeated work, use consistent naming so search, reports, and exports stay understandable later.

#### Practical Tips

Tip 1: keep the Roadmap result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 1: leaving Roadmap before checking whether the action produced the expected visible result.
Recovery 1: return to Roadmap, repeat the last action with a smaller change, and check the activity or status message.
Tip 2: keep the Roadmap result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 2: leaving Roadmap before checking whether the action produced the expected visible result.
Recovery 2: return to Roadmap, repeat the last action with a smaller change, and check the activity or status message.
Tip 3: keep the Roadmap result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 3: leaving Roadmap before checking whether the action produced the expected visible result.
Recovery 3: return to Roadmap, repeat the last action with a smaller change, and check the activity or status message.
Tip 4: keep the Roadmap result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 4: leaving Roadmap before checking whether the action produced the expected visible result.
Recovery 4: return to Roadmap, repeat the last action with a smaller change, and check the activity or status message.
Tip 5: keep the Roadmap result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 5: leaving Roadmap before checking whether the action produced the expected visible result.
Recovery 5: return to Roadmap, repeat the last action with a smaller change, and check the activity or status message.
Tip 6: keep the Roadmap result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 6: leaving Roadmap before checking whether the action produced the expected visible result.
Recovery 6: return to Roadmap, repeat the last action with a smaller change, and check the activity or status message.
Tip 7: keep the Roadmap result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 7: leaving Roadmap before checking whether the action produced the expected visible result.
Recovery 7: return to Roadmap, repeat the last action with a smaller change, and check the activity or status message.
Tip 8: keep the Roadmap result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 8: leaving Roadmap before checking whether the action produced the expected visible result.
Recovery 8: return to Roadmap, repeat the last action with a smaller change, and check the activity or status message.

#### Checklist

The correct Roadmap panel is open.
Required fields are filled in.
The main action button is enabled.
The result has been reviewed before leaving the view.
Any saved file uses the expected extension.
The recent activity log or status message confirms completion.

#### Troubleshooting

If Roadmap is blank, check whether this workspace needs a created record, selected project, selected file, or cloud sign-in.
If Roadmap does not save, choose a writable folder and keep the extension DawnDesk suggests.
If Roadmap shows old information, refresh the workspace or leave and reopen the module.
If Roadmap uses AI, confirm the provider is configured in Settings before retrying.
If Roadmap exports a file, open the file after saving to confirm the output is usable.

How to use Strategies

Strategies is part of Project Manager. This section explains how to approach the view, what to check first, how to complete the main action, and how to recover when something looks wrong.

flowchart TD Start[Open Strategies] --> Input[Enter or select user content] Input --> Review[Review the current panel] Review --> Action[Run the main action] Action --> Save[Save, export, copy, or update] Save --> Confirm[Check confirmation or recent activity] Confirm --> Continue[Continue using project-manager]

#### How To Use This Area

Use Strategies when you need to complete the related DawnDesk task without leaving the Project Manager workspace.
Start by reading the labels on the panel, because DawnDesk keeps the primary action near the current view.
Enter only the information needed for the current step, then save, export, copy, or review the result before moving on.
If a save dialog opens, choose a clear filename and keep the default extension unless your workflow requires a different one.
After completing the action, check the confirmation message or the recent activity log so you know the operation finished.
When the result affects another workspace, return to the Dashboard and open the next module from there.
If the panel appears empty, create the first record, import an existing file, or remove filters that may be hiding content.
For repeated work, use consistent naming so search, reports, and exports stay understandable later.

#### Practical Tips

Tip 1: keep the Strategies result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 1: leaving Strategies before checking whether the action produced the expected visible result.
Recovery 1: return to Strategies, repeat the last action with a smaller change, and check the activity or status message.
Tip 2: keep the Strategies result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 2: leaving Strategies before checking whether the action produced the expected visible result.
Recovery 2: return to Strategies, repeat the last action with a smaller change, and check the activity or status message.
Tip 3: keep the Strategies result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 3: leaving Strategies before checking whether the action produced the expected visible result.
Recovery 3: return to Strategies, repeat the last action with a smaller change, and check the activity or status message.
Tip 4: keep the Strategies result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 4: leaving Strategies before checking whether the action produced the expected visible result.
Recovery 4: return to Strategies, repeat the last action with a smaller change, and check the activity or status message.
Tip 5: keep the Strategies result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 5: leaving Strategies before checking whether the action produced the expected visible result.
Recovery 5: return to Strategies, repeat the last action with a smaller change, and check the activity or status message.
Tip 6: keep the Strategies result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 6: leaving Strategies before checking whether the action produced the expected visible result.
Recovery 6: return to Strategies, repeat the last action with a smaller change, and check the activity or status message.
Tip 7: keep the Strategies result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 7: leaving Strategies before checking whether the action produced the expected visible result.
Recovery 7: return to Strategies, repeat the last action with a smaller change, and check the activity or status message.
Tip 8: keep the Strategies result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 8: leaving Strategies before checking whether the action produced the expected visible result.
Recovery 8: return to Strategies, repeat the last action with a smaller change, and check the activity or status message.

#### Checklist

The correct Strategies panel is open.
Required fields are filled in.
The main action button is enabled.
The result has been reviewed before leaving the view.
Any saved file uses the expected extension.
The recent activity log or status message confirms completion.

#### Troubleshooting

If Strategies is blank, check whether this workspace needs a created record, selected project, selected file, or cloud sign-in.
If Strategies does not save, choose a writable folder and keep the extension DawnDesk suggests.
If Strategies shows old information, refresh the workspace or leave and reopen the module.
If Strategies uses AI, confirm the provider is configured in Settings before retrying.
If Strategies exports a file, open the file after saving to confirm the output is usable.

How to use Versions

Versions is part of Project Manager. This section explains how to approach the view, what to check first, how to complete the main action, and how to recover when something looks wrong.

flowchart TD Start[Open Versions] --> Input[Enter or select user content] Input --> Review[Review the current panel] Review --> Action[Run the main action] Action --> Save[Save, export, copy, or update] Save --> Confirm[Check confirmation or recent activity] Confirm --> Continue[Continue using project-manager]

#### How To Use This Area

Use Versions when you need to complete the related DawnDesk task without leaving the Project Manager workspace.
Start by reading the labels on the panel, because DawnDesk keeps the primary action near the current view.
Enter only the information needed for the current step, then save, export, copy, or review the result before moving on.
If a save dialog opens, choose a clear filename and keep the default extension unless your workflow requires a different one.
After completing the action, check the confirmation message or the recent activity log so you know the operation finished.
When the result affects another workspace, return to the Dashboard and open the next module from there.
If the panel appears empty, create the first record, import an existing file, or remove filters that may be hiding content.
For repeated work, use consistent naming so search, reports, and exports stay understandable later.

#### Practical Tips

Tip 1: keep the Versions result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 1: leaving Versions before checking whether the action produced the expected visible result.
Recovery 1: return to Versions, repeat the last action with a smaller change, and check the activity or status message.
Tip 2: keep the Versions result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 2: leaving Versions before checking whether the action produced the expected visible result.
Recovery 2: return to Versions, repeat the last action with a smaller change, and check the activity or status message.
Tip 3: keep the Versions result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 3: leaving Versions before checking whether the action produced the expected visible result.
Recovery 3: return to Versions, repeat the last action with a smaller change, and check the activity or status message.
Tip 4: keep the Versions result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 4: leaving Versions before checking whether the action produced the expected visible result.
Recovery 4: return to Versions, repeat the last action with a smaller change, and check the activity or status message.
Tip 5: keep the Versions result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 5: leaving Versions before checking whether the action produced the expected visible result.
Recovery 5: return to Versions, repeat the last action with a smaller change, and check the activity or status message.
Tip 6: keep the Versions result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 6: leaving Versions before checking whether the action produced the expected visible result.
Recovery 6: return to Versions, repeat the last action with a smaller change, and check the activity or status message.
Tip 7: keep the Versions result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 7: leaving Versions before checking whether the action produced the expected visible result.
Recovery 7: return to Versions, repeat the last action with a smaller change, and check the activity or status message.
Tip 8: keep the Versions result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 8: leaving Versions before checking whether the action produced the expected visible result.
Recovery 8: return to Versions, repeat the last action with a smaller change, and check the activity or status message.

#### Checklist

The correct Versions panel is open.
Required fields are filled in.
The main action button is enabled.
The result has been reviewed before leaving the view.
Any saved file uses the expected extension.
The recent activity log or status message confirms completion.

#### Troubleshooting

If Versions is blank, check whether this workspace needs a created record, selected project, selected file, or cloud sign-in.
If Versions does not save, choose a writable folder and keep the extension DawnDesk suggests.
If Versions shows old information, refresh the workspace or leave and reopen the module.
If Versions uses AI, confirm the provider is configured in Settings before retrying.
If Versions exports a file, open the file after saving to confirm the output is usable.

How to use Comments

Comments is part of Project Manager. This section explains how to approach the view, what to check first, how to complete the main action, and how to recover when something looks wrong.

flowchart TD Start[Open Comments] --> Input[Enter or select user content] Input --> Review[Review the current panel] Review --> Action[Run the main action] Action --> Save[Save, export, copy, or update] Save --> Confirm[Check confirmation or recent activity] Confirm --> Continue[Continue using project-manager]

#### How To Use This Area

Use Comments when you need to complete the related DawnDesk task without leaving the Project Manager workspace.
Start by reading the labels on the panel, because DawnDesk keeps the primary action near the current view.
Enter only the information needed for the current step, then save, export, copy, or review the result before moving on.
If a save dialog opens, choose a clear filename and keep the default extension unless your workflow requires a different one.
After completing the action, check the confirmation message or the recent activity log so you know the operation finished.
When the result affects another workspace, return to the Dashboard and open the next module from there.
If the panel appears empty, create the first record, import an existing file, or remove filters that may be hiding content.
For repeated work, use consistent naming so search, reports, and exports stay understandable later.

#### Practical Tips

Tip 1: keep the Comments result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 1: leaving Comments before checking whether the action produced the expected visible result.
Recovery 1: return to Comments, repeat the last action with a smaller change, and check the activity or status message.
Tip 2: keep the Comments result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 2: leaving Comments before checking whether the action produced the expected visible result.
Recovery 2: return to Comments, repeat the last action with a smaller change, and check the activity or status message.
Tip 3: keep the Comments result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 3: leaving Comments before checking whether the action produced the expected visible result.
Recovery 3: return to Comments, repeat the last action with a smaller change, and check the activity or status message.
Tip 4: keep the Comments result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 4: leaving Comments before checking whether the action produced the expected visible result.
Recovery 4: return to Comments, repeat the last action with a smaller change, and check the activity or status message.
Tip 5: keep the Comments result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 5: leaving Comments before checking whether the action produced the expected visible result.
Recovery 5: return to Comments, repeat the last action with a smaller change, and check the activity or status message.
Tip 6: keep the Comments result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 6: leaving Comments before checking whether the action produced the expected visible result.
Recovery 6: return to Comments, repeat the last action with a smaller change, and check the activity or status message.
Tip 7: keep the Comments result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 7: leaving Comments before checking whether the action produced the expected visible result.
Recovery 7: return to Comments, repeat the last action with a smaller change, and check the activity or status message.
Tip 8: keep the Comments result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 8: leaving Comments before checking whether the action produced the expected visible result.
Recovery 8: return to Comments, repeat the last action with a smaller change, and check the activity or status message.

#### Checklist

The correct Comments panel is open.
Required fields are filled in.
The main action button is enabled.
The result has been reviewed before leaving the view.
Any saved file uses the expected extension.
The recent activity log or status message confirms completion.

#### Troubleshooting

If Comments is blank, check whether this workspace needs a created record, selected project, selected file, or cloud sign-in.
If Comments does not save, choose a writable folder and keep the extension DawnDesk suggests.
If Comments shows old information, refresh the workspace or leave and reopen the module.
If Comments uses AI, confirm the provider is configured in Settings before retrying.
If Comments exports a file, open the file after saving to confirm the output is usable.

How to use Search and filters

Search and filters is part of Project Manager. This section explains how to approach the view, what to check first, how to complete the main action, and how to recover when something looks wrong.

Search and filters screenshot placeholder

flowchart TD Start[Open Search and filters] --> Input[Enter or select user content] Input --> Review[Review the current panel] Review --> Action[Run the main action] Action --> Save[Save, export, copy, or update] Save --> Confirm[Check confirmation or recent activity] Confirm --> Continue[Continue using project-manager]

#### How To Use This Area

Use Search and filters when you need to complete the related DawnDesk task without leaving the Project Manager workspace.
Start by reading the labels on the panel, because DawnDesk keeps the primary action near the current view.
Enter only the information needed for the current step, then save, export, copy, or review the result before moving on.
If a save dialog opens, choose a clear filename and keep the default extension unless your workflow requires a different one.
After completing the action, check the confirmation message or the recent activity log so you know the operation finished.
When the result affects another workspace, return to the Dashboard and open the next module from there.
If the panel appears empty, create the first record, import an existing file, or remove filters that may be hiding content.
For repeated work, use consistent naming so search, reports, and exports stay understandable later.

#### Practical Tips

Tip 1: keep the Search and filters result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 1: leaving Search and filters before checking whether the action produced the expected visible result.
Recovery 1: return to Search and filters, repeat the last action with a smaller change, and check the activity or status message.
Tip 2: keep the Search and filters result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 2: leaving Search and filters before checking whether the action produced the expected visible result.
Recovery 2: return to Search and filters, repeat the last action with a smaller change, and check the activity or status message.
Tip 3: keep the Search and filters result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 3: leaving Search and filters before checking whether the action produced the expected visible result.
Recovery 3: return to Search and filters, repeat the last action with a smaller change, and check the activity or status message.
Tip 4: keep the Search and filters result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 4: leaving Search and filters before checking whether the action produced the expected visible result.
Recovery 4: return to Search and filters, repeat the last action with a smaller change, and check the activity or status message.
Tip 5: keep the Search and filters result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 5: leaving Search and filters before checking whether the action produced the expected visible result.
Recovery 5: return to Search and filters, repeat the last action with a smaller change, and check the activity or status message.
Tip 6: keep the Search and filters result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 6: leaving Search and filters before checking whether the action produced the expected visible result.
Recovery 6: return to Search and filters, repeat the last action with a smaller change, and check the activity or status message.
Tip 7: keep the Search and filters result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 7: leaving Search and filters before checking whether the action produced the expected visible result.
Recovery 7: return to Search and filters, repeat the last action with a smaller change, and check the activity or status message.
Tip 8: keep the Search and filters result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 8: leaving Search and filters before checking whether the action produced the expected visible result.
Recovery 8: return to Search and filters, repeat the last action with a smaller change, and check the activity or status message.

#### Checklist

The correct Search and filters panel is open.
Required fields are filled in.
The main action button is enabled.
The result has been reviewed before leaving the view.
Any saved file uses the expected extension.
The recent activity log or status message confirms completion.

#### Troubleshooting

If Search and filters is blank, check whether this workspace needs a created record, selected project, selected file, or cloud sign-in.
If Search and filters does not save, choose a writable folder and keep the extension DawnDesk suggests.
If Search and filters shows old information, refresh the workspace or leave and reopen the module.
If Search and filters uses AI, confirm the provider is configured in Settings before retrying.
If Search and filters exports a file, open the file after saving to confirm the output is usable.

How to use Members

Members is part of Project Manager. This section explains how to approach the view, what to check first, how to complete the main action, and how to recover when something looks wrong.

flowchart TD Start[Open Members] --> Input[Enter or select user content] Input --> Review[Review the current panel] Review --> Action[Run the main action] Action --> Save[Save, export, copy, or update] Save --> Confirm[Check confirmation or recent activity] Confirm --> Continue[Continue using project-manager]

#### How To Use This Area

Use Members when you need to complete the related DawnDesk task without leaving the Project Manager workspace.
Start by reading the labels on the panel, because DawnDesk keeps the primary action near the current view.
Enter only the information needed for the current step, then save, export, copy, or review the result before moving on.
If a save dialog opens, choose a clear filename and keep the default extension unless your workflow requires a different one.
After completing the action, check the confirmation message or the recent activity log so you know the operation finished.
When the result affects another workspace, return to the Dashboard and open the next module from there.
If the panel appears empty, create the first record, import an existing file, or remove filters that may be hiding content.
For repeated work, use consistent naming so search, reports, and exports stay understandable later.

#### Practical Tips

Tip 1: keep the Members result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 1: leaving Members before checking whether the action produced the expected visible result.
Recovery 1: return to Members, repeat the last action with a smaller change, and check the activity or status message.
Tip 2: keep the Members result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 2: leaving Members before checking whether the action produced the expected visible result.
Recovery 2: return to Members, repeat the last action with a smaller change, and check the activity or status message.
Tip 3: keep the Members result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 3: leaving Members before checking whether the action produced the expected visible result.
Recovery 3: return to Members, repeat the last action with a smaller change, and check the activity or status message.
Tip 4: keep the Members result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 4: leaving Members before checking whether the action produced the expected visible result.
Recovery 4: return to Members, repeat the last action with a smaller change, and check the activity or status message.
Tip 5: keep the Members result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 5: leaving Members before checking whether the action produced the expected visible result.
Recovery 5: return to Members, repeat the last action with a smaller change, and check the activity or status message.
Tip 6: keep the Members result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 6: leaving Members before checking whether the action produced the expected visible result.
Recovery 6: return to Members, repeat the last action with a smaller change, and check the activity or status message.
Tip 7: keep the Members result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 7: leaving Members before checking whether the action produced the expected visible result.
Recovery 7: return to Members, repeat the last action with a smaller change, and check the activity or status message.
Tip 8: keep the Members result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 8: leaving Members before checking whether the action produced the expected visible result.
Recovery 8: return to Members, repeat the last action with a smaller change, and check the activity or status message.

#### Checklist

The correct Members panel is open.
Required fields are filled in.
The main action button is enabled.
The result has been reviewed before leaving the view.
Any saved file uses the expected extension.
The recent activity log or status message confirms completion.

#### Troubleshooting

If Members is blank, check whether this workspace needs a created record, selected project, selected file, or cloud sign-in.
If Members does not save, choose a writable folder and keep the extension DawnDesk suggests.
If Members shows old information, refresh the workspace or leave and reopen the module.
If Members uses AI, confirm the provider is configured in Settings before retrying.
If Members exports a file, open the file after saving to confirm the output is usable.

How to use Project settings

Project settings is part of Project Manager. This section explains how to approach the view, what to check first, how to complete the main action, and how to recover when something looks wrong.

flowchart TD Start[Open Project settings] --> Input[Enter or select user content] Input --> Review[Review the current panel] Review --> Action[Run the main action] Action --> Save[Save, export, copy, or update] Save --> Confirm[Check confirmation or recent activity] Confirm --> Continue[Continue using project-manager]

#### How To Use This Area

Use Project settings when you need to complete the related DawnDesk task without leaving the Project Manager workspace.
Start by reading the labels on the panel, because DawnDesk keeps the primary action near the current view.
Enter only the information needed for the current step, then save, export, copy, or review the result before moving on.
If a save dialog opens, choose a clear filename and keep the default extension unless your workflow requires a different one.
After completing the action, check the confirmation message or the recent activity log so you know the operation finished.
When the result affects another workspace, return to the Dashboard and open the next module from there.
If the panel appears empty, create the first record, import an existing file, or remove filters that may be hiding content.
For repeated work, use consistent naming so search, reports, and exports stay understandable later.

#### Practical Tips

Tip 1: keep the Project settings result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 1: leaving Project settings before checking whether the action produced the expected visible result.
Recovery 1: return to Project settings, repeat the last action with a smaller change, and check the activity or status message.
Tip 2: keep the Project settings result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 2: leaving Project settings before checking whether the action produced the expected visible result.
Recovery 2: return to Project settings, repeat the last action with a smaller change, and check the activity or status message.
Tip 3: keep the Project settings result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 3: leaving Project settings before checking whether the action produced the expected visible result.
Recovery 3: return to Project settings, repeat the last action with a smaller change, and check the activity or status message.
Tip 4: keep the Project settings result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 4: leaving Project settings before checking whether the action produced the expected visible result.
Recovery 4: return to Project settings, repeat the last action with a smaller change, and check the activity or status message.
Tip 5: keep the Project settings result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 5: leaving Project settings before checking whether the action produced the expected visible result.
Recovery 5: return to Project settings, repeat the last action with a smaller change, and check the activity or status message.
Tip 6: keep the Project settings result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 6: leaving Project settings before checking whether the action produced the expected visible result.
Recovery 6: return to Project settings, repeat the last action with a smaller change, and check the activity or status message.
Tip 7: keep the Project settings result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 7: leaving Project settings before checking whether the action produced the expected visible result.
Recovery 7: return to Project settings, repeat the last action with a smaller change, and check the activity or status message.
Tip 8: keep the Project settings result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 8: leaving Project settings before checking whether the action produced the expected visible result.
Recovery 8: return to Project settings, repeat the last action with a smaller change, and check the activity or status message.

#### Checklist

The correct Project settings panel is open.
Required fields are filled in.
The main action button is enabled.
The result has been reviewed before leaving the view.
Any saved file uses the expected extension.
The recent activity log or status message confirms completion.

#### Troubleshooting

If Project settings is blank, check whether this workspace needs a created record, selected project, selected file, or cloud sign-in.
If Project settings does not save, choose a writable folder and keep the extension DawnDesk suggests.
If Project settings shows old information, refresh the workspace or leave and reopen the module.
If Project settings uses AI, confirm the provider is configured in Settings before retrying.
If Project settings exports a file, open the file after saving to confirm the output is usable.

Practical Reference

Open in Project list

Use case: Open content when working inside Project list.

User action: Go to Project list, complete the visible fields, and use the nearest open control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Project list result.

Tip: Use descriptive names and check status messages so Project list work remains easy to find later.

Create in Project dashboard

Use case: Create content when working inside Project dashboard.

User action: Go to Project dashboard, complete the visible fields, and use the nearest create control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Project dashboard result.

Tip: Use descriptive names and check status messages so Project dashboard work remains easy to find later.

Edit in Backlog

Use case: Edit content when working inside Backlog.

User action: Go to Backlog, complete the visible fields, and use the nearest edit control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Backlog result.

Tip: Use descriptive names and check status messages so Backlog work remains easy to find later.

Save in Board

Use case: Save content when working inside Board.

User action: Go to Board, complete the visible fields, and use the nearest save control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Board result.

Tip: Use descriptive names and check status messages so Board work remains easy to find later.

Export in Reports

Use case: Export content when working inside Reports.

User action: Go to Reports, complete the visible fields, and use the nearest export control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Reports result.

Tip: Use descriptive names and check status messages so Reports work remains easy to find later.

Search in Roadmap

Use case: Search content when working inside Roadmap.

User action: Go to Roadmap, complete the visible fields, and use the nearest search control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Roadmap result.

Tip: Use descriptive names and check status messages so Roadmap work remains easy to find later.

Filter in Strategies

Use case: Filter content when working inside Strategies.

User action: Go to Strategies, complete the visible fields, and use the nearest filter control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Strategies result.

Tip: Use descriptive names and check status messages so Strategies work remains easy to find later.

Review in Versions

Use case: Review content when working inside Versions.

User action: Go to Versions, complete the visible fields, and use the nearest review control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Versions result.

Tip: Use descriptive names and check status messages so Versions work remains easy to find later.

Copy in Comments

Use case: Copy content when working inside Comments.

User action: Go to Comments, complete the visible fields, and use the nearest copy control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Comments result.

Tip: Use descriptive names and check status messages so Comments work remains easy to find later.

Import in Search and filters

Use case: Import content when working inside Search and filters.

User action: Go to Search and filters, complete the visible fields, and use the nearest import control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Search and filters result.

Tip: Use descriptive names and check status messages so Search and filters work remains easy to find later.

Open in Members

Use case: Open content when working inside Members.

User action: Go to Members, complete the visible fields, and use the nearest open control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Members result.

Tip: Use descriptive names and check status messages so Members work remains easy to find later.

Create in Project settings

Use case: Create content when working inside Project settings.

User action: Go to Project settings, complete the visible fields, and use the nearest create control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Project settings result.

Tip: Use descriptive names and check status messages so Project settings work remains easy to find later.

Edit in Project list

Use case: Edit content when working inside Project list.

User action: Go to Project list, complete the visible fields, and use the nearest edit control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Project list result.

Tip: Use descriptive names and check status messages so Project list work remains easy to find later.

Save in Project dashboard

Use case: Save content when working inside Project dashboard.

User action: Go to Project dashboard, complete the visible fields, and use the nearest save control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Project dashboard result.

Tip: Use descriptive names and check status messages so Project dashboard work remains easy to find later.

Export in Backlog

Use case: Export content when working inside Backlog.

User action: Go to Backlog, complete the visible fields, and use the nearest export control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Backlog result.

Tip: Use descriptive names and check status messages so Backlog work remains easy to find later.

Search in Board

Use case: Search content when working inside Board.

User action: Go to Board, complete the visible fields, and use the nearest search control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Board result.

Tip: Use descriptive names and check status messages so Board work remains easy to find later.

Filter in Reports

Use case: Filter content when working inside Reports.

User action: Go to Reports, complete the visible fields, and use the nearest filter control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Reports result.

Tip: Use descriptive names and check status messages so Reports work remains easy to find later.

Review in Roadmap

Use case: Review content when working inside Roadmap.

User action: Go to Roadmap, complete the visible fields, and use the nearest review control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Roadmap result.

Tip: Use descriptive names and check status messages so Roadmap work remains easy to find later.

Copy in Strategies

Use case: Copy content when working inside Strategies.

User action: Go to Strategies, complete the visible fields, and use the nearest copy control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Strategies result.

Tip: Use descriptive names and check status messages so Strategies work remains easy to find later.

Import in Versions

Use case: Import content when working inside Versions.

User action: Go to Versions, complete the visible fields, and use the nearest import control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Versions result.

Tip: Use descriptive names and check status messages so Versions work remains easy to find later.

Open in Comments

Use case: Open content when working inside Comments.

User action: Go to Comments, complete the visible fields, and use the nearest open control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Comments result.

Tip: Use descriptive names and check status messages so Comments work remains easy to find later.

Create in Search and filters

Use case: Create content when working inside Search and filters.

User action: Go to Search and filters, complete the visible fields, and use the nearest create control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Search and filters result.

Tip: Use descriptive names and check status messages so Search and filters work remains easy to find later.

Edit in Members

Use case: Edit content when working inside Members.

User action: Go to Members, complete the visible fields, and use the nearest edit control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Members result.

Tip: Use descriptive names and check status messages so Members work remains easy to find later.

Save in Project settings

Use case: Save content when working inside Project settings.

User action: Go to Project settings, complete the visible fields, and use the nearest save control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Project settings result.

Tip: Use descriptive names and check status messages so Project settings work remains easy to find later.

Export in Project list

Use case: Export content when working inside Project list.

User action: Go to Project list, complete the visible fields, and use the nearest export control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Project list result.

Tip: Use descriptive names and check status messages so Project list work remains easy to find later.

Search in Project dashboard

Use case: Search content when working inside Project dashboard.

User action: Go to Project dashboard, complete the visible fields, and use the nearest search control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Project dashboard result.

Tip: Use descriptive names and check status messages so Project dashboard work remains easy to find later.

Filter in Backlog

Use case: Filter content when working inside Backlog.

User action: Go to Backlog, complete the visible fields, and use the nearest filter control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Backlog result.

Tip: Use descriptive names and check status messages so Backlog work remains easy to find later.

Review in Board

Use case: Review content when working inside Board.

User action: Go to Board, complete the visible fields, and use the nearest review control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Board result.

Tip: Use descriptive names and check status messages so Board work remains easy to find later.

Copy in Reports

Use case: Copy content when working inside Reports.

User action: Go to Reports, complete the visible fields, and use the nearest copy control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Reports result.

Tip: Use descriptive names and check status messages so Reports work remains easy to find later.

Import in Roadmap

Use case: Import content when working inside Roadmap.

User action: Go to Roadmap, complete the visible fields, and use the nearest import control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Roadmap result.

Tip: Use descriptive names and check status messages so Roadmap work remains easy to find later.

User Safety Notes

Save important work before switching modules.
Use clear filenames for exports so files are easy to recognize outside DawnDesk.
Check confirmation messages after save, import, export, delete, or AI actions.
Do not paste private API keys or sensitive customer data into fields that do not need them.
When cloud workspaces are enabled, confirm sign-in before assuming data is missing.

Download DawnDesk

Project Manager Documentation

Overview

How to use this guide

Image Placeholders

Quick Start

Core Workflows

Create a project workspace

Import a project export

Plan a backlog

Run a sprint

Use reports

Write strategy notes

Workspace Areas

How to use Project list

How to use Project dashboard

How to use Backlog

How to use Board

How to use Reports

How to use Roadmap

How to use Strategies

How to use Versions

How to use Comments

How to use Search and filters

How to use Members

How to use Project settings

Practical Reference

Open in Project list

Create in Project dashboard

Edit in Backlog

Save in Board

Export in Reports

Search in Roadmap

Filter in Strategies

Review in Versions

Copy in Comments

Import in Search and filters

Open in Members

Create in Project settings

Edit in Project list

Save in Project dashboard

Export in Backlog

Search in Board

Filter in Reports

Review in Roadmap

Copy in Strategies

Import in Versions

Open in Comments

Create in Search and filters

Edit in Members

Save in Project settings

Export in Project list

Search in Project dashboard

Filter in Backlog

Review in Board

Copy in Reports

Import in Roadmap

User Safety Notes