Import user attributes into Assets with email addresses
Assets is included with Service Collection Paid plans (Standard, Premium, and Enterprise). What Assets is and how it works.
You can use email addresses to import User-type attributes into Assets. When you include email addresses in your import file, Assets resolves them to the corresponding Atlassian account or customer account automatically — removing the need to manually look up account IDs.
This works for all Assets import methods: CSV, JSON, Discovery, and External Import.
Before you begin
You need import permissions for the Assets schema you're importing into.
To resolve customer (portal-only) accounts by email, the user running the import must have the Agent role in the relevant JSM project.
How email resolution works
When your import file contains email addresses in a column mapped to a User-type attribute, Assets resolves those emails through Atlassian Identity and stores the corresponding account reference.
Account type | Requirement |
|---|---|
Atlassian accounts | The target user's email privacy setting (at id.atlassian.com) must be set to Anyone or Collaborator. |
Customer / portal-only accounts | The person triggering the import must have the Agent role. |
If an email address can't be resolved (privacy setting is too restrictive, the email doesn't exist in your organisation, or the importer lacks the Agent role for customer accounts), the User attribute field is left empty for that row.
No error message will be displayed.
Import user attributes with email addresses
Prepare your import file (CSV, JSON, or Discovery export). In the column in the data source where you will store user-type attributes, enter the users' email addresses. You can mix email addresses and account IDs in the same column — each value is resolved according to its format.
In Assets, go to your object schema and open Import > Configure import.
Create or edit an import structure as you normally would.
In the attribute mapping step, map the email column to your User-type attribute.
Enable the mapping and run the import.
Assets resolves each email to the matching Atlassian account or customer account and stores the account reference.
Troubleshoot unresolved emails
If a User attribute is empty after import, check the following:
Symptom | Cause | Fix |
|---|---|---|
Atlassian account email not resolved | User's email visibility is set to Private | Ask the user to change their email privacy to Anyone or Collaborator at id.atlassian.com. |
Customer / portal-only email not resolved | Importer does not have the Agent role | Ensure the person running the import holds the Agent role on the relevant JSM project. |
Email not resolved (any type) | Email address doesn't match any account in the organisation | Verify the email is correct and that the user exists in your Atlassian organisation or customer directory. |
If you can't change a user's privacy setting, you can still import using their Atlassian Account ID or Customer ID directly. See https://support.atlassian.com/assets/docs/prepare-your-data-for-importing-into-assets/ for formatting requirements.
Was this helpful?