Settings

Appearance (light / dark / system) and other per-browser preferences.

What you sell, to whom, and how you position it. Once reviewed, Wave briefs its content AI with this.

Your brand kit (logo, colours, fonts, voice) and the email templates Wave builds from it. Every template carries the legal footer.

Themes, personas, funnel stages, and industries used by content extraction.

Extraction text cap and max tags per category applied by the pipeline.

Map UTM + referrer signals to canonical channels for Channel Affinity.

Toggle the post-sync auto-crawl orchestrator for this tenant.

Define the content-format allowlist used by Content Intelligence extraction (webinar, blog post, whitepaper, etc.).

Opt this tenant in to the per-connector sync control panel (kill switches, writeback toggles, sync-now, history).

Typed fields of your own on the person record. Wave holds every source to the type you declare.

Record types of your own, such as a subscription, with typed fields and records linked to a person or an account.

The kinds of activity Wave records on a person's history, and which of them count as engagement.

The shape each kind of campaign name must have, and who may open each campaign folder.

The rule that decides who may be contacted on each channel, and who it would hold today.

Per-Opportunity Buying Groups setup: HubSpot custom association type, kill switches.

Host and path rules for which pages belong to a sibling business unit, so their engagement doesn't count toward this unit's curriculum.

Slack alerts and email digest for this tenant's Wave notifications.

Verbose vs concise tooltip mode for the in-product data dictionary. Per-browser preference.

Invite teammates, manage roles, and audit Tidal Wave operator access for this tenant.

AI agents that have connected to read this workspace's data. Read-only — access is granted and withdrawn in your identity provider.

Compare each model with and without the agent engagement you opted in, and let a workspace admin promote one once it beats the live model on its bar.

Per-day consumption for this tenant — assets crawled, syncs run, predictions written, writeback pushes — plus AI use against its allowance and caps, where workspace admins set their own limits.

Choose which model runs each Wave AI task: Tidal Wave's Claude, Claude on your own key, or your own OpenAI-compatible endpoint. Workspace admins manage connections and routing.

What Wave sends to an AI model, what it keeps and for how long, and who can read it, for each way this workspace can run AI.

Lifecycle state (active / suspended / archived) and transition history. Read-only here; flip state from the TMC.