> For the complete documentation index, see [llms.txt](https://docs.cortex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cortex.io/get-started/quickstart/getting-started-logging-in-to-cortex-and-configuring-your-workspace.md).

# Getting started: Logging in to Cortex and configuring your workspace

This article walks through logging in to Cortex for the first time. It also includes additional information for admins on how to configure the Cortex workspace.

## Logging in to Cortex

{% hint style="info" %}
On-prem users log in through their organization's unique URL, e.g.  `https://app.cortex.your-org-name.com`. Check with your Cortex admin if you don't know your URL.
{% endhint %}

Follow the steps below to log in to Cortex Cloud. 

1. Go to the Cortex login page:
   1. US environment - <https://app.getcortexapp.com/login>
   2. EU environment - <https://app.eu.cortex.io/login>
2. Enter your workspace name, then click **Sign in**.

When you first log in to your Cortex workspace, you are prompted through the steps of configuring your account and connecting data. See the video below for a demonstration:

{% embed url="<https://www.youtube.com/watch?v=yT6Ka0y_r80>" %}

{% hint style="info" %}
Once Cortex detects a user's workspace, it automatically redirects them to their SSO provider and preserves any deep links, so they land exactly where they intended without any extra steps.
{% endhint %}

### Session timeouts

Cortex sessions expire after **7 days of inactivity**. Inactivity is defined as not having made a request in the past 7 days. Active usage resets the timer, so users only need to re-authenticate after a continuous period without activity.

**How it works**

When a user authenticates, Cortex creates a session that remains active as long as the user continues to make requests. After 7 days without activity, the session expires and the user must re-authenticate.

This behavior is the same for both Cloud and On-Prem deployments. The only difference between the two is the authentication method:

* **Cloud** (US and EU) - Authentication goes through Auth0 + OIDC.
* **On-Prem** - Authentication uses OIDC directly.

**Logging out**

When a user logs out from the UI, Cortex clears the session and cookie, then redirects them to the login page.

{% hint style="info" %}
The session timeout is a global configuration value and cannot currently be customized per tenant.
{% endhint %}

## For Cortex Admins

Users with the `Admin` role have full access to everything in Cortex, from customizing the organization's workspace and setting up SSO to managing users and configuring entities. This section covers the essentials for getting your workspace set up and ready for your team.

{% hint style="info" %}
Access your Cortex workspace using the workspace ID provided to you by the Cortex team. If you are deploying Cortex on-premises, the Cortex team will provide you with access to an installer.
{% endhint %}

### Setting up SSO

Your initial login is configured to use Google for Single Sign-On (SSO).

If you do not use a Google domain email address, contact the Cortex team at <help@cortex.io> to discuss initial access and [configuring an alternate SSO provider](/configure/settings/managing-users/configuring-sso.md).

### Customizing the look of your workspace

A few quick tweaks to your workspace can help make it feel like part of your company's toolkit. Head to general settings to upload your logo, set a workspace name, and choose a brand color. See [Customizing your workspace](/configure/settings/workspace-customization.md) for more information.

### Adding users to your workspace

With your account set up, you're ready to bring your team into Cortex. You can invite users one at a time or in bulk, and assign each person a role that reflects the level of access they need. See [Roles and permissions](/configure/settings/managing-users/permissioning.md) for more information.

Before you start inviting the broader team, it's strongly recommended to configure at least two users with the `Admin` role. Having a second admin ensures redundancy of access: if one admin is out of office, changes roles, or leaves the organization, you'll always have someone who can manage Cortex.

### Additional resources

Go further with your initial setup! We recommend reviewing the following resources:

* [Onboarding management](/configure/settings/managing-users/onboarding-mgmt.md) - Stay informed about user onboarding statuses.
* [IP allowlist](/configure/settings/ip-allowlist.md) - Use the IP allowlist to restrict which networks can access your Cortex workspace.
* [Workspace settings](/configure/settings.md) - Further customize your Cortex workspace and view audit logs.