# Authentication

To connect the CLI with your Frontitude account, you will need to provide a valid authentication.

Choose one of the next options according to your use case:

1. Personal access token (OAuth 2.0 authentication using Google/Microsoft Azure/SAML SSO) - Use this option when you want to try the CLI or pull copy changes manually.
2. Workspace-level access token - Use this option when you want to use the CLI in your CI/CD pipeline.

## Workspace-level access token

{% hint style="info" %}
If you don't have access to your team's Frontitude workspace, you can ask one of your teammates to generate the access token and send it to you. Make sure they send it over secure channels!
{% endhint %}

Create your workspace-level access token from [your account settings](https://app.frontitude.com/settings/integrations?utm_source=dev-cli-docs), under the Developer CLI integration. Once created, continue to run the next commands in the CLI.

{% embed url="<https://frontitude-public.s3.eu-west-1.amazonaws.com/website/cli-access-token.mp4>" fullWidth="false" %}
Creating a workspace-level access token in Frontitude
{% endembed %}

To set your workspace-level access token in the CLI:

```bash
$ frontitude config set access-token <your-token>
```

To remove your workspace-level access token:

```bash
$ frontitude config del access-token
```

## Personal access token (browser sign-in)

{% hint style="info" %}
When using this option, make sure that you were invited to your team's Frontitude workspace. Otherwise you won't have access to the team's content.
{% endhint %}

Frontitude CLI supports OAuth 2.0 authentication (using Google/Microsoft Azure/SAML SSO) via your default browser to automatically generate your personal access token.

To initiate the authentication process:

```bash
$ frontitude login
```

To remove your generated personal access token:

```bash
$ frontitude logout
```