PlatformHow it worksPricingDocs
中文Sign inOpen workspace
Documentation
Get startedGetting started
Core workflowsCampaignsSourcingMailboxesInbox and Threads
Billing & adminCredits and billingTeam and roles
← Docs

Campaigns

Last updated August 7, 2026

Configure creator campaign briefs, budgets, routing, and approval gates in Karis.

On this page
  1. 01Campaign model
  2. 02Brief and audience
  3. 03Campaign Default Mailbox
  4. 04Approval gates
  5. 05Content and fulfillment

Campaign model

Campaigns are created directly in Karis. Each campaign holds configuration for briefs, audience, routing tags, budget, fulfillment rules, and workflow state. Campaign IDs are generated independently inside your Organization.

Campaign-first configuration means sourcing sessions, outreach Threads, negotiation, content review, and publish stats can all reference the same campaign context.

Brief and audience

The campaign brief captures what you are promoting, deliverable expectations, brand guidelines, and compensation boundaries. Audience fields and routing tags help Karis match creators during sourcing and route inbound replies to the correct campaign Thread.

  • Budget tracks target spend and progress toward published creators.
  • Routing tags in subject patterns help classify unsorted mail into campaigns.
  • Policies define negotiation boundaries and operator review requirements.

Campaign Default Mailbox

The Campaign Default Mailbox is the mutable Mailbox preference used for future first sends on Threads that have not started a provider conversation. Organization administrators may change or clear it at any time.

It is a default, not historical evidence: changing it never reroutes a bound Thread, Message, provider operation, or sync cursor. Once a Thread's first send is accepted, the Thread Mailbox Binding is fixed for all follow-ups and replies.

Approval gates

Karis supports operator-reviewed drafts and confirmation gates before messages leave your Organization. Approval gates appear in the cockpit and campaign views when policy requires human review — for example before first touch, after negotiation changes, or before contract steps.

Drafts remain Local First-touch Drafts until send: mailbox-neutral content stored only in Karis with no provider draft ID. Sender and signature resolve at the durable send boundary.

Content and fulfillment

After creators accept, track deliverables, content review, compliance checks, and publish stats from the campaign detail views. Fulfillment records connect deal terms, uploaded assets, and publication evidence back to the same Thread and campaign.

PreviousGetting startedNextSourcing
Privacy PolicyTerms of Service
© 2026 Karis