Share Weave With Your Team
Description
Section titled “Description”What one person learns from Weave can be used by the whole project. A pinned answer or a recipe is always worked out again as the person reading or running it, with their own access, so nobody sees figures their role hides.
Pinned Answers
Section titled “Pinned Answers”Pin an answer to share it with everyone in the project.
- Under the answer in the Weave dock, choose Keep ▾ → As a pinned answer.
- Weave says the project it pins the answer to, and the title it will be listed under, which is your question. Everyone in the project will see your question and how Weave answered it.
- Click Pin.
The answer is marked Pinned. Copy link copies a link to it.
When a teammate opens a pinned answer, Weave re-runs it as them, so the figures are their own. The answer says who pinned it and when, and that Weave re-ran it for them. If what they can see differs from what you saw, they’re told You see different data here., with Ask again.
When a teammate asks Weave a question that matches a pinned answer, a line above Weave’s answer offers it: A teammate pinned an answer about this, with Show.
- Weave can pin answers it can re-run for someone else: answers from metrics and value searches, and the answers to Explain, Where is this used, What changed, Check, Tables it reads, Preview, Document and What needs attention?. Other answers can be kept as a recipe instead, and Weave offers Keep as a recipe.
- A teammate sees a pinned answer only if they can open everything it’s about.
- Whoever pinned the answer, or a project Architect, can Unpin it.
Team Recipes
Section titled “Team Recipes”A recipe is a question saved so anyone on your team can run it again, the way you asked it.
- Under an answer in the dock, choose Keep ▾ → As a recipe.
- Weave names the recipe from your question and says that everyone in the project, and the AI tools they connect to PlaidCloud, will see your question and how Weave answered it. Click Save, or Change… to ask again.
To run a recipe, type / in the dock and choose it under Recipes, or type / and its
short name. Weave runs it as you, in a conversation titled Recipe: and the recipe’s name.
The parts of a recipe that only read data run without calling an AI model. Any other part is
asked of Weave again. A change a recipe proposes is a card that you approve, as with any
other.
- Anyone who can open everything a recipe works on can see it, run it and set a trigger on it. Others don’t see it.
- Whoever saved a recipe, or a project Architect, can rename or delete it. Deleting a recipe stops the triggers people set on it.
- AI tools connected to PlaidCloud over MCP list the project’s recipes too.
Run a Recipe on a Trigger
Section titled “Run a Recipe on a Trigger”To have a recipe run by itself, choose Run on a trigger… from its ⋯ menu on the project’s Overview, and say when in the dock, such as every Monday at 08:00 or after Month-End Close runs. The recipe becomes a standing request that runs as you, listed on the Requests page as Recipe: and its name. A trigger after a workflow run does nothing when nothing the recipe reads has changed. If any part of the recipe asks Weave, the card says it Uses AI each time it runs.
Run on a trigger… is offered for recipes that read at least one table.
From Your Team on the Project’s Overview
Section titled “From Your Team on the Project’s Overview”Once something is shared in a project, its Overview has a From your team card: Answers your teammates pinned and recipes they saved, run as you. Each pinned answer shows its title, who pinned it and when. Each recipe shows its name and author, with Run and a ⋯ menu with Run on a trigger…, Rename… and Delete.
Comments and @Weave
Section titled “Comments and @Weave”Steps, workflows, tables and findings have comment threads. Choose Comment from the Weave section of an object’s right-click menu, or use the comments button in the workflow canvas toolbar for the workflow’s own thread. On a finding, open it and click Comments.
Type in Add a comment and click Add comment. Comments can’t be edited or removed.
- Mention a teammate by name, and they’re told in PlaidCloud that you mentioned them. If they can’t see what the comment is about, they aren’t told, and you’re told so.
- Mention @Weave to ask Weave a question in the thread. A note under the box says that everyone who can see the step, workflow, table or finding will see your question and how Weave answered it.
Weave answers as you, with your access, in a conversation of yours titled Comment on and what the thread is about. The thread gets one line, such as Weave answered Dana about Allocate by Driver., with Open the answer. You open your own conversation from it, and anyone else sees the answer re-run as them. If Weave proposes a change, the line says it’s waiting for you to approve it, and only you see Review the change.
If Weave can’t take the question, because Weave isn’t set up in the workspace or you haven’t agreed to how Weave uses your data, your comment is still saved and the thread says why.