Step-by-step guides, organized by what you're doing: never by video or article.
You land here in one of three moments: you're setting Bryn up for the first time, you already have it running and want to know exactly what the controls do, or you're the engineer who's been handed the deeper, technical end of either job. This hub is organized around those three moments, onboarding, control plane, GTM engineering, not around whether something happened to get published as a written guide or a video.
Every guide here is written the same way the product itself works: concrete steps, a way to check you actually did it right, and links to the deeper docs page if you want more than the marketing-surface version.
Go from a blank workspace to your first identified account, a real company Bryn has actually resolved from an anonymous visit, not a line in an analytics report, in about 30 minutes.
For: anyone about to set Bryn up for the first time
Everything below adapts Bryn's own six-step setup wizard, the same one you'll actually click through, so there are no surprises between what you read here and what you see in the product.
Your First Identified Visitor in Slack: The Complete Setup Walkthrough
The six-step wizard, start to finish, adapted from Bryn's own getting-started docs, including the "about 30 minutes" claim, sourced.
Installing the Pixel Without an Engineer
The per-platform install paths (GTM, HTML, Webflow, WordPress) and what to send a developer if you don't have site access yourself.
Getting Your ICP Defaults Right
Why the default scoring weights are good enough to start on, and when it's actually worth changing them.
Mapping Your First Signals
Turning raw site and product events into a named signal, with worked examples.
Connecting Slack and Your Other Outputs
Getting alerts landing in the right channel without turning it into noise you mute.
How to run Plays, the automated rules you set once, in plain terms: when this happens, do this, with exactly as much oversight as you want.
For: anyone whose Plays are already live and wants to know precisely what the controls do
These guides use the product's own control language: Run mode and Approve mode, as described at civic.com/bryn/product, plus the kill switch and audit trail exactly as the docs describe them, rather than a marketing paraphrase of any of it.
Run, Approve, and Kill: Inside Bryn's Control Plane
The two modes every Play runs in, the one-click kill switch, and the audit trail underneath all of it.
Reading the Audit Log Like Your CFO Will
What's actually recorded for every run, and how to hand the record to someone who wasn't in the room.
Setting Holds and Cooldowns on a Sensitive Play
When to move a Play from Run mode into Approve mode, and how cooldowns keep it from firing too often.
Building a Play From Scratch
Trigger, conditions, and actions: assembling a new Play beyond the pre-built library.
The technical layer underneath: the MCP server, the API, and request signing.
For: engineers, technical co-founders, or anyone helping with the two topics above
Bryn's dashboard covers setup and day-to-day operation on its own: you don't need any of this to run Bryn. These guides are for the reader who wants to go further: connecting an MCP client, calling the API directly, or verifying signed webhook payloads.
Connecting the MCP Server to Claude, Cursor, or VS Code
Wiring Bryn's MCP server into an AI coding tool, step by step.
Signing Requests With HMAC
Verifying server-side events with request signing, for anyone posting events into Bryn directly.
Using the API Alongside the Dashboard
Base URLs, auth, and tenant resolution: for teams who want to script parts of setup instead of clicking through it.