Understand service accounts
Who can do this? |
Which user management experience do you have?
Go to Atlassian Administration. Select your organization if you have more than one. You can identify which user management experience you have by checking where your Users page is located.
Centralized | Original |
|---|---|
In Atlassian Administration, Users is located in Directory. | In Atlassian Administration, Users is located in Apps > |
Centralized user management content
Atlassian organizations bring together your company’s users and apps. As an organization admin, you manage the Atlassian accounts of your employees and the apps that belong to your organization.
Service accounts allow you to manage the identities of services, integrations, and apps for your Atlassian organization.
What is a service account?
A service account is an account that is not associated with a person. This means it doesn’t need to a password to log in to your Atlassian organization.
Manage a service account lifecycle the same way you manage a user account. You can create and edit the account. You can also give the account app permissions, edit the details of the service account profile, and create credentials for the service account.
Available tiers for service accounts
We provide your organization with 5 free single service account to automate tasks or integrate apps. If you need additional service accounts to run more integrations, you can upgrade to Atlassian Guard Standard, which offers up to 250 service accounts.
For enterprise customers, the enterprise subscription plan allows you to add up to 1,000 service accounts, along with priority support, custom integrations, and service level agreements (SLAs).
App user count does not include service accounts
When you grant a service account access to Jira or Confluence, they do not count towards your user limit. This means we don’t charge your Jira or Confluence subscription plan for service accounts.
How to create a service account
You’re able to create a service account in Atlassian administration. You’re unable to provision service accounts from your identity provider. When you provide the service account with a name and description, we generate a unique account ID and service account email. After you create a service account, you can’t change the account email.
You can assign app permissions to service accounts based on the app you select.
To create a service account:
Go to Atlassian administration. Select your organization if you have more than one.
Select Directory> Service accounts.
Select Create a service account.
For service account name, enter alphanumeric Name with 6 to 30 characters.
For the optional Description, enter the name of a person or app that uses the account.
Select roles for the apps that the service account needs to access. You can also add the service account to a group.
Select Create.
After you create a service account, you can create a credential for the service account. You can either create an:
API token for the service account
OAuth 2.0 credential
Edit service accounts
You’re able to edit the name and the description for your service account.
To edit a service account:
Go to Atlassian administration. Select your organization if you have more than one.
Select Directory> Service accounts.
Select a service account you’d like to edit.
Select Edit details.
Edit the service account name and description and select Save.
Delete service accounts
When you delete a service account, this means the service account can no longer access any apps. We also delete the credentials associated with this service account.
To delete a service account:
Go to Atlassian administration. Select your organization if you have more than one.
Select Directory> Service accounts.
Select Actions for the service account you’d like to delete.
Select Delete service account.
Monitor API token usage for service accounts
Monitor the recent usage of the API token associated with a service account from a central location. You can see how many active tokens exist, when they were created, when they expire, and the last time the token was used by the service account.
To view API tokens:
Go to Atlassian administration. Select your organization if you have more than one.
Select Directory> Service accounts.
Select Action for the service account.
Select View API tokens.
Original user management content
Atlassian organizations bring together your company’s users and apps. As an organization admin, you manage the Atlassian accounts of your employees and the apps that belong to your organization.
Service accounts allow you to manage the identities of services, integrations, and apps for your Atlassian organization.
What is a service account?
A service account is an account that is not associated with a person. This means it doesn’t need to a password to log in to your Atlassian organization.
Manage a service account lifecycle the same way you manage a user account. You can create and edit the account. You can also give the account app permissions, edit the details of the service account profile, and create credentials for the service account.
Available tiers for service accounts
We provide your organization with 5 free single service account to automate tasks or integrate apps. If you need additional service accounts to run more integrations, you can upgrade to Atlassian Guard Standard, which offers up to 250 service accounts.
For enterprise customers, the enterprise subscription plan allows you to add up to 1,000 service accounts, along with priority support, custom integrations, and service level agreements (SLAs).
App user count does not include service accounts
When you grant a service account access to Jira or Confluence, they do not count towards your user limit. This means we don’t charge your Jira or Confluence subscription plan for service accounts.
How to create a service account
You’re able to create a service account in Atlassian administration. You’re unable to provision service accounts from your identity provider. When you provide the service account with a name and description, we generate a unique account ID and service account email. After you create a service account, you can’t change the account email.
You can assign app permissions to service accounts based on the app you select.
To create a service account:
Go to Atlassian administration. Select your organization if you have more than one.
Select Directory> Service accounts.
Select Create a service account.
For service account name, enter alphanumeric Name with 6 to 30 characters.
For the optional Description, enter the name of a person or app that uses the account.
Select roles for the apps that the service account needs to access.
Select Create.
After you create a service account, you can create an API token for the service account.
To add a service account to a group:
Go to Atlassian administration. Select your organization if you have more than one.
Select Directory> Service accounts.
Select the service account you want to add to a group.
Select Apps to make sure you assigned the service account to an app.
For the service account, select the (…) action and add it to a group.
Edit service accounts
You’re able to edit the name and the description for your service account.
To edit a service account:
Go to Atlassian administration. Select your organization if you have more than one.
Select Directory> Service accounts.
Select a service account you’d like to edit.
Select Edit details.
Edit the service account name and description and select Save.
Delete service accounts
When you delete a service account, this means the service account can no longer access any apps. We also delete the credentials associated with this service account.
To delete a service account:
Go to Atlassian administration. Select your organization if you have more than one.
Select Directory> Service accounts.
Select Actions for the service account you’d like to delete.
Select Delete service account.
Monitor API token usage for service accounts
Monitor the recent usage of the API token associated with a service account from a central location. You can see how many active tokens exist, when they were created, when they expire, and the last time the token was used by the service account.
To view API tokens:
Go to Atlassian administration. Select your organization if you have more than one.
Select Directory> Service accounts.
Select Action for the service account.
Select View API tokens.
Was this helpful?