# Generate access token
{% hint style="info" %}
**Only users with administration rights can generate access tokens.**
{% endhint %}
Access tokens are a secure way of performing automated integrations with OpenText Core SCA. They are safer compared to using a username and password, and their typical use cases include GitLab, Bitbucket, and API integrations, which are not tied to a particular user, but rather to a repository or a project.
To generate a new access token:
1. Go to **Admin tools** on the left side menu.
2. Type your password to go to administrative mode.
3. In the **Access Tokens** tab, click the **+Create** button.
4. Type the description. If needed, select the **Admin** box which gives access to more actions, such as performing scans.
5. Click **Generate.**
6. Copy the generated token.
To generate a new access token for an Enterprise:
1. Go to **Admin tools** on the left side menu.
2. Type your password to go to administrative mode.
3. In the Access token tab, click the **+Create** button.
4. Type the description.
5. Select the repositories and user roles from the drop-down.
6. Click **Generate**.
7. Copy the generated token.
{% hint style="info" %}
**Save the token before closing the window as you can only view this token once.**
{% endhint %}
### Export access token details
You can export the filtered and visible access token details in the table to a CSV file. To do so, click **Export Table** located at the top-right corner of the table. *For more information, refer to the* [*Export table data*](https://docs.debricked.com/product/administration/repositories/export-table-data) *topic.*
### Token access scope
#### Freemium & Premium
For 'Freemium' and 'Premium' accounts, the following two access scopes are available:
* Admin tokens - Always give access to all repositories, both already existing and those created in the future.
* User tokens - When creating a token, the new token gets **User** access (equivalent to [Reviewer in RBAC](https://docs.debricked.com/product/users/role-based-access-control-enterprise#userroles)) to every existing repository at the time of token creation.
#### Enterprise (with Role-Based Access Control (RBAC))
For Enterprise accounts, the access scope of access tokens can be configured granularly with different scopes for individual repositories. The access granted by the various scopes is equivalent to that provided by our RBAC user roles.
For repositories created or integrated after the generation of the token, access will be based on the default role, which can be configured by a company admin.
*For more information on the available user roles, their access and how to set the default role, see* [*Role-Based Access Control (Enterprise)*](https://docs.debricked.com/product/administration/users/role-based-access-control-enterprise)*.*
