# User guide

> What Proteside does, the core concepts and how the dashboard is organized.

URL: https://docs.proteside.com/en/docs/guide

Proteside protects your store's payment pages against malicious scripts. It detects skimming (the theft of card data
by a script hidden in the checkout) and payment tampering, such as swapping the Pix key or the boleto barcode. From
what it observes, it builds the evidence you present in your PCI DSS 4.0 assessment, requirements 6.4.3 and 11.6.1.

This guide shows how to use the dashboard day to day, from your first sign-in to the report for your auditor.

> **Evidence, not certification**
>
> Proteside gathers evidence for requirements 6.4.3 and 11.6.1, but it doesn't certify your store. The dashboard itself
> says so: "not a compliance certification". Compliance is assessed by your QSA or your compliance team.

## How it works
You paste a small piece of code, the **snippet**, into the `<head>` of your checkout pages. It loads the Proteside
**SDK** in each customer's browser. The SDK watches the scripts that run on the page, the forms and the payment data
displayed, and sends what it sees to the dashboard. The SDK doesn't read what the customer types and doesn't send card numbers, CVVs or Pix keys.
See [Privacy and LGPD](https://docs.proteside.com/en/docs/integration/privacy).

In the dashboard, you decide which scripts can run, keep track of alerts and download the evidence reports.

For a product overview without installation details, see
[How Proteside works](https://proteside.com/en/how-it-works) and
[Proteside for online stores](https://proteside.com/en/solutions/online-stores) on the website.

## Key concepts
| Concept                   | What it is                                                                                                                                                                                             |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Organization**          | Your account. It holds the plan, billing and people. An organization can have several stores.                                                                                                          |
| **Store**                 | A protected domain, such as `mystore.com`. Each store has its own SDK key, scripts, alerts, rules and settings. Everything the dashboard shows belongs to the store selected at the top of the screen. |
| **SDK and snippet**       | The SDK is the Proteside code that runs in the customer's browser. The snippet is the piece of code you paste into the page to load it.                                                                |
| **Scripts and inventory** | Every script that shows up in the checkout goes into the store's inventory. A new script arrives as **Needs review** until you authorize or block it.                                                  |
| **Alerts**                | Warnings about something suspicious: an injected script, tampered Pix, a hijacked form, a script whose content changed, and more.                                                                      |
| **Rules**                 | Direct orders to the SDK to block or allow scripts from a domain or a URL.                                                                                                                             |
| **Policies**              | Criteria that automatically authorize or block known scripts, or that recommend a decision for you to review.                                                                                          |
| **Evidence**              | The summary of the PCI DSS requirements, the security headers, the periodic verifications and the reports in PDF, JSON and CSV.                                                                        |

These terms are explained in more detail in the [Glossary](https://docs.proteside.com/en/docs/guide/glossary).

## How the dashboard is organized
*Image: The fixed areas of the dashboard, the same on every screen.*

* The **sidebar** (1) has three sections. **Protection** groups **Dashboard**, **Scripts**, **Alerts**, **Payment
  Integrity**, **Rules**, **Policies** and **SDK Health**. **Compliance** leads to **PCI DSS Evidence**.
  **Settings** groups **Store**, **Pages & Domains**, **Payment protection**, **Notifications**, **Team**,
  **API** and **Audit log**. The numbers next to the items show what's waiting for you, such as scripts to review and
  open alerts. The **Billing** screen isn't in the menu: see [Billing and plans](https://docs.proteside.com/en/docs/guide/settings/billing).
* The **store selector** (2), at the top, switches the store you're viewing.
* The **SDK status pill** (3) turns green with **Proteside active** when the SDK has received real visits to the store
  in the last 24 hours. In red, **Proteside not detected** means the snippet isn't published yet or nobody has opened
  the checkout in that period. Click it to go to **Pages & Domains**.
* The **protection mode pill** (4) shows **Monitor** or **Block**. Click it to go to
  [Payment protection](https://docs.proteside.com/en/docs/guide/settings/payment-protection).
* The **Theme** selector (5), at the bottom of the sidebar, has three options: **Auto**, **Light** and **Dark**.
  **Auto** is the default and follows your system theme.
* The **user menu** (6), right below the theme, gives you access to your profile, language, subscription and the
  **Log out** button.

On mobile, a bar fixed to the bottom of the screen gives you access to **Dashboard**, **Scripts**, **Alerts**,
**Payment** and **More**, which opens the full menu. The store selector sits at the top of the screen, next to the
menu button. On small screens, the SDK status pill shows only the colored dot, and the protection mode pill doesn't
appear.

## Recommended flow
### Create your account and first store
Choose a plan, sign up and enter the store's domain in the wizard. See [Getting started](https://docs.proteside.com/en/docs/guide/getting-started).

### Install the snippet
Copy the snippet from **Settings → Pages & Domains** and paste it as the first item in the `<head>` of your checkout
pages. See [Installing the snippet](https://docs.proteside.com/en/docs/integration/install).

### Confirm the SDK was detected
Open the store's checkout and check for the **Proteside active** indicator at the top of the dashboard and on the
[SDK Health](https://docs.proteside.com/en/docs/guide/sdk-health) screen.

### Review the scripts
In [Scripts](https://docs.proteside.com/en/docs/guide/scripts), authorize what's legitimate with a justification and block what you don't recognize.
[Approval policies](https://docs.proteside.com/en/docs/guide/policies) help you decide on known scripts all at once.

### Handle the alerts
Keep track of [Alerts](https://docs.proteside.com/en/docs/guide/alerts) and [Payment integrity](https://docs.proteside.com/en/docs/guide/payment-integrity), and set up
[Notifications](https://docs.proteside.com/en/docs/guide/settings/notifications) so you hear about problems without having to open the dashboard.

### Generate the evidence
In [PCI DSS Evidence](https://docs.proteside.com/en/docs/guide/compliance), check the status of the requirements and download the report for your QSA.

## Next steps
- [Getting started](https://docs.proteside.com/en/docs/guide/getting-started): From choosing a plan to your first reviewed script.
- [Account and access](https://docs.proteside.com/en/docs/guide/account): Sign-in, password, invitations, stores, language and subscription.
- [Dashboard](https://docs.proteside.com/en/docs/guide/dashboard): Your store's indicators at a glance.
- [Scripts](https://docs.proteside.com/en/docs/guide/scripts): Inventory, authorization and integrity.
- [Alerts](https://docs.proteside.com/en/docs/guide/alerts): Investigate, resolve or snooze.
- [PCI DSS Evidence](https://docs.proteside.com/en/docs/guide/compliance): Requirements 6.4.3 and 11.6.1, and reports.
