Team knowledge
Put team-specific workflows, project documentation, meeting notes, playbooks, and guidelines in the team’s knowledge location in Library.
-
Find the intended team’s knowledge location.
-
Create a note where you have permission, or ask Play in chat:
Save this to the engineering team’s knowledge.
-
Check the saved location and contents, especially before adding sensitive information.
-
Keep the note current as the team’s process changes.
Team members can read the team scope. Team shelves are initially shared with the team for writing, but a particular location or note can have different permissions. If a note opens as view only, ask someone with the appropriate access to make the change.
| Intended use | Where to put the information |
|---|---|
| Relevant across the company | Organization knowledge |
| Specific to how one team works | That team’s knowledge |
| Personal context or preferences | Personal knowledge |
Sharing grants can affect access beyond the default scope. Review them rather than treating a team folder’s name as a privacy guarantee.
Still stuck? Email support@play.fast