Knowledge is the stuff the team should typically know about your company — brand voice, product details, customer notes, decisions, key links. It lives in the workspace and Astra pulls from it whenever the team works on something.
What belongs in knowledge
- Brand voice and tone notes ("we write casual, no exclamation marks")
- Product specs, feature lists, positioning
- Pricing, packaging, what's free vs. paid
- Customer profiles — who you sell to, what they care about
- Decisions you don't want to re-explain ("we don't do referral discounts," "we never use stock photos")
- Key links — your site, your docs, your help center, your repo
What doesn't belong
- One-off task instructions — those go in the task brief
- Anything you'd rather the team forget tomorrow
- Secrets — API keys and passwords go in the integration settings, not knowledge
How the team uses it
Every time Astra plans a task and every time an AI employee picks one up, the relevant knowledge gets pulled in. The chairman doesn't need to repeat themselves across tasks — the team carries the context.
Keep it short
A page of well-written context beats a hundred pages of dump. Trim aggressively.
For how to add knowledge, see the add-knowledge guide.