Project Context

Project context is scoped to a single project, and changes on an ongoing basis as the team or work evolves. Where workspace and connection context set the ground rules everyone builds on, project context is for the things that only make sense for a particular team, department, or piece of work.

Project context can be defined via the UI in any given project under 'Manage project'.

or synced via the API if it needs to update automatically from your own systems:

curl -XPATCH https://api.eu.count.co/v1/projects/project_key \
  -H"Authorization: Bearer $COUNT_API_KEY" \
  -H'Content-Type: application/json' \
  -d'{"agent_context":"This project contains our retail sales data..."}'

#What belongs in project context?

Connection context might include:

• Scope & definitions: what this project covers, and how term sshould be interpreted here even if they mean something different elsewhere in the business.
• Data guides: team-specific direction on how to work with data within this project: which source is authoritative for this team's questions, which fields to prioritize, caveats that only apply to how this team uses the data.
• Formatting & output: team-specific style guides: preferred chart types, layouts and naming conventions for this project's outputs.