Keep knowledge attached to the work
Signals is the shared knowledge space for your projects and teams. Use it to keep decisions, updates, lessons, reference articles and working instructions available after the immediate conversation has passed.
A publication has a knowledge type and an audience. A decision describes what was agreed; its access setting determines who can read it. Publishing a post does not create a project, assign a task or change anyone’s permissions.
Choose a project or team space to read its knowledge. Home, Projects, Teams, Saved and Recent help you find material across the spaces you can access.
Choose a space or feed
| Navigation | What to use it for |
|---|---|
| Home | Knowledge across the spaces available to you |
| Projects / Project spaces | Browse project knowledge or open a named project |
| Teams / Team spaces | Browse team knowledge or open a named team |
| Saved | Return to posts you bookmarked |
| Recent | Find recent activity |
| Search knowledge and Type | Search by text and narrow results to a knowledge type |
Choose the knowledge type
| Type | Use it for |
|---|---|
| Update | Progress or a change people need to know about |
| Decision | An agreed choice, its context and the next action |
| Insight | A finding or lesson worth reusing |
| Article | A longer explanation with sections and a summary |
| Guide | Instructions for completing a specific piece of work |
| Playbook | A repeatable method, checklist or operating procedure |
| Question | A question for the people in the selected space |
| Announcement | A notice that needs the audience’s attention |
Publish a useful entry
- 1Open New post
Use + or Share an update, decision or reusable insight… in the feed.
- 2Choose the type and write a clear title
Describe the subject so colleagues can find it later. Add the decision, explanation or instructions in the body; Article, Guide and Playbook also provide a summary.
- 3Structure the content
Use the heading, bullet-list and quote controls for longer material. Add tags that describe the work.
- 4Add sources
Attach files or images and add labelled links in Sources & attachments when creating the post. Review the files and audience before publishing.
- 5Choose Access and publish
Choose Only me, One project or Selected teams. Select the specific project or teams, then publish the entry.
Choose exactly who can open the post
| Access | Meaning |
|---|---|
| Only me | A private entry for your own use |
| One project | Choose one accessible project; its permitted members can open the entry |
| Selected teams | Select the teams that need the material |
Read, discuss and reuse
- Open a post to read the full entry and discussion. Add a comment when context needs clarification.
- Use Helpful for useful material and Save to return to it from Saved.
- Pin reference material when publishing so it remains easy to find in Pinned.
- Use the edit or delete controls offered for posts you are permitted to manage. Deletion asks for confirmation.
- An external link opens its source; access to that service is governed by the source’s own permissions.
Keep project actions in the project applications
Use Signals to explain why a decision was made or how a method works. Assign the delivery task in Project Workspace, manage the team in Team Canvas and prepare personal launch paths in Onboarding. Link relevant knowledge so people can return to the context.