# Getting started

Ladon alerts your team when a vulnerability affects software you run: WordPress core, plugins and themes, open-source packages and public GitHub repositories. This guide takes you from a new account to your first alert in a few minutes.

## 1. Create an account

Ladon uses your HackIndex account, the same account for every HackIndex service. Sign up with an email address and password, or with Google, GitHub or GitLab. Confirm your email address and accept the terms.

Every account comes with a personal team. Working with colleagues or clients? Create a team for your organisation and invite people in your [account settings](https://account.hackindex.io/settings/teams). Everything in Ladon belongs to a team, and inside the team to a project.

## 2. Open Ladon

Open the [dashboard](https://ladon.hackindex.io/dashboard). The first time, Ladon asks you to accept its additional terms. They explain what an alert is and what you may do with the vulnerability data.

## 3. Watch your first software

Everything you watch lives in a project, and so do its alerts, CVE rules and channels. Use one project per client, app or group of sites.

1. Open your team, choose **Add** and then **Add project**. Give it a name and save.
2. In the project choose **Add to project**. Pick **Lockfile** and drop one or more lockfiles such as `package-lock.json`, `composer.lock`, `poetry.lock`, `Gemfile.lock`, `Cargo.lock`, `go.mod` or `gradle.lockfile`, and Ladon watches every package in them. On the paid plans you can pick a **GitHub repository** instead, and Ladon reads every lockfile from there and keeps them up to date.
3. Or add software by hand with **Add to project**: a plugin, a theme or WordPress itself, or common software such as PHP, nginx or Apache.
4. Choose the versions your sites run: all versions, or only the ones you use, such as `>=6.4 <7.0`.
5. Choose **Add to project**.

On the right you already see the known vulnerabilities for that software, how many affect the versions you chose and how many have no fix in the newest version. Read more in [Projects and lockfiles](https://ladon.hackindex.io/docs/projects.md) and [Watching software](https://ladon.hackindex.io/docs/watches.md).

Want to hear about new CVEs in general, also for software you do not run yet? Add a rule on the **CVE Monitor** tab of the project, for example every critical CVE that is not about routers, see [CVE rules](https://ladon.hackindex.io/docs/cve-rules.md).

## 4. Add a channel

Every alert shows up on the **Alerts** tab of the project. To also get them elsewhere, open **Channels** in the project and choose **Add channel**. The channel decides which alerts it sends, with its own event types and severity filter, and only gets the alerts of its own project:

- **Email** (paid plans): add one or more addresses. Every recipient confirms with a link first.
- **Webhook**: Ladon sends signed JSON to your own endpoint. The endpoint first proves it is yours by answering a challenge.
- **Slack, Discord or Microsoft Teams**: connect a channel of your chat app, on every plan. Discord only gets [CVE rule](https://ladon.hackindex.io/docs/cve-rules.md) alerts.

Send a test message from the channel page to see what arrives. Read more in [Channels](https://ladon.hackindex.io/docs/channels.md) and [Webhooks](https://ladon.hackindex.io/docs/webhooks.md).

## Next steps

- See every event and its payload in [Events and payloads](https://ladon.hackindex.io/docs/events.md).
- Require two-factor authentication for your team in [Teams and security](https://ladon.hackindex.io/docs/teams-and-security.md).
- Check what your plan includes in [Plans and limits](https://ladon.hackindex.io/docs/plans-and-limits.md).
