Skip to main content
Common questions about the Context Library. For Desktop questions see the Palette Desktop FAQ. For broader Palette questions see the general FAQ.

​
How does the Context Library work?

Connect supported company tools. Palette captures selected activity and check-ins, then refreshes scoped context pages once each week. People read pages in Palette, and compatible agents can search and read permitted context through MCP. See How the Context Library works for the full flow.

​
What if the AI gets things wrong?

Generated fields can include a model-provided confidence value and source citations. Team check-ins add corrections or context that tool activity does not contain. Confidence is not a guarantee, so people should still review important information before acting on it.

​
How is this different from a dashboard?

Dashboards are useful for metrics and reporting. The Context Library instead presents generated company context as readable pages for people and agents. Those pages refresh weekly from selected source activity and check-ins.

​
How is this different from a wiki?

Wikis are useful for authored knowledge and durable reference material. The Context Library complements them by generating scoped context from selected activity and check-ins. Both can be useful, and neither removes the need for review and ownership.

​
What tools do you connect to?

The current organization setup guides cover Slack, Jira, Linear, GitHub, and Notion. Connection availability can vary during early access. Google Calendar is a personal Connector Gateway connection, not an organization-level Context Library connection.

​
How long does setup take?

Connection time depends on the tool, the sources you select, and your organization’s early-access setup. After the connections are active, wait for the first generated context pages to appear. Your Palette onboarding contact can confirm the initial generation schedule.

​
Why not just connect my tools to Claude or ChatGPT directly?

Direct connections can give an AI tool source-specific data. The Context Library instead composes selected activity into generated organization, team, and user pages. When an agent reads those pages through MCP, it only receives context allowed by the signed-in person’s Palette permissions.

​
What if we already have good processes?

The Context Library does not replace good processes, authored docs, or clear ownership. It makes selected context from those processes available as scoped pages that permitted people and agents can read.