Home›Agents›Atlassian Rovo Agents

AgentenCode evidence profileEnterprise

✓ Editorially reviewedChecked: September 30, 2026

Agent profile · Enterprise

Atlassian Rovo Agents

Atlassian Rovo Agents is classified by AgentenCode as a workplace agents from Atlassian. It belongs to the Enterprise category. This English profile does not maintain a separate factual record: it renders the same underlying evidence, trust and history data as the German profile.

AtlassianEnterpriseTeams & Businesses

View profile ↓Check sources ↓

Enterpriseeditorial classification

Atlassianprovider

11 primary sourcessource status

September 30, 2026last verification

AgentenTrust 2.0 · EU & governance evidence

Trust, privacy and control evidence for Atlassian Rovo Agents

Direct answer: AgentenCode currently documents 10 of 36 normalized trust controls for this profile. Missing fields remain Unknown and are never automatically interpreted as “no”.

EU AI ActEvidence context only. AgentenCode does not infer legal applicability or compliance from individual product controls.

GDPRPrivacy and security signals are documented field by field. Data residency alone is not a compliance or transfer assessment.

Privacy contextPrivacy & data2 of 8 documentedResidency, training, retention, DPA, subprocessors and processing scope.

Security contextSecurity & access6 of 10 documentedEncryption, SSO, SCIM, RBAC, roles and credential handling.

Human controlHuman control0 of 10 documentedApproval, oversight, permissions and stop or rollback controls.

TraceabilityAudit & traceability2 of 8 documentedAudit logs, APIs, SIEM, observability, tracing and activity history.

Important: these numbers show evidence coverage, not a product rating. 0 of 10 means that no field-level public evidence is stored for those ten controls in the current dataset. It does not mean the product lacks those capabilities.

Field-level evidence

Documented controls and values from primary sources.

Documented yesDocumented valueUnknown remains unknown

High confidence

Governance · Audit logs · API

Yes — documented

Rovo audit activity is available through Atlassian organization audit-log APIs.

Scope: rovo_organization_audit_events · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Audit logs · Available

Yes — documented

Rovo admin and user actions are recorded in Atlassian organization audit logs.

Scope: rovo_admin_and_user_actions · verified 2026-10-02 · Primary source ↗

High confidence

Governance · RBAC

Yes — documented

Rovo agent administration and editing use explicit role-based permissions.

Scope: rovo_agent_creation_editing_and_usage · verified 2026-10-01 · Primary source ↗

High confidence

Governance · SCIM

Yes — documented

Rovo access can be governed through Atlassian organization SCIM provisioning.

Scope: atlassian_org_users_accessing_rovo · verified 2026-10-01 · Primary source ↗

High confidence

Governance · SSO · Saml

Yes — documented

Rovo user access inherits Atlassian organization SAML SSO controls.

Scope: atlassian_org_users_accessing_rovo · verified 2026-10-01 · Primary source ↗

High confidence

Privacy · Data residency · Available

Yes — documented

Rovo supports data residency for in-scope data.

Scope: rovo_in_scope_data · verified 2026-10-01 · Primary source ↗

High confidence

Privacy · Data residency · Customer Region Selectable

Yes — documented

Organizations can pin in-scope Rovo data to supported geographic regions through Atlassian data-residency controls.

Scope: rovo_in_scope_data · verified 2026-10-02 · Primary source ↗

High confidence

Protocols · Mcp · Client

Yes — documented

Rovo can consume external MCP servers for agent tool invocation.

Scope: rovo_out_of_box_third_party_mcp_agents · verified 2026-10-01 · Primary source ↗

High confidence

Security · Encryption · At rest

AES-256

Rovo customer data is covered by Atlassian's AES-256 encryption-at-rest control.

Scope: rovo_customer_data · verified 2026-10-01 · Primary source ↗

High confidence

Security · Encryption · In transit

TLS 1.2+

Rovo inherits Atlassian Cloud TLS 1.2+ transport encryption.

Scope: rovo_customer_data · verified 2026-10-01 · Primary source ↗

High confidence

Security · Soc2 Type2

Yes — documented

Atlassian documents completed SOC 2 assessment for Rovo and AI.

Scope: rovo_and_atlassian_ai · verified 2026-10-01 · Primary source ↗

Evidence-backed overview

What is Atlassian Rovo Agents?

Product-specific evidence for Atlassian Rovo Agents

This profile links 11 unique primary sources across the product profile, field-level evidence, trust controls and documented relations. The points below describe this product’s stored evidence rather than generic characteristics of Enterprise.

