Evaluate third-party connectors in the Teamwork Graph
Who can do this? Role: Site admin, Organization admins Atlassian Cloud: Standard, Premium, Enterprise Atlassian Government Cloud: Not available |
|---|
Rovo integrates with your tools through connectors that bring data into Atlassian’s Teamwork Graph.
Some connectors are built by Atlassian, while others are built by third-party developers. This page explains how these connectors differ, how you can evaluate third-party connectors, and what to consider before you enable them.
How to set up a Teamwork Graph connector
What’s the difference between Atlassian-built and third-party connectors?
The main distinction is governance.
Atlassian-built connectors are governed and maintained by Atlassian, while third-party connectors are independently built and managed by their developers. This means behaviours like how the data syncs and is deleted, or how permissions are handled can vary.
More about how Atlassian-built connectors handle your data
Understand how they differ across a range of common capabilities:
| Atlassian-built connectors | Third-party connectors |
|---|---|---|
Built and maintained by | Atlassian | Independent third-party developers |
Data freshness | Managed by Atlassian to meet published standards. | Varies. May be listed in Capabilities. |
Permissions handling | Mirrors source permissions with regular checks. | Varies. May be workspace-wide and listed in Capabilities. |
Deletion sync | Anything deleted at the source is reflected in the Teamwork Graph. | Varies. You might need to disable the connection to delete the data. |
Privacy and terms | Developer privacy policy and terms apply. |
Evaluate a connector
When you’re deciding if a third-party connector is right for your needs, there’s a few aspects to consider:
When you’re first exploring the Marketplace listing, review the developer’s privacy policy linked from the consent screen.
Review the connector’s capabilities. These include: Data permissions, how data stays up to date, and data sync. Keep in mind, capabilities are self declared and not verified by Atlassian.
Confirm the connector aligns with your organisation's retention, deletion, and access-control policies. If deletions aren’t synced, data may persist until you disconnect the connector.
Connector capabilities
Understanding what capabilities a connector has can help you decide if the connector is right for you.
When configuring a connector, you’ll be shown whether the third-party has declared how they manage data permissions, data freshness, and data syncing.
Capabilities are self declared by the developer or vendor who created the connector and they're not verified by Atlassian. Sometimes, a developer may choose not to declare their app’s exact capabilities. When you’re evaluating a connector, we recommended you contact the developer directly to learn more.
Here’s some more information about how each capability works:
Connector capability | Description |
|---|---|
Data permissions |
|
How data changes at source are handled | There’s three ways data is updated, if declared:
If this is not declared by the developer, data might not reflect the current state of the source. |
Data mode |
|
If you want to make sure that data will be deleted from the Teamwork Graph when it’s deleted at the source, look for connectors that declare they’re set up to add, update, and delete data.
Otherwise, you may need to disconnect and reconnect the connector to delete data.
Disconnect a third-party connection
If you want to disable a third-party connector, and remove all its ingested data from the Teamwork Graph:
Go to Atlassian Administration. Select your organization if you have more than one.
Select Rovo, then Rovo access.
Under Sites, expand the site, and locate the app you’d like to remove, select the More actions () menu.
Select Disconnect, and on the confirmation popup, select Disconnect again.
Was this helpful?