Prompt Manager Documentation

Overview

Prompt Manager helps you stop rewriting the same AI instructions. Store dependable templates, add placeholders, keep outputs close to the template, and reuse prompts from one place when working with DawnDesk AI provider 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.

Image Placeholders

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

Quick Start

1. Open Prompt Manager.
2. Create a new prompt.
3. Give it a descriptive title.
4. Write the prompt body with enough context to be reusable.
5. Add placeholders like [Topic], [Code], or [Audience] when a part changes each time.
6. Save the prompt.

Core Workflows

Save a reusable prompt

Use this workflow when you want to save a reusable prompt in DawnDesk with a clear beginning, result, and confirmation step.

#### Steps

1. Open Prompt Manager.
2. Create a new prompt.
3. Give it a descriptive title.
4. Write the prompt body with enough context to be reusable.
5. Add placeholders like [Topic], [Code], or [Audience] when a part changes each time.
6. Save the prompt.

#### What To Check

• Step 1: After this step, DawnDesk should show progress toward save a reusable prompt.

- 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 save a reusable prompt.

- 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 save a reusable prompt.

- 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 save a reusable prompt.

- 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 save a reusable prompt.

- 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 save a reusable prompt.

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

Reuse a prompt

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

#### Steps

1. Open Prompt Manager.
2. Search or browse for the right template.
3. Fill in variable placeholders mentally or in the prompt body.
4. Copy the prompt.
5. Paste it into the AI workflow or provider you want to use.
6. Update the saved prompt if the improved wording works better.

#### What To Check

• Step 1: After this step, DawnDesk should show progress toward reuse a prompt.

- 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 reuse a prompt.

- 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 reuse a prompt.

- 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 reuse a prompt.

- 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 reuse a prompt.

- 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 reuse a prompt.

- 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 prompt work

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

#### Steps

1. Group prompts by outcome, module, audience, or project.
2. Keep titles direct.
3. Archive prompts that no longer work.
4. Store important generated outputs when the app supports it.
5. Review prompts periodically to remove duplicates.

#### What To Check

• Step 1: After this step, DawnDesk should show progress toward organize prompt work.

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

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

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

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

- 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 Prompt library

Prompt library is part of Prompt 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.

#### How To Use This Area

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

#### Practical Tips

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

#### Checklist

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

How to use Prompt editor

Prompt editor is part of Prompt 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.

#### How To Use This Area

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

#### Practical Tips

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

#### Checklist

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

How to use Template variables

Template variables is part of Prompt 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.

#### How To Use This Area

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

#### Practical Tips

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

#### Checklist

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

How to use Copy controls

Copy controls is part of Prompt 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.

#### How To Use This Area

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

#### Practical Tips

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

#### Checklist

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

How to use Saved outputs

Saved outputs is part of Prompt 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.

#### How To Use This Area

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

#### Practical Tips

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

#### Checklist

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

How to use Profile area

Profile area is part of Prompt 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.

#### How To Use This Area

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

#### Practical Tips

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

#### Checklist

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

How to use Search and organization

Search and organization is part of Prompt 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.

#### How To Use This Area

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

#### Practical Tips

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

#### Checklist

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

Practical Reference

Open in Prompt library

Use case: Open content when working inside Prompt library.

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

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

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

Create in Prompt editor

Use case: Create content when working inside Prompt editor.

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

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

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

Edit in Template variables

Use case: Edit content when working inside Template variables.

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

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

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

Save in Copy controls

Use case: Save content when working inside Copy controls.

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

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

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

Export in Saved outputs

Use case: Export content when working inside Saved outputs.

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

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

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

Search in Profile area

Use case: Search content when working inside Profile area.

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

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

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

Filter in Search and organization

Use case: Filter content when working inside Search and organization.

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

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

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

Review in Prompt library

Use case: Review content when working inside Prompt library.

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

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

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

Copy in Prompt editor

Use case: Copy content when working inside Prompt editor.

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

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

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

Import in Template variables

Use case: Import content when working inside Template variables.

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

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

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

Open in Copy controls

Use case: Open content when working inside Copy controls.

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

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

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

Create in Saved outputs

Use case: Create content when working inside Saved outputs.

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

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

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

Edit in Profile area

Use case: Edit content when working inside Profile area.

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

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

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

Save in Search and organization

Use case: Save content when working inside Search and organization.

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

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

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

Export in Prompt library

Use case: Export content when working inside Prompt library.

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

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

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

Search in Prompt editor

Use case: Search content when working inside Prompt editor.

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

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

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

Filter in Template variables

Use case: Filter content when working inside Template variables.

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

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

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

Review in Copy controls

Use case: Review content when working inside Copy controls.

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

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

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

Copy in Saved outputs

Use case: Copy content when working inside Saved outputs.

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

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

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

Import in Profile area

Use case: Import content when working inside Profile area.

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

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

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

Open in Search and organization

Use case: Open content when working inside Search and organization.

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

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

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

Create in Prompt library

Use case: Create content when working inside Prompt library.

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

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

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

Edit in Prompt editor

Use case: Edit content when working inside Prompt editor.

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

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

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

Save in Template variables

Use case: Save content when working inside Template variables.

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

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

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

Export in Copy controls

Use case: Export content when working inside Copy controls.

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

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

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

Search in Saved outputs

Use case: Search content when working inside Saved outputs.

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

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

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

Filter in Profile area

Use case: Filter content when working inside Profile area.

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

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

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

Review in Search and organization

Use case: Review content when working inside Search and organization.

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

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

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

Copy in Prompt library

Use case: Copy content when working inside Prompt library.

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

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

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

Import in Prompt editor

Use case: Import content when working inside Prompt editor.

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

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

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