Settings

Keys, environments, teammates, connections, and billing.

Settings opens as a panel over whatever you were looking at. Most of it you touch once during setup; two parts you come back to.

Environments and API keys

The part you will actually revisit. Each environment holds its own ingestion key, so production, staging, and local traffic stay separate and you can rotate one without breaking the others.

Environments settings with API keys
A key can be copied, revealed, renamed, rotated, or deleted from its row.

Keys are safe to ship to the browser — that is what they are for. See Install.

People

Membership is per project. Invite the people who need this project rather than granting blanket access, and remove them here when they leave.

Connectors

Where an agent gets permission to reach outside Human Behavior — the messaging and tracker integrations an agent can post to. Connect it once here and every agent can use it.

Everything else

SectionWhat it holds
ProfileYour name, picture, and signed-in devices
PreferencesYour own display choices for this project
NotificationsWhat Human Behavior emails or messages you about
GeneralProject name, URL, and reporting currency
FilteringRules that exclude traffic you do not want counted
MemoryWhat agents are allowed to remember between runs
MCPConnecting an editor or external agent — see MCP
BillingPlan and invoices

Filtering changes what your numbers mean

An exclusion rule applies to counting, so internal or bot traffic stops inflating your metrics. Expect totals to move when you add one — that is the rule working, not a bug.