Data Residency

Yes · Scope: rovo_in_scope_data · verified 2026-10-01.

Primary source ↗

Region auswählbar

Yes · Scope: rovo_in_scope_data · verified 2026-10-02.

Primary source ↗

Verschlüsselung at rest

AES-256 · Scope: rovo_customer_data · verified 2026-10-01.

Primary source ↗

Verschlüsselung in transit

TLS 1.2+ · Scope: rovo_customer_data · verified 2026-10-01.

Primary source ↗

SOC 2 Type 2

Yes · Scope: rovo_and_atlassian_ai · verified 2026-10-01.

Primary source ↗

Audit Log API

Yes · Scope: rovo_organization_audit_events · verified 2026-10-01.

Primary source ↗

AgentenCode treats this page as a reference profile rather than a ranking. Product facts are separated from editorial classification, and the profile is tied to a specific verification date. If a capability is not backed by sufficiently precise public evidence, it remains unknown instead of being inferred from marketing language or from similar products.

1primary source

11field-level evidence claims

10documented trust controls

2history events

How to read the evidence

The field-level evidence layer records a value, a scope, a confidence level, a verification date and one or more primary sources. Scope matters: an enterprise-only security feature must not be generalized to every plan or deployment surface. The same rule applies to hosting, privacy, audit and protocol claims.

AgentenCode also keeps Unknown distinct from false. A missing claim means the public dataset does not currently contain sufficiently precise evidence for that field. A negative value is used only when a reliable primary source explicitly documents a restriction or non-availability.

Decision context

Provider and category

Atlassian Rovo Agents is documented under Enterprise and is associated with Atlassian. Category labels help navigation but do not replace product-specific evidence.

Verification status

The public profile is marked editorially reviewed and was last checked on September 30, 2026.

Trust coverage

10 of 36 normalized trust controls currently have field-level public evidence. The remaining controls are not treated as negative findings.

Source-first use

For procurement, security or legal decisions, use the linked primary sources and verify the plan, region and configuration that apply to your organization.

Capabilities, strengths and deployment checks for Atlassian Rovo Agents

Atlassian Rovo Agents is classified as Workplace Agents from Atlassian. The profile’s editorial layer is derived from the stored use cases, strengths and checks below; claims about security, privacy or governance remain separate and require field-level evidence.

Projektarbeit

This use case is part of the stored profile for Atlassian Rovo Agents. The related strength is “Jira- und Confluence-Kontext”. In a production evaluation, the practical boundary to verify is: Agentenrechte an bestehende Berechtigungen koppeln.

Wissensmanagement

This use case is part of the stored profile for Atlassian Rovo Agents. The related strength is “Konfigurierbare Agentenrollen”. In a production evaluation, the practical boundary to verify is: Automationsaktionen testen.

Ticket- und Dokumentenarbeit

This use case is part of the stored profile for Atlassian Rovo Agents. The related strength is “Atlassian-Berechtigungen”. In a production evaluation, the practical boundary to verify is: Verbundene Apps separat absichern.

Team-Automation

This use case is part of the stored profile for Atlassian Rovo Agents. The related strength is “Integration in Teamworkflows”. In a production evaluation, the practical boundary to verify is: Agentenrechte an bestehende Berechtigungen koppeln.

What to verify before adoption

Agentenrechte an bestehende Berechtigungen koppeln. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Automationsaktionen testen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Verbundene Apps separat absichern. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.

Editorial boundary: The use-case and strength descriptions are product-specific editorial context based on the stored profile. Trust, privacy and governance statements are only presented as facts when field-level primary-source evidence exists.

Verified history

The public history layer records only confirmed profile changes and verification events. Monitoring signals are not published as product facts until they have been reviewed.

September 30, 2026 · Verification Update
September 28, 2026 · Schema Upgrade

Official sources

This profile links 11 unique primary sources across the product profile, field-level evidence, trust layer and documented relations. Provider documentation remains authoritative when the product changes between verification cycles.

Frequently asked questions

What is Atlassian Rovo Agents?

Atlassian Rovo Agents is listed by AgentenCode as an enterprise agent or agentic product from Atlassian.

How much trust evidence is documented for Atlassian Rovo Agents?

The current trust layer documents 10 of 36 normalized controls. Missing controls remain unknown rather than being treated as false.

When was this profile last checked?

The current profile verification date is September 30, 2026. The linked primary sources remain authoritative if the product changes between checks.

Method note: AgentenCode does not certify GDPR or EU AI Act compliance. It documents evidence that can support a separate legal, security or procurement assessment.