Overview

Notes is the local knowledge workspace in DawnDesk. Use it for meeting notes, research, daily notes, checklists, templates, task extraction, linked note relationships, version history, and searchable long-term reference material.

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 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 notes]

Image Placeholders

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

Quick Start

Open Notes from the Dashboard.
Choose the create note action.
Enter a clear title.
Write the note body using headings, lists, checkboxes, tables, code blocks, or plain text.
Save or let the workspace update the note state.

Core Workflows

Create a note

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

flowchart TD Start[Open Create a note] --> 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 notes]

#### Steps

Open Notes from the Dashboard.
Choose the create note action.
Enter a clear title.
Write the note body using headings, lists, checkboxes, tables, code blocks, or plain text.
Save or let the workspace update the note state.

#### What To Check

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

- 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 note.

- 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 note.

- 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 note.

- 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 note.

- 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.

Organize with notebooks

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

flowchart TD Start[Open Organize with notebooks] --> 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 notes]

#### Steps

Open the notebook area.
Create a notebook for a project, topic, client, or personal area.
Move related notes into that notebook.
Use notebook names that describe the kind of information stored there.
Review notebooks periodically to prevent clutter.

#### What To Check

Step 1: After this step, DawnDesk should show progress toward organize with notebooks.

- 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 organize with notebooks.

- 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 organize with notebooks.

- 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 organize with notebooks.

- 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 organize with notebooks.

- 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 tags

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

flowchart TD Start[Open Use tags] --> 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 notes]

#### Steps

Open or create a note.
Add tags for cross-cutting labels such as urgent, meeting, research, finance, or idea.
Use tag filtering to find notes across notebooks.
Remove tags when the context no longer applies.
Keep tag names short and reusable.

#### What To Check

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

- 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 tags.

- 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 tags.

- 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 tags.

- 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 use tags.

- 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.

Create daily notes

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

flowchart TD Start[Open Create daily 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 notes]

#### Steps

Open Daily Notes.
Choose the current date or a target date.
Create the daily note if none exists.
Record tasks, decisions, reminders, and reflections.
Return later from the calendar-style daily note view.

#### What To Check

Step 1: After this step, DawnDesk should show progress toward create daily 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 create daily 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 create daily 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 create daily 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 create daily 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.

Work with backlinks

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

flowchart TD Start[Open Work with backlinks] --> 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 notes]

#### Steps

Link one note to another when the context matters.
Open the backlinks view for a note.
Review notes that reference the current note.
Use backlinks to discover related knowledge.
Clean up broken or stale references when reorganizing.

#### What To Check

Step 1: After this step, DawnDesk should show progress toward work with backlinks.

- 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 work with backlinks.

- 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 work with backlinks.

- 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 work with backlinks.

- 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 work with backlinks.

- 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 All notes

All notes is part of Notes. 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 All 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 notes]

#### How To Use This Area

Use All notes when you need to complete the related DawnDesk task without leaving the Notes 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 All notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 1: leaving All notes before checking whether the action produced the expected visible result.
Recovery 1: return to All notes, repeat the last action with a smaller change, and check the activity or status message.
Tip 2: keep the All notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 2: leaving All notes before checking whether the action produced the expected visible result.
Recovery 2: return to All notes, repeat the last action with a smaller change, and check the activity or status message.
Tip 3: keep the All notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 3: leaving All notes before checking whether the action produced the expected visible result.
Recovery 3: return to All notes, repeat the last action with a smaller change, and check the activity or status message.
Tip 4: keep the All notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 4: leaving All notes before checking whether the action produced the expected visible result.
Recovery 4: return to All notes, repeat the last action with a smaller change, and check the activity or status message.
Tip 5: keep the All notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 5: leaving All notes before checking whether the action produced the expected visible result.
Recovery 5: return to All notes, repeat the last action with a smaller change, and check the activity or status message.
Tip 6: keep the All notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 6: leaving All notes before checking whether the action produced the expected visible result.
Recovery 6: return to All notes, repeat the last action with a smaller change, and check the activity or status message.
Tip 7: keep the All notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 7: leaving All notes before checking whether the action produced the expected visible result.
Recovery 7: return to All notes, repeat the last action with a smaller change, and check the activity or status message.
Tip 8: keep the All notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 8: leaving All notes before checking whether the action produced the expected visible result.
Recovery 8: return to All notes, repeat the last action with a smaller change, and check the activity or status message.

#### Checklist

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

