1. DataSync Service Account
This is a dedicated Spira user that the sync engine uses to authenticate with Spira's API. It's needed regardless of whether you use the Cloud, On-premises, or Desktop datasync option.
Credential Details
Spira Login (username): A dedicated service account user in Spira (e.g., "DataSyncService")
Spira Password: The password for that service account
Where it’s entered
Cloud Spira DataSync: Inflectra Customer Area > My Cloud Subscriptions > Configure (the Spira DataSync row)
On-premises Windows Service: DataSyncService.exe.config XML file (Login & Password fields)
Desktop DataSync app: The app's UI (Username & Password fields), then click "Test"and click "Update" to apply the changes
Required memberships for the DataSync Service Account
Must be an active user in Spira with login access
Must be explicitly added as a member of every Spira product you want to sync
Must have a Product Role with permissions to view, create, and modify all synced artifact types (Incidents, Requirements, Tasks, Releases, Documents)
Does NOT need to be a System Administrator
2. Inflectra Customer Area Login (Cloud DataSync Only)
Credential Details
Required access
Must be an authorized billing or technical administrator for your Inflectra subscription
Used to add the Spira DataSync feature and configure it in "My Cloud Subscriptions"
This is NOT a Spira login — it's your inflectra.com Customer Area login
3. Spira System Administrator
Credential Details
Used for
Configuring the JiraDataSync plugin settings (System Administration > Integrations > Data Synchronization)
Setting up user mappings (Administration > Users > View Edit Users)
Activating the datasync per product and configuring all field mappings
Required memberships
4. Jira Cloud Account
Credential Details
Jira Login: Atlassian email address (e.g., admin@yourcompany.com)
Jira API Key: An Atlassian API Token (generated at id.atlassian.com > Security > API tokens) — NOT a password
Where it’s entered
In Spira: the JiraDataSync plugin configuration page (Jira URL, Jira Login, Jira API Key fields)
In the Jira Configuration Helper desktop app (same URL + Login + API Key)
Required project memberships in Jira
The Jira account must have permissions to create and view issues and versions in the Jira project(s) being synced
Typically needs at least a project role equivalent to "Developer" or higher in each synced Jira project
Must be able to read all issue types, statuses, priorities, custom fields, and versions
5. Mapped Users
These aren't "configuration credentials" but they affect how data appears after sync.
Mode Details
Auto-map (recommended): Auto-map works by email address. The requirement is that the user has the same email address registered in both systems
Manual mapping: For each Spira user, a Jira account ID or Jira user email address is entered in their Spira profile (Administration > Users > Edit > Membership and Mapping >Data Mapping tab)
Required memberships for mapped users
In Spira: Each mapped user should be a member of the synced product(s) so that artifact assignments display correctly
In Jira: Each mapped user should be a member of the synced Jira project(s) so assignments can be written back
Note: The datasync does NOT create users in either system. It only maps existing ones.
Account summary
| # | Account Type | Needed For | Key Membership Requirement(s) |
| 1 | DataSync Service Account (Spira user) | Sync engine authenticates to Spira | Member of every synced product with create/modify permissions on all artifact types |
| 2 | Inflectra Customer Area admin (inflectra.com account) | Adding & configuring Cloud datasync | Authorized billing/tech admin on the subscription |
| 3 | Spira System Admin (Spira user) | Configuring the plugin, field mappings, user mappings | System Administrator role |
| 4 | Jira account (Atlassian user) | Plugin connection to Jira also used in Jira Configuration Helper app | Project-level permissions (required on each synced Jira project): Global/site-level permissions: |
| 5 | Mapped users (both sides) Spira and Jira | Correct attribution of who did what | Members of the respective products/projects on both sides |