An access control list defines who can view or access a specific object in Teamwork Graph. ACLs are used to ensure data security and privacy by controlling visibility of objects based on user permissions. When building connectors, you specify ACLs for each object you add to the graph.

See Permissions and Access Control Lists for more information.

Activity relationship

An activity relationship captures user actions and interactions with objects in Teamwork Graph. These relationships record behavioral data about who did what to which objects, such as when a user created a work item, updated a Confluence page, or viewed a project. Activity relationships are automatically generated by Atlassian systems when users interact with objects.

See Relationships for more information.

API object type

An API object type represents a category of data that you can query using the Teamwork Graph API. Examples include Jira work item, User, and Atlassian project. API object types define the structure and properties of objects available for querying in the graph.

See Object types for more information.

ARI (Atlassian Resource Identifier)

An Atlassian Resource Identifier is a globally unique string used to identify content across Atlassian apps. ARIs follow the pattern ari:cloud:{app}:{siteId}:{objectType}/{objectId} and are used throughout the Teamwork Graph API to identify specific objects when querying relationships and traversing the graph.

See Understanding ARIs in Teamwork Graph for more information.

C

Canonical relationship

A canonical relationship is a direct, structural connection between objects in Teamwork Graph. These relationships define ownership, containment, and logical associations between objects, such as a work item belonging to a project, or a document having a parent document. When building connectors, you create canonical relationships using attributes like parentKey, containerKey, or associations.

See Relationships for more information.

Connector

A Teamwork Graph connector is an integration that brings data from external apps and tools into Teamwork Graph. Connectors extract data from source systems, map it to Teamwork Graph's object types, and push it into the graph via bulk APIs. Atlassian provides 100 out-of-the-box connectors, and you can build custom connectors using the Teamwork Graph connector module.

See Build a Teamwork Graph connector for more information.

Connector object type

A connector object type represents a category of data that you can use when building Teamwork Graph connectors. Examples include Work item, Document, and Project. When building connectors, you map external data to these standardized object types.

See Object types for more information.

Cypher

Cypher is a graph query language originally developed by Neo4j. The Teamwork Graph API uses Cypher for querying relationships and traversing the graph. You don't need to learn Cypher to use the Teamwork Graph API, as the documentation provides ready-to-use Cypher query examples for all supported relationships.

See GraphQL and Cypher for more information.

G

GraphQL

GraphQL is a query language for APIs that the Teamwork Graph API uses. With GraphQL, you can query exactly the data you need, making it efficient for accessing objects and relationships in Teamwork Graph.

See GraphQL and Cypher for more information.

I

Inferred relationship

An inferred relationship is a connection between objects that is not directly recorded by explicit actions or events, but is derived by Teamwork Graph itself. These relationships are calculated by analyzing patterns, metadata, or using machine learning models on existing data. Examples include inferring "top collaborators" for a user or suggesting relevant work items based on behavioral patterns.

See Relationships for more information.

O

Object

An object is an instance of data in Teamwork Graph. Each item—such as a Jira work item, Confluence page, or Google Drive file—is represented in Teamwork Graph as an object. Objects belong to specific object types that define their category and properties.

Object type

An object type represents a category of data in Teamwork Graph. Object types define the structure, properties, and relationships that objects of that type can have. There are two main categories: API object types (for querying data) and connector object types (for adding data via connectors).

See Object types for more information.

R

Relationship

A relationship is a connection between objects in Teamwork Graph that describes how those objects are related. Relationships are fundamental to how Teamwork Graph connects, organizes, and enables insights across Atlassian experiences. Every relationship has a type, is directional (with a "from" and "to" object), and forms part of a semantic network that can be queried.

See Relationships for more information.

T

Teamwork Graph

Teamwork Graph is Atlassian's unified data layer that connects teamwork data from across Atlassian apps, like Jira and Confluence, as well as external tools. It enables organizations to centralize their data, break down silos, and streamline workflows by providing a common data model for work items, documents, messages, users, groups, projects, and more.

See What is Teamwork Graph for more information.

Teamwork Graph API

The Teamwork Graph API is a curated GraphQL API that enables unified access to data across Atlassian apps as well as any external products and tools that have been connected to Teamwork Graph via connectors. You can use the Teamwork Graph API to query relationships and objects across Atlassian and integrated sources.

See Call the Teamwork Graph API for more information.

Teamwork Graph connector SDK

The Teamwork Graph connector SDK provides the APIs and tools you need to build connectors. The SDK includes three types of operations: object operations, user operations, and group operations.

See Connector reference overview for more information.