How to use Notebook tree

Notebook tree is part of Notes. 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 Notebook tree] --> 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 notes]

#### How To Use This Area

Use Notebook tree when you need to complete the related DawnDesk task without leaving the Notes 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 Notebook tree result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 1: leaving Notebook tree before checking whether the action produced the expected visible result.
Recovery 1: return to Notebook tree, repeat the last action with a smaller change, and check the activity or status message.
Tip 2: keep the Notebook tree result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 2: leaving Notebook tree before checking whether the action produced the expected visible result.
Recovery 2: return to Notebook tree, repeat the last action with a smaller change, and check the activity or status message.
Tip 3: keep the Notebook tree result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 3: leaving Notebook tree before checking whether the action produced the expected visible result.
Recovery 3: return to Notebook tree, repeat the last action with a smaller change, and check the activity or status message.
Tip 4: keep the Notebook tree result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 4: leaving Notebook tree before checking whether the action produced the expected visible result.
Recovery 4: return to Notebook tree, repeat the last action with a smaller change, and check the activity or status message.
Tip 5: keep the Notebook tree result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 5: leaving Notebook tree before checking whether the action produced the expected visible result.
Recovery 5: return to Notebook tree, repeat the last action with a smaller change, and check the activity or status message.
Tip 6: keep the Notebook tree result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 6: leaving Notebook tree before checking whether the action produced the expected visible result.
Recovery 6: return to Notebook tree, repeat the last action with a smaller change, and check the activity or status message.
Tip 7: keep the Notebook tree result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 7: leaving Notebook tree before checking whether the action produced the expected visible result.
Recovery 7: return to Notebook tree, repeat the last action with a smaller change, and check the activity or status message.
Tip 8: keep the Notebook tree result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 8: leaving Notebook tree before checking whether the action produced the expected visible result.
Recovery 8: return to Notebook tree, repeat the last action with a smaller change, and check the activity or status message.

#### Checklist

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

How to use Tags

Tags is part of Notes. 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 Tags] --> 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 notes]

#### How To Use This Area

Use Tags when you need to complete the related DawnDesk task without leaving the Notes 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 Tags result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 1: leaving Tags before checking whether the action produced the expected visible result.
Recovery 1: return to Tags, repeat the last action with a smaller change, and check the activity or status message.
Tip 2: keep the Tags result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 2: leaving Tags before checking whether the action produced the expected visible result.
Recovery 2: return to Tags, repeat the last action with a smaller change, and check the activity or status message.
Tip 3: keep the Tags result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 3: leaving Tags before checking whether the action produced the expected visible result.
Recovery 3: return to Tags, repeat the last action with a smaller change, and check the activity or status message.
Tip 4: keep the Tags result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 4: leaving Tags before checking whether the action produced the expected visible result.
Recovery 4: return to Tags, repeat the last action with a smaller change, and check the activity or status message.
Tip 5: keep the Tags result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 5: leaving Tags before checking whether the action produced the expected visible result.
Recovery 5: return to Tags, repeat the last action with a smaller change, and check the activity or status message.
Tip 6: keep the Tags result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 6: leaving Tags before checking whether the action produced the expected visible result.
Recovery 6: return to Tags, repeat the last action with a smaller change, and check the activity or status message.
Tip 7: keep the Tags result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 7: leaving Tags before checking whether the action produced the expected visible result.
Recovery 7: return to Tags, repeat the last action with a smaller change, and check the activity or status message.
Tip 8: keep the Tags result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 8: leaving Tags before checking whether the action produced the expected visible result.
Recovery 8: return to Tags, repeat the last action with a smaller change, and check the activity or status message.

#### Checklist

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

How to use Editor

Editor is part of Notes. 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 Editor] --> 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 notes]

#### How To Use This Area

