# Initial configuration

> Complete first-time setup—core preferences, licensing, users, and your first project—then validate the installation with a test run.

Source: https://totalshiftleft.ai/help-center/configuration/initial-configuration


## Overview

Once Shift-Left API is installed (Cloud or self-hosted), a quick initial setup ensures your environment is ready for smooth test creation, execution, and collaboration.

If you haven’t installed yet, start with [Getting started](/help-center/installation/getting-started).

## Step 1: Launch Studio

Launch **Shift-Left Studio** from the **Desktop shortcut** (Shift-Left Studio) or from the **Start Menu**.

## First Launch & Account Setup

On first launch, you will need to create an administrator account. The first screen will prompt you to create your administrator account. Click **Create your administrator account**.

![Shift-Left Studio – Sign in screen, Create your administrator account](/images/help-center/configuration/create-administrator-account.png)

![Shift-Left Studio – Sign in screen (alternate view)](/images/help-center/configuration/create-administrator-account-additional.png)

Once you click **Create your administrator account**, the form opens as below:

![Create your administrator account – Full Name, Email, Password form](/images/help-center/configuration/create-administrator-account-form.png)

Fill in your full name, email address, and choose a password for the administrator account. After entering your details, click the **Create Administrator Account** button.

Congratulations — you've successfully created your administrator account. You'll see a success screen like the one below. You'll be redirected to the login screen automatically in a few seconds, or you can click **Back to Login** to sign in right away.

![Administrator account created successfully – success screen, redirect countdown](/images/help-center/configuration/create-administrator-account-success.png)

## Step 2: Logging In

On the login page, enter the **email address** and **password** you used to create the administrator account. Click **Sign in** to log in.

![Sign in to your account – Email, Password, Sign in button](/images/help-center/configuration/sign-in.png)

## Step 3: Activate your license

Once you log in, you'll see the **License Issue Detected** screen. Click **Manage License** and enter the license key you received via email when you signed up. You can also reach out to your Customer Success Manager or contact Support at [support@totalshiftleft.com](mailto:support@totalshiftleft.com).

![License Issue Detected – Manage License, enter license key](/images/help-center/configuration/license-issue-detected.png)

Related platform documentation: [License Management](/help-center/product-documentation/license-management).

## Step 4: Add users

Invite your team members so work can happen in parallel:

- Go to [**User Management**](/help-center/product-documentation/user-management) → Add New User
- Assign roles (for example **Admin**, **Tester**, **Viewer**) based on responsibilities
- Restrict access by project/workspace where appropriate

Related platform documentation: [User Management](/help-center/product-documentation/user-management), [Role Permissions](/help-center/product-documentation/role-permissions), and [User Policies](/help-center/product-documentation/user-policies).

## Step 5: Add your first project

Create a project that represents an API you want to test:

- Click **New Project** and provide a name + short description
- Define the **API base URL** for the target environment (Dev/QA/Staging/Prod)
- Choose an authentication approach (API key, OAuth/Bearer token, etc.)
- Add endpoints manually or import via **OpenAPI/Swagger**

If you’re setting up multiple environments, keep them separate (dev vs staging vs prod) so failures are easier to interpret.

Related platform documentation: [Project](/help-center/product-documentation/project), [Managing projects](/help-center/product-documentation/managing-projects).

## Quick tip: set up RBAC early

For larger teams or multi-project environments, configure role-based access control early so permissions stay clear and auditable as the workspace grows.

## What to read next

- [Project](/help-center/product-documentation/project) (how projects are organized)
- [Endpoint management](/help-center/product-documentation/endpoint-management) (import vs manual)
- [Test run](/help-center/product-documentation/test-run) (execution and outcomes)