Per-Project Behavior

How Bob works across multiple projects in your organization.

Bob is organization-scoped but project-aware. This means Bob has access to all projects in your organization, but every conversation and action plan is tied to a specific project context. Understanding this distinction helps you get the most accurate and relevant guidance from Bob.

How project context works

Bob can analyze any project in your org

Bob has visibility into every project within your organization. He can pull crawl data, probe results, scores, competitor analysis, and sentiment data from any project you have access to.

Use the project selector to switch context

At the top of the agent interface, a project selector lets you choose which project Bob is currently focused on. When you switch projects, Bob loads that project's data and tailors his responses accordingly.

Each conversation is scoped to a specific project

When you start a chat with Bob, the conversation is tied to the project selected at the time. This ensures Bob's answers reference the correct crawl results, scores, and action history. If you need Bob to look at a different project, switch the project selector before asking your question.

Action plans are project-specific

Every action item Bob proposes lives under a specific project. This means:

  • Proposed actions are scoped to the project they were generated for
  • The Action Plan view filters to the currently selected project
  • Executed actions are logged against the project they affected
  • You will not accidentally apply a fix meant for one site to a different one

Organization-wide settings

While action plans and conversations are project-specific, certain settings apply across your entire organization:

  • Guardrails: Your autonomy level, risk profile, and allowed action types are set at the org level and apply to all projects uniformly
  • Risk profile: The confidence threshold governs Bob's behavior across every project
  • Integrations: Connected tools (Asana, Monday, Linear, Notion) receive action items from all projects through a single configuration

This design keeps your safety boundaries consistent. You do not need to configure guardrails separately for each project.

Mention the project name in your message to Bob to ensure he's looking at the right context. For example: "Bob, how is the schema health for the Acme Corp project?" This is especially helpful if you have many projects and want to confirm Bob is referencing the correct one.

Switching between projects

  1. Open the agent interface at /app/agent.
  2. Click the project selector at the top of the page.
  3. Choose the project you want Bob to focus on.
  4. Start a new conversation or continue reviewing the selected project's Action Plan.

Bob immediately loads the selected project's data. Any questions you ask or actions you review will reference this project until you switch again.

Best practices

  • One project per conversation: Avoid switching projects mid-conversation. Start a new chat when you want to discuss a different project to keep Bob's context clean.
  • Name your projects clearly: Descriptive project names (e.g., "Acme Corp (Marketing Site)") help Bob disambiguate when you reference a project by name in chat.
  • Review action plans per project: Periodically switch to each project and review its Action Plan to ensure nothing is waiting for approval.