Your first assignment gives Para something useful to do. Your reply helps it understand how you want that work handled. When an approach is worth keeping, ask Para to save it for future work and show you the instructions. You can then use it on another assignment or include it in a recurring responsibility.
What carries forward
| Context | Where it applies | How to control it |
|---|---|---|
| The current conversation | Replies in the same email or Slack thread, or your next message on Work, pick up where you left off. A message sent while Para is still working joins the current task. Para remembers earlier work, so you can refer back to it any time. | Reply in place for a revision. In a new assignment, name the project, prior work, and method you need. |
| Saved personal guidance | Para can save useful preferences and methods for your later work. Personal guidance is not automatically shared with colleagues or limited to one project. | Say whether it is for this assignment, only a named project, or your future work. Ask what was saved, then correct or withdraw it in conversation. |
| Project documents | Documents live in Desk and Personal, or in named projects when the case.dev plugin is installed. An email thread does not change document access. | Name the current source files. Open Projects to manage documents. A new thread does not change access. |
| Team skills | Administrator-managed instructions are available on the next request to the people and groups they are assigned to in the organization. | An owner or administrator edits, disables, deletes, or changes the audience on Skills. |
| Shared Para conversations | What the organization’s Shared Para works on in Slack channels is visible to everyone in the organization, and your own Para can draw on it. | Keep private projects and personal guidance in direct messages, email, or Work. See Shared Para. |
| A saved automation | Its brief and schedule define future work using your access. It may run without the earlier conversation in front of it. | Review the saved brief, timezone, delivery, and next run. Edit or pause it when the responsibility changes. |
Tell Para which kind of correction you mean
“Shorten this update” asks for a revision. “For Northwind updates only, leave out the budget history unless it changes” gives project-specific guidance. “Save a method for my future status updates: lead with deadlines and decisions, then material changes with sources” asks for a reusable approach. These should not have the same effect.
Ask Para to show the instructions it saved and their intended scope. A project-specific instruction is part of the method you describe, not a separate project-level setting or access restriction. If that scope is wrong, reply: “Keep that rule for Northwind only; do not apply it to my other projects.” When you use the method again, check the result rather than assuming every correction was retained. Para does not remember everything, and saved guidance is not a substitute for current source documents.
You can change your mind
To withdraw personal guidance, ask Para to remove it from the saved method and confirm the change. This is not a request to erase conversation history or delivered documents. Team skills and automation prompts are separately managed, so check those too if they contain the old instruction.
Try it on familiar work
The starter guides (status updates, meeting follow-ups, and vendor review) use deliberately simple approaches, not prescribed procedures. Choose one, try it with suitable source material, and email Para what you would change. Check the result against its sources before you rely on it or send it on.
- Status updatesRequest an update, change its emphasis, and review the next scheduled delivery.
- Meeting follow-upsTurn a meeting into decisions and action items, then reuse the approach.
- Vendor reviewPrepare a preliminary memo, refine its questions, and use the method on the next vendor.
- SkillsSave a personal method or manage shared instructions.
- AutomationsConfigure and manage standing work.