---
title: "Clarity Getting Started Guide"
slug: "getting-started-step-1"
description: "The first step in setting up Clarity is to get some data into your tenant. Clarity relies on this to provide the data necessary for Clarity to function."
tags: ["application", "Application Connectors", "Application Marketplace", "connectors", "Getting started", "tutorial"]
updated: 2026-06-16T18:49:43Z
published: 2026-06-16T18:49:43Z
canonical: "help.claritysecurity.com/getting-started-step-1"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.claritysecurity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Step 1: Connect to your Applications

The first step in setting up Clarity is to get some data into your tenant. Clarity relies on Downstream Applications to provide the data necessary for Clarity to function.

In this section, you will perform the following actions:

1. Determine your list of Downstream Applications.
2. Connect to your Source of Truth application(s).
3. Connect any other applications already available in our [Integrations Marketplace](https://claritysecurity.com/platform/supported-integrations).

---

## Determine your list of applications

When configuring your system, you will want to compile a list of Applications or Databases you want to manage through Clarity. You will want to begin by connecting a Source of Truth that contains the most complete user information for your institution. You can then add further Downstream Applications to manage.

---

### Connecting your Source of Truth Applications

A good place to start when connecting your applications, is with the applications that will act as a Source of Truth. These applications will create an Identity for any active Service Users found, which will help reduce alerts for any future applications that you connect. An Identity in Clarity functions as a container that includes matched Service Users and their corresponding data (Attributes and Entitlements).

The first thing to consider is which applications accurately represent your organization's complete list of users. These typically include your Human Resources (HR) platform, Active Directory (on-prem or cloud), and Identity Management services.

**Common Sources of Truth**:

- HR Platform
  - ADP
  - BambooHR
  - Zenefits
- Active Directory
  - Azure Active Directory (cloud)
  - Microsoft Active Directory (on-prem)
- Authentication Services
  - Okta
  - Azure AD

---

### Connecting your other Applications

Next, you will want to determine which SaaS applications your organization uses and would like to manage using Clarity. The type and number of applications or databases you connect to your Clarity tenant will vary greatly upon your organization's needs.

**Examples of commonly Connected Apps:**

- SQL Database
- Zendesk
- Github
- Zoom

To see the full list of applications that Clarity Security supports, you can search our Knowledge Base (where you are right now) for the application name, or head directly to our [Integrations Marketplace](https://claritysecurity.com/platform/supported-integrations) for a listing of our currently supported apps, and configuration steps.

Note

If you do not see an application you use on the currently supported Applications, please reach out to Clarity Support via the information below with an Enhancement Request.

## Up Next: Using attributes of describe your Identities

In the next section of our Getting Started guide, we will use the data collected from your Downstream Applications you have connectioned, especially your Sources of Truth.

[Step 2: Establish Identity Attributes](/v1/docs/getting-started-step-2)

---

## Need help?

If you have any problems, contact your customer success team. You can also get in touch with our general support [via email](mailto:support@claritysecurity.io), open a [support ticket](https://support.claritysecurity.com/home). Our general support team is available Monday - Friday from 8:00 AM - 6:30 PM CST.

A Downstream Application is any application that supplies Clarity with service users, entitlements, and attributes.

An identity is a single entity's (employee, contractor, service account) grouping of service users, attributes, and assigned entitlements.

A Service User is a user, or service account, discovered by Clarity in a downstream application.

An attribute is a piece of information used to describe a service user, entitlement, or identity. Common examples include First Name, Last Name, Job Title, Department, etc.

An Entitlement is an assignable permission found in a downstream application. Common examples include licenses, groups, and policies.