Use Editor when you need to complete the related DawnDesk task without leaving the Notes 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 Editor result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 1: leaving Editor before checking whether the action produced the expected visible result.
Recovery 1: return to Editor, repeat the last action with a smaller change, and check the activity or status message.
Tip 2: keep the Editor result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 2: leaving Editor before checking whether the action produced the expected visible result.
Recovery 2: return to Editor, repeat the last action with a smaller change, and check the activity or status message.
Tip 3: keep the Editor result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 3: leaving Editor before checking whether the action produced the expected visible result.
Recovery 3: return to Editor, repeat the last action with a smaller change, and check the activity or status message.
Tip 4: keep the Editor result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 4: leaving Editor before checking whether the action produced the expected visible result.
Recovery 4: return to Editor, repeat the last action with a smaller change, and check the activity or status message.
Tip 5: keep the Editor result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 5: leaving Editor before checking whether the action produced the expected visible result.
Recovery 5: return to Editor, repeat the last action with a smaller change, and check the activity or status message.
Tip 6: keep the Editor result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 6: leaving Editor before checking whether the action produced the expected visible result.
Recovery 6: return to Editor, repeat the last action with a smaller change, and check the activity or status message.
Tip 7: keep the Editor result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 7: leaving Editor before checking whether the action produced the expected visible result.
Recovery 7: return to Editor, repeat the last action with a smaller change, and check the activity or status message.
Tip 8: keep the Editor result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 8: leaving Editor before checking whether the action produced the expected visible result.
Recovery 8: return to Editor, repeat the last action with a smaller change, and check the activity or status message.

#### Checklist

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

How to use Tasks view

Tasks view is part of Notes. 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 Tasks view] --> 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 notes]

#### How To Use This Area

Use Tasks view when you need to complete the related DawnDesk task without leaving the Notes 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 Tasks view result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 1: leaving Tasks view before checking whether the action produced the expected visible result.
Recovery 1: return to Tasks view, repeat the last action with a smaller change, and check the activity or status message.
Tip 2: keep the Tasks view result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 2: leaving Tasks view before checking whether the action produced the expected visible result.
Recovery 2: return to Tasks view, repeat the last action with a smaller change, and check the activity or status message.
Tip 3: keep the Tasks view result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 3: leaving Tasks view before checking whether the action produced the expected visible result.
Recovery 3: return to Tasks view, repeat the last action with a smaller change, and check the activity or status message.
Tip 4: keep the Tasks view result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 4: leaving Tasks view before checking whether the action produced the expected visible result.
Recovery 4: return to Tasks view, repeat the last action with a smaller change, and check the activity or status message.
Tip 5: keep the Tasks view result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 5: leaving Tasks view before checking whether the action produced the expected visible result.
Recovery 5: return to Tasks view, repeat the last action with a smaller change, and check the activity or status message.
Tip 6: keep the Tasks view result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 6: leaving Tasks view before checking whether the action produced the expected visible result.
Recovery 6: return to Tasks view, repeat the last action with a smaller change, and check the activity or status message.
Tip 7: keep the Tasks view result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 7: leaving Tasks view before checking whether the action produced the expected visible result.
Recovery 7: return to Tasks view, repeat the last action with a smaller change, and check the activity or status message.
Tip 8: keep the Tasks view result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 8: leaving Tasks view before checking whether the action produced the expected visible result.
Recovery 8: return to Tasks view, repeat the last action with a smaller change, and check the activity or status message.

#### Checklist

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

How to use Daily notes

Daily notes is part of Notes. 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 Daily 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 notes]

#### How To Use This Area

Use Daily notes when you need to complete the related DawnDesk task without leaving the Notes 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 Daily notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 1: leaving Daily notes before checking whether the action produced the expected visible result.
Recovery 1: return to Daily notes, repeat the last action with a smaller change, and check the activity or status message.
Tip 2: keep the Daily notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 2: leaving Daily notes before checking whether the action produced the expected visible result.
Recovery 2: return to Daily notes, repeat the last action with a smaller change, and check the activity or status message.
Tip 3: keep the Daily notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 3: leaving Daily notes before checking whether the action produced the expected visible result.
Recovery 3: return to Daily notes, repeat the last action with a smaller change, and check the activity or status message.
Tip 4: keep the Daily notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 4: leaving Daily notes before checking whether the action produced the expected visible result.
Recovery 4: return to Daily notes, repeat the last action with a smaller change, and check the activity or status message.
Tip 5: keep the Daily notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 5: leaving Daily notes before checking whether the action produced the expected visible result.
Recovery 5: return to Daily notes, repeat the last action with a smaller change, and check the activity or status message.
Tip 6: keep the Daily notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 6: leaving Daily notes before checking whether the action produced the expected visible result.
Recovery 6: return to Daily notes, repeat the last action with a smaller change, and check the activity or status message.
Tip 7: keep the Daily notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 7: leaving Daily notes before checking whether the action produced the expected visible result.
Recovery 7: return to Daily notes, repeat the last action with a smaller change, and check the activity or status message.
Tip 8: keep the Daily notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 8: leaving Daily notes before checking whether the action produced the expected visible result.
Recovery 8: return to Daily notes, repeat the last action with a smaller change, and check the activity or status message.

