Service Accounts

This page explains service accounts, and the functionalities available to service accounts.

What are service accounts?

A service account is an access key token that can be generated by admins and owner, it is not considered as a person. Your systems can use service accounts to make authorized API calls, akin to a user’s BrowserStack access token.

For example, your Jenkins CI/CD pipeline can be run on BrowserStack using the service account, and that account will use the parallels assigned to the team/organization that the service account is for. This way, a user’s access keys don’t need to be shared across the organization. This way the resources and accesses available to the service account can be controlled without compromising a user’s account.

The owner gets the full view of all service accounts, and teams assigned to them. If the ownership is transferred the new owner will get access to all service accounts.

It is important to note that service account access keys are different from user access keys. Each user on BrowserStack is assigned an access key, which acts as a unique identifier and authentication token for the user. When viewing documentation on BrowserStack, the code snippets get personalized with your personal access key, and not service account’s access key.

You can create service accounts on your settings dashboard (Account>Settings).

Differences between a service account and a user account

The differences between a user account and service account are:

  • A user’s account can access product dashboards and login into the BrowserStack UI, whereas the service account does not have dashboard privileges. Service accounts do not have passwords, and cannot log in via browsers or cookies.
  • All service accounts are visible to Owners and the creator of the service account.
  • Service accounts can only be created by the Owner, Group Admin, or Team Admin.
  • Service accounts are not considered part of your user licenses.
  • Service accounts will not receive any emails like daily reports or alerts.

Similarities between a service account and a user account

  • Service accounts get access to parallels and APIs akin to a user, either as a Group User or Team User, depending upon the service account configuration.
  • Tests run by service account will be visible on product dashboards with the service account identifier being used as the user’s name.
  • Manage Data Access applies to service accounts. If the organization is on Team View, a service account which has a team assigned, will not be able to access data of other teams.

Identifier

The identifier is used to mark the service account on product dashboards and user reports.

Team

Like users, a service account can be assigned a team. All the team management access rules apply to the service account once it is part of a team.

If a team is not assigned, the service account will be considered a group level service account.

Note: BrowserStack Teams is an Enterprise feature. Learn more about Enterprise plans.

Username & Access Key

Each service account has a username and access key assigned to them. Which is used to connect your CI/CD pipelines, or access BrowserStack via APIs.

Service keys can be cycled similar to a user’s access keys, via REST APIs.

What happens to the service account when the user shifts the organization or team?

The service account is always visible to the owner of the organization. The owner can modify or delete the service account. If the organization doesn’t have any other user, then the service account and access keys are destroyed.

In case of a change of team, the service account remains part of the team assigned to it.

We're sorry to hear that. Please share your feedback so we can do better







Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked






Thank you for your valuable feedback

Is this page helping you?

Yes
No

We're sorry to hear that. Please share your feedback so we can do better







Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked






Thank you for your valuable feedback!

Talk to an Expert
Talk to an Expert