Grey
Project settings
Set a Grey project's processing and transcription models and query logging, choose which sections your sidebar shows, and export the project's data.
Basics
Opening project settings
Choose Settings in Grey's sidebar to open the project's settings: General, Team & Members, Roles & Permissions, Navigation and Data Export. Settings apply to the current project only.
The Settings section appears for Owners, Admins and Managers. Changing General needs the Manage workspace settings permission, which Owners and Admins have; everyone else sees it read-only. Team & Members and Roles & Permissions are covered in Team and roles.
General
Processing and transcription models
The Models card in Settings → General picks the models Grey uses behind the scenes. They run on your own model provider connections.
- Processing connection and Processing model: a chat model for knowledge graph extraction, contextual enrichment, image descriptions and judging evaluations. A small, fast model works well. It starts as None, and those features don't run until you set one. Image descriptions need a model that can see images.
- Transcription connection and Transcription model: what transcribes audio and video sources. Automatic uses your only transcription connection, so with two or more, pick one. Leave the model on the provider's default, or choose one.
If you have no suitable connection yet, the card links to Model Providers; see Connecting a model provider. Choose Save changes at the top to keep your choices.
General
Project details and query logging
The Project card in Settings → General shows the project's Name and Project ID. Both are read-only here; rename projects in Dash.
Log queries, under Retention & logging, is on by default. Turned off, requests still appear in Usage → Request Logs with their channel, status, timing, tokens and cost, but without the question or the retrieved chunks. Choose Save changes at the top after changing it.
Navigation
Sections that depend on others
Some screens need another one to be useful, so Grey won't let you hide what a visible screen depends on, or show a screen while what it needs is hidden. The switch is disabled and explains why, with a link to the screen in the way.
- Playground, Evaluations and Request Logs need Pipelines.
- MCP Servers and Widgets need API Keys.
- Knowledge Graph needs Knowledge Bases.
To hide Pipelines, for example, hide Playground, Evaluations and Request Logs first.
Data Export
Exporting project data
Settings → Data Export downloads the project's data as JSON files, built in your browser. Choose Export on a card for one part, or Full export at the top for everything in one file:
- Knowledge bases & sources: every knowledge base and its sources' details, without the files themselves.
- Chunks: each chunk's text, order and position.
- Knowledge graph: entity and relation types, entities, relations and mentions.
- Conversations: Playground and widget conversations with their messages.
- Eval sets: evaluation sets and their cases.
If part of an export comes back incomplete, Grey still downloads the file and says what's missing. Exporting needs the Run data exports permission, which Owners, Admins and Managers have.