Rovo connectors need separate access-and-deletion tests

Approve a connector as a data path, not a feature toggle

The direct answer is to inventory every source system, connector identity, authentication method, indexed object, field, attachment, permission model, refresh interval, cache, derived representation, query surface, and permitted action. Name the source owner and the service owner who can approve, suspend, and remove that path. A global Rovo entitlement should not silently convert an application-specific access decision into enterprise-wide retrieval. Search, summarization, and agent execution also need separate scopes because permission to read a record does not imply permission to synthesize it for another audience or act on it.

Test permission changes and negative access cases

Use accounts with overlapping and conflicting roles, guests, contractors, suspended users, transferred employees, restricted projects, private channels, legal holds, inherited groups, field-level controls, and records shared through links. Confirm what happens before and after access is granted or removed in the source. Test direct search, chat, recaps, agent tools, desktop, mobile, browser, MCP, and command-line surfaces rather than assuming one interface represents all of them. The required evidence is that a user cannot discover, infer, retrieve, cite, summarize, or act on material outside the current source authority.

Make deletion and correction observable end to end

When a source record is corrected, expired, restricted, or deleted, measure how quickly indexes, snippets, embeddings, caches, answers, citations, generated artifacts, and agent memory stop using the prior state. Preserve the source event, connector refresh, affected query, result, remediation, and confirmation. A current answer can still be unsafe if it is derived from a record that the user no longer has authority to see. Define maximum propagation windows, escalation, and a practical way to disable the connector or affected capability while stale context is investigated.

Reopen review when context or actions expand

Repeat the test when a connector, API scope, source schema, permission model, application, model, Rovo surface, agent, MCP server, action, or retention rule changes. Track coverage, forbidden retrieval, stale results, deletion latency, citation fidelity, action failures, reviewer effort, and incident recovery without turning a provider control statement into production evidence. Atlassian is the provider source; current documentation, contracts, tenant configuration, identity records, controlled negative tests, logs, and qualified architecture, data, privacy, security, records, procurement, and legal review control.

Turn this source into a reviewable decision

For AI for CIOs, use this briefing as a dated decision record rather than a substitute for the source. Preserve Atlassian, the exact URL, the August 15, 2026 review date, the supported facts above, the editorial interpretation, the limitations, and any buyer-specific evidence. Link that record to the decisions most directly affected: Enterprise knowledge retrieval; Identity and agent access; Data products and AI-ready information; Operations and incident intelligence. State whether the source changes the scope, evidence requirement, control, sequence, or only the language used to describe the decision.

Before action, name the accountable owner, affected population and workflow, exact offering or configuration, source data and rights, human decision point, exception and appeal path, complete cost, expected benefit, failure and stop conditions, retained evidence, and next review date. Keep official facts, provider statements, buyer observations, representative tests, measured outcomes, editorial inferences, and unknowns visibly separate. Reopen the record when the source, offer, model, integration, data, policy, population, responsible person, or measured result changes.

Limitations and unknowns

Atlassian is the provider source. Its current Rovo page describes cross-application search, chat, agents, connectors, user surfaces, administrative access control, policy governance, and provider trust positioning but does not independently establish a buyer’s connector configuration, source permissions, indexing, cache, deletion propagation, action rights, audit coverage, security, reliability, or outcome. Current product documentation, contracts, tenant and identity configuration, representative positive and negative tests, operating logs, and qualified architecture, data, privacy, security, records, procurement, and legal review control.