Export your Teammates and Teammate activity logs to Amazon S3, Google Cloud Storage, or Azure Blob Storage alongside your conversations data.
Scheduled data exports used to cover conversations only. You can now choose which data objects each scheduled export includes, and have teammate data delivered to your own cloud storage on the same schedule as everything else.
Use it for:
Access reviews and audit evidence — who has access to your workspace, and what changed
Security monitoring — logins, permission changes, and SSO changes in your own SIEM (security information and event management system)
Data governance and retention alongside your conversation data
What data objects can I export?
The table below describes each data object: what it contains and how frequently it exports.
Data object | Contents | How it exports |
Conversations | Conversations and their parts, including authors, assignments, tags, and custom attributes. | New and updated conversations each run |
Teammates | Every teammate in the workspace, with their name, email address, and role. | A full snapshot every run |
Teammate activity logs | A record of teammate account activity, such as logins, permission changes, and SSO changes. | New activity since the previous run |
Each data object runs as its own export on your existing schedule and delivers to the same bucket, in a separate folder per object. Runs are tracked separately, so a problem with one data object won't stop the others.
Teammate data exports as JSON or JSONL (JSON Lines — a format where each line is a separate JSON object, useful for streaming large datasets), using the same schema as the List all admins and List all activity logs endpoints of the Data API version your export is set to.
Where does exported teammate data land in my bucket?
Teammate data is written to its own folder per data object, so it never mixes with your conversation files. Your existing conversation files don't move — they stay exactly where they are today, at the root of your export folder.
Teammate data is stored in dedicated subfolders within your existing export bucket, separate from your conversation files, as shown below.
Folder | What's in it |
| Your conversation files, unchanged |
| Teammates |
| Teammate activity logs |
If you enabled Export data dated folders, the date folder sits inside the data object folder, not the other way round:
Dated folders | Example path |
Off |
|
On |
|
If you glob your conversation prefix in a downstream pipeline, that pattern keeps working unchanged and won't start picking up teammate files.
Filenames follow the same convention as conversation exports — <batch start>-<batch end>-<batch id> in UTC, with : replaced by -, and a .json or .jsonl extension matching your Output format.
How many files per run:
Teammates — one file per run, containing the whole roster.
Teammate activity logs — one or more files per run, split into batches like conversations.
The date in the folder name is the date the export ran, not the date the activity happened.
What do I need before exporting teammate data?
Permissions. You need both Manage teammates and See all teammates and team details. Without both, the teammate data objects aren't offered.
Destination. Teammate data objects are available for AWS S3, Google Cloud Storage, and Azure Blob Storage. They aren't available for Snowflake Data Share destinations.
Data API version. Teammate activity logs require a recent Data API version. Exports pinned to an older version can't include them.
How to export teammate data to cloud storage
1. Go to Settings > Data > Imports & exports > Export data and open your existing data export, or select New data export.
If you're creating a new export, follow Export conversations data to cloud storage to configure your Data API version, Output format, folder options, destination bucket, and schedule first.
2. In the Data objects section, tick the data objects you want to export. You can pick any combination.
An export needs at least one data object. The last remaining ticked checkbox is disabled — tick another data object before removing it.
3. Scroll to the bottom of the page and click Update (or Start data export for a new export).
4. A confirmation dialog appears whenever teammate data starts or stops flowing. There are two versions depending on whether you're adding or removing a data object — read the dialog and click Save changes.
When you add teammate data, the dialog confirms that it will be included from the next scheduled run, that it's personal data (names, email addresses and roles, plus account activity such as logins, permission changes and SSO changes), and that it's written to storage you control — so Intercom can't recall or delete it after it's exported.
When you remove a data object, the dialog explains what you can recover:
Teammate activity logs — if you turn them back on within a few days, the next export catches up. After that, only a historical export requested from Intercom can fill the gap.
Teammates — every run exports the full roster, so turning it back on restores the complete data with no permanent gap.
A save that both adds and removes data objects shows a single dialog covering both. Clicking Cancel sends nothing and leaves your unsaved selection on screen. Once you've saved teammate data objects you won't be prompted again for unrelated changes, such as switching Output format.
5. After the next scheduled run, check your bucket. Teammate data appears under its own folder per data object — admins/ and admin_activity_logs/.
6. To confirm an export ran, go back to Settings > Data > Imports & exports > Export data and check the Runs tab. Each row is labelled by its data object — Conversations, Teammates, or Teammate activity logs.
7. To see who changed your export configuration and when, go to Settings > Workspace > Teammates > activity log and filter to the data export events. Entries record which data objects were involved. Events recorded before this feature shipped keep their original wording, without data objects.
8. To stop exporting teammate data, untick the data objects, click Update, and confirm. Deleting the whole export removes the configuration but won't delete files already written to your bucket.
What are the current limitations?
The following limitations apply to teammate and activity log data exports to cloud storage.
Intercom can't delete exported files. Once data is written to your bucket, Intercom can only write to it — it cannot read or delete from it. Erasure requests can't propagate to exported files, so removing a teammate's data from files already in your bucket is your responsibility. This is the same as existing conversation exports.
Teammates is a full snapshot, not a delta. Every run exports your whole roster in a single file. There's no incremental or changed-only mode, and no per-teammate or date-range filtering.
No self-serve historical export for teammate data. Unlike conversations, there's no two-year backfill option — teammate data starts flowing from the next scheduled run after you enable it. If you need earlier activity, contact Support and Intercom can run a historical export for you.
At least one data object is required. You can't leave an export with nothing ticked.
Teammate activity logs need a recent Data API version. Exports pinned to an older version can't include them.
Some activity is anonymised. Where an action was performed by an account that's no longer on your workspace's teammate list, the actor's ID and IP address aren't included. Activity log metadata is limited to a curated set of fields, so an exported activity log can contain less detail than the same record from the Data API.
One workspace per bucket. As with conversations, you can't export multiple workspaces to the same bucket.
Troubleshooting
If something looks wrong in your export configuration or run history, use the table below to diagnose it.
What you see | What it means |
Teammate checkboxes are missing, but Conversations shows | You're likely missing Manage teammates and/or See all teammates and team details. |
A checkbox is greyed out and won't untick | It's the last remaining data object. Tick another one first. |
A checkbox is ticked and greyed out | The export already includes that data object, but it can't be changed here — your permissions or the export's Data API version changed after it was set up. Ask a teammate with full teammate permissions, or contact Support. |
"You need permission to manage teammates and to see all teammates and team details…" | You don't have both required permissions. An admin can grant them in Settings > Teammates. |
"Refresh the page to see the object types available…" | The available data objects changed since the page loaded, usually a Data API version that can't serve activity logs. Refresh and try again, then contact Support if it persists. |
A run appears in the Runs tab but no file lands in your bucket | Usually bucket permissions. Re-run the Test button on your destination, then contact Support. |
Some activity log rows have no actor, or empty metadata | Expected — the teammate who performed the action is no longer on your workspace's roster. |
Exported metadata differs from | Expected — exports use a stricter, curated set of metadata fields than the API response. |
You missed a window and need it backfilled | Contact Support — Intercom can run a historical export of your teammate and activity log data. |
Related articles
Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts