Skip to main content
The Context Library organizes plain-English company context into pages scoped to the organization, a team, or a user. The exact pages and fields vary with your organization’s setup and the sources it connects. Scope determines where a page belongs and who can read it. It does not give people or agents access beyond their Palette permissions. See How the Context Library works for the capture and generation flow.

​
Organization

Organization pages can describe company background, priorities, teams, and other shared context. They sit at the broadest scope.

​
Team

Team pages can describe a team’s purpose, members, focus, active work, and dependencies. They are available according to the team’s scope and the reader’s access.

​
User

User pages can describe a person’s role, team, focus, and relevant working context. User scope keeps personal context separate from organization-wide material.

​
How pages are refreshed

Palette captures selected activity from organization connections throughout the week. Team check-ins can add context or corrections that tool activity does not contain. Once each week, a generation step uses that source material to refresh generated context pages. The readable pages are not updated in real time. Generated fields can include a model-provided confidence value and source citations. A confidence value is not a simple count of supporting events, and citations can vary by field. Read more about the weekly generation step in Signal engine.

​
How people and agents read pages

People can browse context pages in Palette. In Palette Desktop, people can browse organizational context and mention a page in chat. MCP-compatible agents can search, list, and read the pages available to the signed-in person through Palette MCP. Access is on demand and follows Palette permissions. Context is not automatically preloaded into every conversation.