#### Checklist

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

How to use Templates

Templates is part of Notes. 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 Templates] --> 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 notes]

#### How To Use This Area

Use Templates when you need to complete the related DawnDesk task without leaving the Notes 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 Templates result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 1: leaving Templates before checking whether the action produced the expected visible result.
Recovery 1: return to Templates, repeat the last action with a smaller change, and check the activity or status message.
Tip 2: keep the Templates result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 2: leaving Templates before checking whether the action produced the expected visible result.
Recovery 2: return to Templates, repeat the last action with a smaller change, and check the activity or status message.
Tip 3: keep the Templates result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 3: leaving Templates before checking whether the action produced the expected visible result.
Recovery 3: return to Templates, repeat the last action with a smaller change, and check the activity or status message.
Tip 4: keep the Templates result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 4: leaving Templates before checking whether the action produced the expected visible result.
Recovery 4: return to Templates, repeat the last action with a smaller change, and check the activity or status message.
Tip 5: keep the Templates result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 5: leaving Templates before checking whether the action produced the expected visible result.
Recovery 5: return to Templates, repeat the last action with a smaller change, and check the activity or status message.
Tip 6: keep the Templates result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 6: leaving Templates before checking whether the action produced the expected visible result.
Recovery 6: return to Templates, repeat the last action with a smaller change, and check the activity or status message.
Tip 7: keep the Templates result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 7: leaving Templates before checking whether the action produced the expected visible result.
Recovery 7: return to Templates, repeat the last action with a smaller change, and check the activity or status message.
Tip 8: keep the Templates result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 8: leaving Templates before checking whether the action produced the expected visible result.
Recovery 8: return to Templates, repeat the last action with a smaller change, and check the activity or status message.

#### Checklist

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

How to use Backlinks

Backlinks is part of Notes. 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 Backlinks] --> 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 notes]

#### How To Use This Area

Use Backlinks when you need to complete the related DawnDesk task without leaving the Notes 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 Backlinks result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 1: leaving Backlinks before checking whether the action produced the expected visible result.
Recovery 1: return to Backlinks, repeat the last action with a smaller change, and check the activity or status message.
Tip 2: keep the Backlinks result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 2: leaving Backlinks before checking whether the action produced the expected visible result.
Recovery 2: return to Backlinks, repeat the last action with a smaller change, and check the activity or status message.
Tip 3: keep the Backlinks result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 3: leaving Backlinks before checking whether the action produced the expected visible result.
Recovery 3: return to Backlinks, repeat the last action with a smaller change, and check the activity or status message.
Tip 4: keep the Backlinks result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 4: leaving Backlinks before checking whether the action produced the expected visible result.
Recovery 4: return to Backlinks, repeat the last action with a smaller change, and check the activity or status message.
Tip 5: keep the Backlinks result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 5: leaving Backlinks before checking whether the action produced the expected visible result.
Recovery 5: return to Backlinks, repeat the last action with a smaller change, and check the activity or status message.
Tip 6: keep the Backlinks result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 6: leaving Backlinks before checking whether the action produced the expected visible result.
Recovery 6: return to Backlinks, repeat the last action with a smaller change, and check the activity or status message.
Tip 7: keep the Backlinks result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 7: leaving Backlinks before checking whether the action produced the expected visible result.
Recovery 7: return to Backlinks, repeat the last action with a smaller change, and check the activity or status message.
Tip 8: keep the Backlinks result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 8: leaving Backlinks before checking whether the action produced the expected visible result.
Recovery 8: return to Backlinks, repeat the last action with a smaller change, and check the activity or status message.

#### Checklist

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

How to use Graph view

Graph view is part of Notes. 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 Graph view] --> 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 notes]

#### How To Use This Area

