← Tallin / Home

Product · Coverage

Know what Tallin can observe and control.

Visibility comes from the sources you connect. Enforcement comes from supported admin actions and the traffic you route through Tallin. They are different capabilities, shown with their source and scope.

TallinCoverage · Illustrative source records

Know what the record proves.

Browser
DeepSeek hostname observed
Provider account unresolved
Device monitor
GitHub MCP configured
Execution not established
Provider record
Claude login reported
Activity limited to the connected source
Gateway
Unapproved model blocked
Only the request routed through Tallin
Every claim carries its source and scope.

Keep observed activity, inferred relationships, enforced controls, and uncovered areas distinct.

Sources, permissions & limits

Start with the evidence you need.

Choose the sources that answer your questions. Browser and device discovery, enterprise content supervision, and Gateway enforcement have different setup and data boundaries.

Evidence supplied, setup requirements, and limits for each Tallin source
SourceEvidence suppliedWhat you needKnown limits
Managed browsersSupported AI hostnames, visit times, managed profile identity, and extension health.Deploy the Tallin extension to managed Chrome or Edge profiles.A visit does not establish the provider account or conversation content.
Identity + provider recordsApproved access, provider membership, and available account activity.Connect supported SSO or provider records with the required administrator permissions.Membership is not always a paid license. Activity availability varies by provider.
Managed device monitorInstalled AI applications, developer tools, and supported MCP installations or configurations.Deploy the managed device monitor through your device-management process.An installation or configuration does not prove use or control MCP execution.
Security sourcesConfigured CASB, SSE, and network signals with available identity and device context.Connect or supply supported security-source evidence with the required permissions.Coverage and identity depend on the source and its deployment.
Spend + uploadsCard charges, expenses, and uploaded records that surface paid AI tools.Supply supported expense, card, or CSV records for the period under review.A charge establishes spending, not who used a tool or what they entered.
Optional browser prompt and file monitoringSubmitted prompts and file-sharing attempts on supported AI chat pages, reported as redacted excerpts, file details, and potential sensitive-information findings.Off by default. Each client’s workspace administrator enables it separately in Browser monitoring → Settings, with an updated enrolled extension.Monitoring only, without blocking. Original files and AI responses are not sent to Tallin. Coverage varies by page and file type; an attempt does not prove a completed upload.
Enterprise compliance APIsMessages, authors, timestamps, and conversation content exposed by supported enterprise APIs.Eligible Claude Enterprise, ChatGPT Enterprise, or ChatGPT Edu workspace; administrator permissions and retention setup.Separate Supervise service. Personal and unconnected workspaces are outside capture.
Tallin GatewayActor, route, model, cost evidence, policy outcome, and optional configured content capture.Route selected apps or developer tools through the hosted or VPC Gateway.Controls apply to routed requests. Direct provider calls and external tool or MCP side effects remain outside that path.

Read each claim in context

Observed does not mean controlled.

A provider API may report usage that never crossed the Gateway. That usage can be observed without being subject to gateway limits. A browser finding may establish a service visit without establishing the provider account used.

Check source health and recency alongside the label. Optional sources are choices; a failure in a source you configured needs a specific next action.

OBSERVED
Observed: direct evidence from a connected source, such as a gateway event, provider usage record, or managed-browser hostname observation. Each record states what the source establishes; identity and account attribution may remain unresolved.
INFERRED
Inferred: a conclusion drawn from supporting signals, such as a likely AI subscription found in an expense record. The source and the inference remain distinct.
ENFORCED
Enforced: a configured control applied through a supported execution path. Gateway controls govern routed requests; provider or identity access actions have their own permissions and scope.
NOT COVERED
Not covered: activity or actions for which no configured source or control provides coverage. Direct provider activity may still be observed through connected APIs without Gateway routing. Tool and MCP side effects are not controlled unless they pass through a supported enforcement path.

Choose the evidence and controls you need.

Review your providers, source permissions, and selected gateway workloads with us before rollout.

Coverage: What Tallin Can Observe and Control | Tallin