We’re introducing a new way to use Atlassian Strategy Collection with any HR information system (HRIS)! The new universal HRIS connector in Talent lets you bring your positions, people, and organization structure into Atlassian using CSV files stored securely in Amazon S3.
To unlock Strategy Collection for more customers and more use cases, we needed a vendor‑agnostic way to bring position and people data into Atlassian.
That’s why universal HRIS connector is generally available today! Every Strategy Collection customer can now get:
Make the right investment decisions with up-to-date and accurate headcount mapped to your strategic priorities
Secure by design: Bring HR data into Strategy Collection with full control of what’s shared, who has access, and how often you update your data
Fast, low-friction onboarding: All you need are CSV exports in an S3 bucket, with no need for a specific third-party connector
Under the hood, your HR data lands in Atlassian’s Teamwork Graph, so the whole platform can use a single, consistent and accurate source of truth.
This data is key for successful strategic planning and portfolio management. When you connect people to your strategic priorities, you get timely signals to accelerate, reallocate, and pivot at the right time and deliver your most critical initiatives. Read more on this approach here.
The universal HRIS connector securely reads CSV files from your S3 bucket and writes that data into the Atlassian Teamwork Graph. Get started with our documentation here.
At a high level:
You provide a CSV file for your HR data from one or multiple sources
You configure the connector in Atlassian administration:
Point it at the S3 file paths for each CSV
Provide an identity access management (IAM) role the connector can assume to read those files
The connector auto-ingests your data and updates:
Reads the CSV from your S3 bucket
Writes the data into the Teamwork Graph
Makes it available to Strategy Collection and Atlassian apps
Many organizations keep different types of workers in different systems of record. With the new connector, you can:
Export data from one or multiple HR systems
Normalize those exports into a CSV (on your side)
Feed them into a single, consistent HR dataset in Atlassian
Who sets up the connector?
Typically, an Atlassian org admin or IT administrator sets up the connector, in partnership with whoever owns your HR system. You’ll need someone who can:
Export CSVs from your HR system(s), and
Configure an IAM role and S3 bucket
What permissions are required in AWS?
You’ll create an IAM role that the connector can assume with read-only access to the S3 paths where your CSVs live. You stay in control of:
Which buckets and paths are accessible
What data is exported into those CSVs
Can we use multiple HR systems?
Yes. You can export data from multiple HR systems and combine or normalize those exports into a CSV before it lands in S3.
Today, the connector expects one CSV per entity type (positions, workers, org structure). As long as your combined CSVs are clean and de‑duplicated, the connector doesn’t care how many systems they came from.
How often does the data update?
Once connected, imports run on a scheduled cadence every six hours. You can update your CSVs in S3 and the connector will pull in changes automatically on the next run. You also have an option to manually initiate a sync in case a change needs to be pulled in sooner.
George Thomas Valooran
3 comments