Step 3: Knowledge
Step 3 asks what should everyone on this team know? Every member inherits the knowledge you attach here. Having no knowledge yet is fine.
Connect an existing knowledge base
Open the picker
Click Connect existing. A drawer titled Connect knowledge bases opens with a search box. If nothing is available it says "No knowledge bases available to this team."
Screenshot placeholderScreenshot to add: The Connect knowledge bases drawer listing available knowledge bases. Choose and confirm
Select one or more knowledge bases and close the drawer. They appear as cards, each tagged Public, Project or Private, and the section tag shows how many are connected.
Remove one (optional)
Click the x on a card. Removing a knowledge base stops new hires getting it. Current members keep it.
Upload new files
Open the upload dialog
Click Upload files. A modal titled Upload files opens.
Screenshot placeholderScreenshot to add: The Upload files modal with Who can use it, Knowledge base name and the drop zone. Choose who can use it
Under Who can use it, pick one:
- Public — everyone in the organization can read it. Only offered to users with the right admin permission.
- Private — only you, plus members you grant it to. Enabled only if you are the Force owner.
- Project — everyone working in this project.
Name it and add files
Type a Knowledge base name (for example
AP runbooks), then drop files onto the drop zone or click it to choose them. Accepted types are PDF, Word (.docx), Excel (.xlsx), text, Markdown, CSV, JSON and HTML, up to 50 MB each. A file over the limit is rejected with a message.Upload
Click the upload button. A toast confirms when the knowledge base is ready. It is connected to the Force automatically. If some files fail, you see a message telling you which.
What the team knows
Below the knowledge bases, What the team knows shows what the team has learned from real work: precedents, coaching notes and Force memories. It starts empty and fills as the team runs.
Continuing
Click Shared resources to continue, or Skip for now. Either one saves a checkpoint. If saving fails you see "Could not save this setup step".
Next: Step 4: Resources.