> For the complete documentation index, see [llms.txt](https://docs.sealsecurity.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealsecurity.io/step-by-step-onboarding-guides/python_pip-no_scm-snyk-github_actions-cli_local-keep_names.md).

# Step-by-Step Setup Guide

This guide walks you through the initial account setup, token generation, and connecting your first project to Seal Security.

## Account Creation & Token Generation

Follow these steps to access the platform and prepare your environment. If you already have a token, you can skip to the next section.

1. **Access the Invite:** Click on the **Sign in >** button in the Seal Security invite email you received.
2. **Log In:** Log in to the platform using your password or social login credentials.
3. **Start Onboarding:** We're starting the onboarding flow. Click **Next >** to begin.
4. **Generate Token:** First, you must generate a token to Seal's artifact server. This allows you to download our sealed versions.\
   ![Generate Token](/files/PavZ4q5NrXJse1vkrR0Y)
   1. **Generate:** Click on **Generate token**.
   2. **Copy:** Copy the newly generated token using the copy icon at the right of the text box.

      > **Important:** You will need this token later. While it should eventually be saved in a secure location (like a password manager or secret store), copy it now for immediate use in the next steps.
   3. **Continue:** Click **Next >**.
5. Click **Maybe later** to skip the GitHub integration.
6. **View Protection page:** You will land on the Protection screen.
   * **Status:** Since no projects are connected yet, we are not showing any results.
   * **Next Step:** We are now going to populate this data using the CLI. ![Empty Protection page](/files/Fgf0cjrcjNzbEzFu4thb)

## Integrate the Seal CLI

To start fixing vulnerabilities (and populate the Protection page), you must integrate the CLI into your build pipeline.

**The Golden Rule:** In all cases, the CLI step must be added **immediately after** dependencies are pulled/installed (from standard registries or your artifact server) but before the final build/compilation.

**Important Configuration:** For all integration methods, you must ensure the following environment variables are set:

* `SEAL_TOKEN`: The token you generated earlier.
* `SEAL_PROJECT`: The ID of your project on the Seal platform (e.g., "my-first-project").

Identify the location of your build pipeline. Typically, this is a `.github/workflows/workflow.yaml` in your repository.

In the pipeline, identify the step where dependencies are installed (e.g., `pip install -r requirements.txt`).

Identify the location of the `requirements.txt` file.

Add the seal fix command:

```yaml
- run: pip install -r requirements.txt
- name: Run Seal Fix
  uses: seal-community/cli-action@latest
  with:
    mode: fix
    fix_mode: local
    target: requirements.txt
    project: my-first-project
    token: ${{ secrets.SEAL_TOKEN }}
  env:
# Snyk integration
    SEAL_SNYK_URL: "https://api.snyk.io"
    SEAL_SNYK_TOKEN: ${SNYK_TOKEN}
    SEAL_SNYK_ORG_ID: ${SNYK_ORG_ID}
    SEAL_SNYK_PROJECT_ID: ${SNYK_PROJECT_ID}
```

## Sealing a package

Once you have integrated the CLI into your pipeline, follow these steps to see the results.