Agent Profiles

Agent Profiles

Agent profiles let you give AI assistants scoped access to your Pantasso workspace. Each profile defines what the assistant can read, what tools it can use, and how it should behave with company data.

This page describes the hosted public beta. Files and Obsidian are the live first source. Slack, Google Drive and Docs, Telegram, and GitHub need a connection.

Why agent profiles

AI assistants are more useful when they have access to real company context. But unscoped access creates risk. Agent profiles solve this by giving each assistant:

• Identity: A stable profile tied to a specific assistant.
• Boundaries: Clear limits on what the assistant can access and do.
• Accountability: A record of every query the assistant makes.

In the hosted public beta, that context starts as approved files and Obsidian notes. Connected sources can widen a profile only after a connection is in place.

Creating a profile

1. From the workspace control plane, go to Agent Profiles.
2. Select Create Profile.
3. Name the profile and assign it to an assistant role.
4. Configure the profile scope and allowed tools.

Profile components

Role

A human-readable description of what the assistant does. Examples: "Planning assistant," "Sales context assistant," "Support triage assistant."

Scope

Which workspace objects the assistant can access. You can scope by:

• Source: Only objects from specific connected sources. In the hosted public beta, start with Files or Obsidian. Slack, Drive, Telegram, and GitHub need a connection before those sources can appear in a profile.
• Object type: Only documents from the live first source, or later message objects after a conversation source is connected.
• Time range: Only objects from the last 30 days, etc.

Allowed tools

What the assistant can do with workspace context:

• Cited queries: Search workspace objects and receive cited answers.
• Brief generation: Create summaries from workspace context.
• Support handoff: Generate redacted support packets.

Smoke test

A saved check that verifies the assistant uses workspace context before answering. The smoke test asks a known question and confirms the assistant returns cited context rather than answering from memory.

Using profiles

Once a profile is created, the assistant uses it to access Pantasso:

1. The assistant receives a query that requires company context.
2. It checks Pantasso using its profile credentials.
3. Pantasso returns cited context within the profile scope.
4. The assistant uses that context to draft its response.

A profile does not create source access. It can only use Files, Obsidian, and later sources the workspace owner has already connected.

Monitoring

All profile activity appears in the workspace activity log. You can see:

• Which profiles are active.
• How many queries each profile made.
• Whether queries returned sufficient context or gap reports.
• When profiles were last used.