You must only install apps that call the Teamwork Graph API in test organizations. Apps calling the Teamwork Graph API require the read:graph:jiraor read:graph:confluence scope, which provides access to Teamwork Graph data across your entire organization. While apps still respect end-user permissions, this scope may grant access to sensitive information. For safety, only install these apps in organizations with test data unless you have an approved path to production.

Additionally, this EAP has significant limitations. To review the full list of limitations, see Limitations and considerations.

You must be part of this EAP in order to use the Teamwork Graph API. Express interest in joining through this form.

An individual that been, currently is, or previously employed/contracted by an organization to fill a specific role.

Available fields and properties

The Teamwork Graph API has the following fields and properties that you can use in your queries:

Object type fields are the core data fields of the object. Use these when you want to retrieve specific information about the object in your queries.
Cypher query properties are metadata properties used for filtering and traversing relationships between different object types in Teamwork Graph. Use Cypher query properties when you need to filter or navigate relationships between this object and other objects in your queries.

Object type fields

You can access these fields in the GraphiQL playground using the book icon in the top left, and then searching for Talent worker.

Field	Type	Description
`id`	`ID!`	The unique Atlassian Resource Identifier (ARI) for this worker.
`preferredName`	`String`	The preferred name of the worker.
`type`	`TalentEntityType!`	The type of entity.
`user`	`User`	The Atlassian user associated with this worker.

Values for TalentEntityType

Value	Description
`FOCUS_AREA`
`FOCUS_AREA_TYPE`
`POSITION`
`PROPOSAL`
`PROPOSED_MOVEMENT`
`TEAM`
`VIEW`
`WORKER`