# Configure

Once Sentinel is installed, configuration happens through the admin interface (or its API). Four concepts cover most of what you'll set up:

## Security Groups

A Security Group holds the rules that govern Sentinel's behavior for a given app or environment — access level (Public, Restricted, or Full), Autopilot behavior, rate limits, and which features are enabled. Most setups use one Security Group per environment (e.g. production vs. staging), or one per app.

See [Security Groups](/docs/sentinel/configure/security-groups/).

## API Keys

Each API Key is created under a Security Group and inherits its access level and rules. The public key (`key_...`) is used by the widget to fetch challenges; the matching secret is used by your server to verify submissions. Rotate keys per-app or per-environment as needed.

See [API Keys](/docs/sentinel/configure/api-keys/).

## Users & Accounts

Accounts group your Security Groups, API Keys, and Forms into logical units (a project, a client, a department). Users are then given a role — Admin, Member, or Read-only — per account, controlling who can access what in the Sentinel admin interface.

See [Users & Accounts](/docs/sentinel/configure/users-accounts/).

## Forms

Collect submissions directly through Sentinel without building your own verification endpoint, and apply content moderation (Classifier, Phishing Detection, Similarity & Training Data) to what's submitted.

See [Forms](/docs/sentinel/configure/forms/).

## Next steps

With a Security Group and API Key in place, continue to [Embed the widget](/docs/integration/widget/) in your app, or review [Features](/docs/sentinel/features/) to decide what to enable.