Use Graph view when you need to complete the related DawnDesk task without leaving the Notes 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 Graph view result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 1: leaving Graph view before checking whether the action produced the expected visible result.
Recovery 1: return to Graph view, repeat the last action with a smaller change, and check the activity or status message.
Tip 2: keep the Graph view result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 2: leaving Graph view before checking whether the action produced the expected visible result.
Recovery 2: return to Graph view, repeat the last action with a smaller change, and check the activity or status message.
Tip 3: keep the Graph view result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 3: leaving Graph view before checking whether the action produced the expected visible result.
Recovery 3: return to Graph view, repeat the last action with a smaller change, and check the activity or status message.
Tip 4: keep the Graph view result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 4: leaving Graph view before checking whether the action produced the expected visible result.
Recovery 4: return to Graph view, repeat the last action with a smaller change, and check the activity or status message.
Tip 5: keep the Graph view result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 5: leaving Graph view before checking whether the action produced the expected visible result.
Recovery 5: return to Graph view, repeat the last action with a smaller change, and check the activity or status message.
Tip 6: keep the Graph view result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 6: leaving Graph view before checking whether the action produced the expected visible result.
Recovery 6: return to Graph view, repeat the last action with a smaller change, and check the activity or status message.
Tip 7: keep the Graph view result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 7: leaving Graph view before checking whether the action produced the expected visible result.
Recovery 7: return to Graph view, repeat the last action with a smaller change, and check the activity or status message.
Tip 8: keep the Graph view result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 8: leaving Graph view before checking whether the action produced the expected visible result.
Recovery 8: return to Graph view, repeat the last action with a smaller change, and check the activity or status message.

#### Checklist

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

How to use Search

Search is part of Notes. 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 Search] --> 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 notes]

#### How To Use This Area

Use Search when you need to complete the related DawnDesk task without leaving the Notes 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 result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 1: leaving Search before checking whether the action produced the expected visible result.
Recovery 1: return to Search, repeat the last action with a smaller change, and check the activity or status message.
Tip 2: keep the Search result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 2: leaving Search before checking whether the action produced the expected visible result.
Recovery 2: return to Search, repeat the last action with a smaller change, and check the activity or status message.
Tip 3: keep the Search result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 3: leaving Search before checking whether the action produced the expected visible result.
Recovery 3: return to Search, repeat the last action with a smaller change, and check the activity or status message.
Tip 4: keep the Search result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 4: leaving Search before checking whether the action produced the expected visible result.
Recovery 4: return to Search, repeat the last action with a smaller change, and check the activity or status message.
Tip 5: keep the Search result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 5: leaving Search before checking whether the action produced the expected visible result.
Recovery 5: return to Search, repeat the last action with a smaller change, and check the activity or status message.
Tip 6: keep the Search result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 6: leaving Search before checking whether the action produced the expected visible result.
Recovery 6: return to Search, repeat the last action with a smaller change, and check the activity or status message.
Tip 7: keep the Search result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 7: leaving Search before checking whether the action produced the expected visible result.
Recovery 7: return to Search, repeat the last action with a smaller change, and check the activity or status message.
Tip 8: keep the Search result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 8: leaving Search before checking whether the action produced the expected visible result.
Recovery 8: return to Search, repeat the last action with a smaller change, and check the activity or status message.

#### Checklist

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

How to use Archive and deleted notes

Archive and deleted notes is part of Notes. 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.

Archive and deleted notes screenshot placeholder

flowchart TD Start[Open Archive and deleted 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 notes]

#### How To Use This Area

Use Archive and deleted notes when you need to complete the related DawnDesk task without leaving the Notes 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 Archive and deleted notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 1: leaving Archive and deleted notes before checking whether the action produced the expected visible result.
Recovery 1: return to Archive and deleted notes, repeat the last action with a smaller change, and check the activity or status message.
Tip 2: keep the Archive and deleted notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 2: leaving Archive and deleted notes before checking whether the action produced the expected visible result.
Recovery 2: return to Archive and deleted notes, repeat the last action with a smaller change, and check the activity or status message.
Tip 3: keep the Archive and deleted notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 3: leaving Archive and deleted notes before checking whether the action produced the expected visible result.
Recovery 3: return to Archive and deleted notes, repeat the last action with a smaller change, and check the activity or status message.
Tip 4: keep the Archive and deleted notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 4: leaving Archive and deleted notes before checking whether the action produced the expected visible result.
Recovery 4: return to Archive and deleted notes, repeat the last action with a smaller change, and check the activity or status message.
Tip 5: keep the Archive and deleted notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 5: leaving Archive and deleted notes before checking whether the action produced the expected visible result.
Recovery 5: return to Archive and deleted notes, repeat the last action with a smaller change, and check the activity or status message.
Tip 6: keep the Archive and deleted notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 6: leaving Archive and deleted notes before checking whether the action produced the expected visible result.
Recovery 6: return to Archive and deleted notes, repeat the last action with a smaller change, and check the activity or status message.
Tip 7: keep the Archive and deleted notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 7: leaving Archive and deleted notes before checking whether the action produced the expected visible result.
Recovery 7: return to Archive and deleted notes, repeat the last action with a smaller change, and check the activity or status message.
Tip 8: keep the Archive and deleted notes result easy to identify by using DawnDesk names, dates, project names, or client names where appropriate.
Common mistake 8: leaving Archive and deleted notes before checking whether the action produced the expected visible result.
Recovery 8: return to Archive and deleted notes, repeat the last action with a smaller change, and check the activity or status message.

