05 · Projects and teamwork
The problem projects solve
Working alone, scattered local configuration is fine. Add two colleagues and the problems arrive immediately:
- Everyone re-explains "this is what our weekly reports look like"
- One person installed the Tencent Docs connector, another did not, and the same prompt produces different results
- The client material lives on one person's machine
- The proposal one person produced arrives with no context for whoever picks it up
A project (项目) organises instructions, connectors, experts, Skills and material in one place. When a member starts a task inside it, that shared configuration is injected automatically — no repeated setup.
Structurally it is two layers: the project carries shared context and conventions; a task is a conversation a member creates inside it, one task to one conversation and one workspace.
What project configuration holds
| Item | Description |
|---|---|
| Name | Required, identifies the project |
| Instructions | Global behaviour rules for the AI, inherited by every task |
| Connectors | External services available in this project |
| Experts | Experts this project can summon |
| Skills | Skill packages this project can call |
Project instructions are the most valuable field here
This is the foundation of team collaboration. Write down rules like "documents use Song 12pt", "external files must carry the disclaimer", "every data conclusion cites its source" and every task from every member inherits them.
Officially recommended: fill this in when you create the project, so all members' tasks inherit consistent behaviour. Adding it later is easy, but earlier tasks are not retroactively affected.
Creating a project
- Click Projects (项目) in the sidebar
- Click
+at the top left - Fill in the configuration
You can also create from a template. Open the template dropdown above the instructions field, pick a preset, and the form pre-fills — modify from there. The templates cover common working scenarios and are much faster than starting blank.
Inviting members
- Click Invite (邀请) at the top right of the project page
- Copy the link and send it
- The invitee opens it, fills in a note and submits a request
- A project admin approves it in the notification centre
Anyone can invite, admins decide
Any project member can send an invitation, but an admin approves who actually joins. That means invitations do not always need an admin, without losing control.
Starting a task
Type into the task input at the bottom of the project page. On creation, three things are injected automatically:
- Project instructions — into the model context
- The project library — as reference material
- Your personal memory — into the context
Selection ranges for experts, Skills and connectors:
| Item | Range | Ordering |
|---|---|---|
| Experts | Project + personal + everything in the expert centre | Project experts pinned |
| Skills | Project + installed + imported on the spot | Project Skills pinned |
| Connectors | Connected public authorisations + project personal authorisations + the connector page | Public authorisations pinned |
The pinning rule says something clear: what the project agreed on comes first, personal choices come after.
Three ways to collaborate
Share a task
Click Invite members (邀请成员) in the task's top bar, copy the link, send it. Whoever opens it joins that conversation and works alongside you.
Good for: two people watching the same output take shape.
Hand off a task
Move the output and the context to someone else. Click the transfer icon in the task's top bar.
The system packages:
| Content | Description |
|---|---|
| Task artifacts | Every file the AI produced in this task |
| Progress summary | An execution summary WorkBuddy generates |
| Custom fields | Title, description, assignee, status, due date — all editable |
| Extra attachments | Additional supporting material you upload |
The recipient opens it with the full context and continues without needing the background explained again.
Good for: research finishes and goes to whoever writes the proposal; the proposal goes to whoever presents it.
A hand-off copies the entire context
Transferring copies the original task's full context — including the conversation log, tool call records and intermediate artifacts — into the new session.
Everything you said in that task is visible to the recipient. Have a look before you send it.
Project activity
Activity keeps members current, in three categories:
| Category | Events |
|---|---|
| Concerning me | Someone shared or handed a task specifically to me |
| Member activity | Others uploading or updating files, inviting members, publishing tasks, adding or removing Skills / experts / connectors, changing instructions |
| Automation | Notifications from automations you created (visible only to you) |
Project assets (the library)
Project assets are the project's central file store. Documents, code artifacts and reference material live here so WorkBuddy can reach the context directly during a task.
Get there via the Assets (资产) tab on the project page.
Storage quota
Each project gets its own space, 5 GB by default, backed by Tencent Drive. The toolbar shows usage live.
File types
Filter by category: documents (.md .txt .docx), spreadsheets (.csv .xlsx), slides (.pptx), PDF, images (.png .jpg .svg .webp), video (.mp4 .webm), audio (.mp3 .wav), websites (URL bookmarks), Markdown, other.
Upload sources
- Local files — pick from your computer
- Artifact files — from an artifact preview inside a project task, choose upload to cloud
Update tracking
The file list shows who updated each item and when. On a multi-person project that matters: "who changed this requirements doc", "when was that design updated" — no more asking in the group chat.
Library content is injected into task context as RAG, and the agent can also read files directly. Fuller library capabilities are in The Library.
Connectors: public versus personal authorisation
The part of projects worth thinking hardest about.
| Mode | Description | Suits |
|---|---|---|
| Public authorisation | An admin configures once, everyone shares one set of credentials | Shared team service accounts |
| Personal authorisation | Each member authorises their own account, credentials not shared | Private personal services |
A connector can exist in both modes at once
An admin can configure Feishu with a team account (public) while members also attach their own Feishu accounts (personal). Both are selectable in a task.
Collaborative tasks disable personal-authorisation connectors entirely
This one matters: in collaborative tasks, only public-authorisation connectors work.
The reason is not hard to see — in a shared session, using anyone's personal credentials would be wrong.
So before you enable collaboration, make sure the project has the public authorisations it needs, or collaborative tasks will suddenly be unable to reach anything.
Call logs for public-authorisation connectors are visible to admins only, for audit and compliance.
Automations
An automation is a special kind of task: it runs a conversation like any other, but is triggered by a preset condition rather than by you. Currently only scheduled execution is supported — a prompt runs at a set time and pushes a notification.
Automations are personal
Visible and manageable only by their creator, running in that person's own session.
An automation you create in a project is invisible and unmanageable to your teammates, and the "automation" category in project activity is likewise private. To reach the team, use a push channel (WeCom bot, mini program) rather than expecting them to see it in the UI.
Configuration: name, prompt, frequency, optional connectors. See Automations on a schedule.
Data boundaries
| Data | Where it lives | Who sees it |
|---|---|---|
| Project configuration (instructions, Skills, experts, connectors) | Cloud | Shared by project members |
| Personal-authorisation connector credentials | Member's machine, not uploaded | Only that member |
| Project library content | Cloud | Project members, injected via RAG |
| Public-authorisation connector call logs | Cloud | Admins only, for audit |
Web and desktop differences
Personal Skill libraries do not cross
The personal Skill libraries on web and desktop are separate. Project-level Skills are managed centrally in the cloud and are identical on both.
In practice: a cloud task cannot select Skills from the desktop personal library, and vice versa.
If your team uses both, put the important Skills at project level rather than in personal libraries.
FAQ
Are there caps on projects and members?
Yes, by plan. Free tier: 5 projects / 3 members each. Standard: 10 / 5. Advanced: 15 / 8. Ultimate: 20 / 10. See Credits & plans.
How do project tasks show in the sidebar?
The sidebar only lists projects that have tasks. A project with none is hidden, appears the instant a task is added, and hides again when the last one is deleted.
Do project tasks have a right-click menu?
Yes — identical to the hover "⋯" menu, with rename, share, archive and delete.
Next
06 The Library — stop artifacts scattering.