> For the complete documentation index, see [llms.txt](https://herd-security.gitbook.io/herd-security-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://herd-security.gitbook.io/herd-security-docs/getting-started/quickstart.md).

# Getting Started with Herd

Get started with the Herd Security Admin Console by setting up your account, connecting users and environments, and creating curated content for your organization.

## Overview

This guide will walk you through your initial login to the Herd Admin Console, as well as how to invite additional users.

## Prerequisites

To receive an **admin account** for Herd, you must first be set up by a **Herd representative**. Once your account is provisioned, you’ll have two login options:

### Option 1: Okta Single Sign-On (Recommended)

If your organization uses **Okta**, we **highly recommend** logging into Herd through [**Okta SSO**](/herd-security-docs/okta/okta-single-sign-on.md). This provides the most seamless and secure login experience. An administrator connects Okta from **Settings → General → Access → Sign-in**, with no help needed from Herd.

Assign the Okta application only to the people who should use the Herd dashboard, and set your default group before you turn SSO on — the [setup guide](/herd-security-docs/okta/okta-single-sign-on.md) explains why. Your wider workforce comes into Herd through [directory sync](/herd-security-docs/okta/okta-group-and-app-sync.md) instead.

### Option 2: AWS Cognito Login

If Okta is not available for your organization, you’ll log in using **AWS Cognito**.

A Herd representative will send you a **welcome email** from AWS Cognito. To log in, you’ll need:

* Your **Herd Organization ID** (usually your company name)
* A **temporary password** (included in the welcome email)

On your first login, you’ll be prompted to set a new password.

{% hint style="info" %}
Organizations on Microsoft can sign in with Entra ID instead. See [Microsoft Entra ID (Azure AD) SSO](/herd-security-docs/microsoft-entra-id-azure-ad/azure-ad-sso.md).
{% endhint %}

## The Get Started checklist

The first thing you'll see on the **Dashboard** is a **Get Started** card. Each step links to the page where you complete it:

1. **Review your company context** — check the company profile Herd auto-built for you.
2. **Connect Slack or Teams** — deliver trainings and phishing tests where your team already works.
3. **Connect your team directory** — sync your team automatically from Okta, Google Workspace, or Microsoft Entra.
4. **See what your team will get** — send yourself "How Herd training works" and read it where they will. This step only appears when your organization has that training.
5. **Assign your first training** — roll out your first training to your team.
6. **Allow-list simulation mail** — let Herd's phishing simulations reach inboxes instead of spam before your first campaign. This step is done only when an admin confirms the allow-list with **Mark as done** in the allow-list panel (see [Allowlisting Email Domains (Microsoft 365)](/herd-security-docs/simulations/phishing-simulations/allowlisting-email-domains-microsoft-365.md#confirm-the-allow-list-in-herd)). Admins who may confirm it can also tick it directly in the checklist.
7. **Test your report button** — report a test email with your usual button and check Herd credits it. This step only appears once Outlook or Gmail report detection is connected, and it completes itself when a test is credited (see [Detecting Phishing Reports From Outlook](/herd-security-docs/email-providers/email-providers/outlook.md#test-your-report-button)).

Steps tick themselves off as Herd detects the work is done. The directory step counts as done only once a directory is genuinely connected (Okta, Google Workspace, or Microsoft Entra ID, or SCIM provisioning that has actually been used). If you build your roster by hand instead, with CSV import or direct adds, tick the step yourself.

The card stays open on every visit to the Dashboard until all steps are complete. **Allow-list simulation mail** and **Test your report button** don't keep it open on their own: if they are the only steps left, the card stays closed, and they remain in the checklist. You can **minimize** it for the current visit, but it cannot be dismissed permanently.

## Finding your way around

The left-hand sidebar is organized in three runs, top to bottom:

* **Dashboard**, **HerdAI**, **People**, and **Reports** at the top. **People** expands into **Directory** (everyone in your organization) and **Groups**.
* **Manage** holds the things you build and run: **Training** (expanding into **Library** and **Tracks**), **Simulations** (expanding into the channels your plan includes: **Email**, **SMS**, **WhatsApp**, **Voice**), **Campaigns** (compliance campaigns), **Policies**, **Messaging** (expanding into **Announcements** and **Reminders**), and **AI Coach**.
* **Risk** holds **Intelligence** (expanding into **Risk score**, **Team risk**, and **User risk**; clicking **Intelligence** itself opens **Risk score**) and **Threat Feed**.

**Settings** sits in the sidebar footer, just above the account menu. Click your name there for **Your training** (your own assigned trainings) and **Sign out**. Rows you don't have permission for, and features your plan doesn't include, are hidden or shown locked, so your sidebar may be shorter than this list.

{% hint style="info" %}
If you knew Herd before this layout: the **Compliance** row is now **Campaigns** (same page), **Users** is now **People › Directory** with **Groups** beside it, **Team Risk** lives under **Intelligence › Team risk**, and the one-off message pages are grouped under **Messaging**.
{% endhint %}

## Set Up User Training

Herd Security sends trainings and content directly to users, helping them stay up to date with security awareness and best practices. Trainings can be delivered through your organization’s preferred communication tool:

* **Slack**
* **Microsoft Teams**

Choose the option that works best for your team during setup.

### Setting Up Slack

If your organization uses **Slack** for messaging, you can connect it to Herd Security to deliver user notifications and training content.

1. Follow the instructions in the [Slack Setup documentation](/herd-security-docs/getting-started/slack-training-setup.md) to connect the **Herd Security app** to your Slack workspace.
2. Once connected, in the Herd application, go to **Settings → Integrations** (Settings is at the bottom of the sidebar), open the **Slack** card, and click **Sync Users**. This keeps all user accounts up to date.

**Please Note**: Users will not see any messages from Herd in Slack unless they are assigned a training.

### Setting Up Teams

If your organization uses **Teams** for messaging, you can connect it to Herd Security to deliver user notifications and training content.

1. Follow the instructions in the [Teams Setup documentation](/herd-security-docs/getting-started/teams-setup.md) to connect the **Herd Security app** to your Microsoft Teams environment.
2. Once connected, go to **Settings → Integrations**, open the **Microsoft Teams** card, and click **Sync Users**. This keeps all user accounts up to date.

**Please Note**: Users will not see any messages from Herd in Microsoft Teams unless they are assigned a training.

## Congratulations! You're logged into Herd.