The Manage Project Page

The Manage Project page allows project owners and administrators to configure how a specific Brim project behaves, including LLM usage, token limits, and project oversight settings.

You can access this page from Settings → Manage Project

This article explains each section and when you should use it.

Overview

The Manage Project page provides project-level configuration controls that affect:

• Which LLM models are used during generation
• Project token usage limits
• Administrative visibility and auditability
• Managing your project's Single-Note API queue
• Project identification and governance

These settings apply only to the selected project, not your entire Brim environment.

At the top of the page, you’ll see:

• Project Name
• Project ID

These identifiers are useful when coordinating with your Brim administrator or support team. 

LLM Model Configuration

The LLM Model Configuration section controls which AI models your project uses during abstraction and decision workflows.

Default LLM Model

The Default LLM Model determines the primary model used for variable generation and abstraction tasks.

If no model is selected, the project will use the environment default model configured by your Brim administrator.

You may want to select a different model if your project requires higher reasoning performance, you want faster or lower-cost generation, or institutional policy restricts model usage.

Advanced Model

Some variables may have Use Advanced Model enabled in their Advanced Settings.

When enabled, Brim will use the Advanced Model specified here for those operations instead of the default model. The models available are dependent on the Admin LLM Config settings.

Project Token Usage Limit

This setting controls the maximum number of generation tokens a project may consume. The default is set by a Brim Admin, but it can be changed at the project level to a different limit, or even unlimited.

Token limits help organizations control AI usage costs and prevent runaway generations, and Project Owners to feel comfortable that they're remaining in-budget.

User Action Logs

The User Action Logs section provides an audit trail of activity within the project.

Administrators can review configuration changes, user actions and operational events.

This supports:

• Institutional compliance
• Research governance
• Debugging workflow issues

Project API Tokens

This section allows you to create and manage project-level API tokens. For more detail, see Creating a Brim API Token.

Single-Note Generations

This section allows you to view and manage single-note generations created by Brim's Single-Note API.

View Single Note Generations

This brings you to the Single-Note Queue for this project, where you can see what's currently in the queue, track the results, and pause uploads if needed.

Max Pending Generations

This manages the number of concurrent single-note generations for this project. Add more to speed up work. The maximum number is the number of workers, which you can find in Admin > Workers.

Administrative Actions

Rename Project

Change the user-facing name of your project here. It is not permitted to be the same as any other active project.

Delete Project or Data

Here you can delete various elements of this project:

1. The project itself
2. The documents in the project (All, or for specific patients)
3. The structured data in the project (All, or for specific patients)
4. Validation data for this project.

Brim will ask what you want to delete, and require typing in a phrase to confirm permanent deletion.