What the AI can see

The AI analyst works for your MSP team, inside the same permissions and customer boundaries as the rest of Revo.

What it sees

• The page you're on, when you share it. The chip at the top of the Ask AI panel shows exactly what's shared: the page, its customer and the ids of the records on it (a finding, device, assessment, asset, Microsoft 365 user, patch deployment, vulnerability or agent fix). Remove the chip or turn off Include page to ask without it; the choice is remembered.
• Records it looks up itself with read tools: findings, assessments, devices, vulnerabilities, posture, insights, agent fixes and the other data you could open yourself, with the same permissions. It looks records up rather than trusting what the page says. Reading never changes anything.
• Live checks it runs: DNS lookups, TLS, HTTP security headers and email security (SPF, DMARC and so on), only against a customer's own registered domains, of the customer the check is for. A request for any other host is refused.

Customer conversations and All customers conversations

A conversation is either pinned to one customer or about All customers. The first chip in the Ask AI panel shows which: the customer's name, or All customers.

• The default. In a customer's workspace, a new conversation is pinned to that customer. On a portfolio page (the dashboard, a list across customers) it's pinned to a customer only if the shared page is about that one customer; otherwise it's an All customers conversation.
• Choosing. Before you send the first message, click × on the customer chip to ask about all customers instead, or click the dashed All customers chip to pin the conversation to the customer again. After the first message the choice is fixed for the conversation.
• Moving between pages. A pinned conversation stays with its customer: on another customer's page the panel doesn't share that page and offers a new conversation for the new customer instead, with a way back. An All customers conversation stays open wherever you go, and the page you're on is shared with each message you send from it (unless you turn Include page off), so one conversation can carry context from several customers.

These protections apply only to pinned conversations:

• the tools refuse records, live checks and lists of any other customer;
• another customer's page is never shared with it, and a portfolio page shares only its kind and the ids of the pinned customer's records, never its title, summary or filters.

In an All customers conversation the analyst can read, with your permissions, any customer of your workspace, just as you can across the portfolio. Pin a conversation when it should stay about one customer, for example before copying its answer into a customer-facing report.

What holds for every conversation: the analyst works inside your workspace only and never sees another MSP's data; it has your role's permissions and nothing more; live checks only reach the registered domains of the customer they're for; and internet searches are checked against every customer's stored identifiers, whatever the scope. Customer-portal users don't have access to the assistant.

Untrusted data and prompt injection

Data from scanned systems (web pages, DNS records, banners) and even text on the page (a finding title, a device name) could have been written by an attacker. Revo treats it as untrusted:

• it's scanned for prompt-injection attempts, which are flagged;
• page context is used only to know what you mean, and facts are checked with tools;
• the analyst can't make changes; it can only file approval requests.

Secrets found by the dark web scan (passwords, keys, tokens) are redacted before they're stored, so they never reach the analyst.

Web search

The analyst can search the public internet for advisories and vendor guidance. Only the search query is sent to the AI provider's search service, never the conversation. Queries (at most 300 characters) must be plain ASCII after Unicode NFKC normalisation. A query is blocked before it's sent if it contains a domain, name, hostname, Microsoft 365 user or contact email that Revo stores for any customer in the workspace, an email address, or an IP address in one of the recognised forms. Hex numbers shaped like Windows error codes, such as 0x80070005, are allowed on purpose. If the stored identifiers can't all be checked, nothing is searched. One message makes at most 8 search calls and 12 page reads, and one search call can run several searches at the provider, within a limit for the whole message. The check is best effort beyond that: it can't recognise identifying details Revo doesn't store (such as a name you type into the chat), IP or email forms it doesn't list, or every possible disguise, and it ignores generic words. An administrator can turn search off in Settings → AI. See Internet search for exactly what is guaranteed and what is best effort.

Monthly allowance

Each of these counts as one AI request against your plan's monthly allowance:

• a chat message;
• a finding analysis;
• a remediation plan;
• an AI-written report summary.

Settings → Billing shows this month's use against the allowance. When it's used up, new AI requests are refused until next month, and report summaries use standard text instead.

Records and audit

Conversations are kept so you can carry on with them. AI actions (requests filed, approved, rejected) are recorded in the audit log.

For how Revo protects data generally, see How your data is protected.