#### Checklist

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

Practical Reference

Open in All notes

Use case: Open content when working inside All notes.

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

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

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

Create in Notebook tree

Use case: Create content when working inside Notebook tree.

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

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

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

Edit in Tags

Use case: Edit content when working inside Tags.

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

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

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

Save in Editor

Use case: Save content when working inside Editor.

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

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

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

Export in Tasks view

Use case: Export content when working inside Tasks view.

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

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

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

Search in Daily notes

Use case: Search content when working inside Daily notes.

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

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

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

Filter in Templates

Use case: Filter content when working inside Templates.

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

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

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

Review in Backlinks

Use case: Review content when working inside Backlinks.

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

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

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

Copy in Graph view

Use case: Copy content when working inside Graph view.

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

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

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

Import in Search

Use case: Import content when working inside Search.

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

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

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

Open in Archive and deleted notes

Use case: Open content when working inside Archive and deleted notes.

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

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Archive and deleted notes result.

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

Create in All notes

Use case: Create content when working inside All notes.

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

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

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

Edit in Notebook tree

Use case: Edit content when working inside Notebook tree.

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

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

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

Save in Tags

Use case: Save content when working inside Tags.

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

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

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

Export in Editor

Use case: Export content when working inside Editor.

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

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

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

Search in Tasks view

Use case: Search content when working inside Tasks view.

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

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

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

Filter in Daily notes

Use case: Filter content when working inside Daily notes.

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

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

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

Review in Templates

Use case: Review content when working inside Templates.

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

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

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

Copy in Backlinks

Use case: Copy content when working inside Backlinks.

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

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

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

Import in Graph view

Use case: Import content when working inside Graph view.

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

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

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

Open in Search

Use case: Open content when working inside Search.

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

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

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

Create in Archive and deleted notes

Use case: Create content when working inside Archive and deleted notes.

User action: Go to Archive and deleted notes, complete the visible fields, and use the nearest create control when it applies.

Expected outcome: DawnDesk updates, saves, copies, exports, or displays the Archive and deleted notes result.

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

Edit in All notes

Use case: Edit content when working inside All notes.

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

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

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

Save in Notebook tree

Use case: Save content when working inside Notebook tree.

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

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

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

Export in Tags

Use case: Export content when working inside Tags.

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

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

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

Search in Editor

Use case: Search content when working inside Editor.

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

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

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

Filter in Tasks view

Use case: Filter content when working inside Tasks view.

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

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

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

Review in Daily notes

Use case: Review content when working inside Daily notes.

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

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

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

Copy in Templates

Use case: Copy content when working inside Templates.

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

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

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

Import in Backlinks

Use case: Import content when working inside Backlinks.

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

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

Tip: Use descriptive names and check status messages so Backlinks 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

Notes Documentation

Overview

How to use this guide

Image Placeholders

Quick Start

Core Workflows

Create a note

Organize with notebooks

Use tags

Create daily notes

Work with backlinks

Workspace Areas

How to use All notes

How to use Notebook tree

How to use Tags

How to use Editor

How to use Tasks view

How to use Daily notes

How to use Templates

How to use Backlinks

How to use Graph view

How to use Search

How to use Archive and deleted notes

Practical Reference

Open in All notes

Create in Notebook tree

Edit in Tags

Save in Editor

Export in Tasks view

Search in Daily notes

Filter in Templates

Review in Backlinks

Copy in Graph view

Import in Search

Open in Archive and deleted notes

Create in All notes

Edit in Notebook tree

Save in Tags

Export in Editor

Search in Tasks view

Filter in Daily notes

Review in Templates

Copy in Backlinks

Import in Graph view

Open in Search

Create in Archive and deleted notes

Edit in All notes

Save in Notebook tree

Export in Tags

Search in Editor

Filter in Tasks view

Review in Daily notes

Copy in Templates

Import in Backlinks

User Safety Notes