Account and campaign workspace
Account creation, email verification, first-campaign setup, tenant configuration, and role-aware access.
Feature availability
Useful now. Honest about what comes next.
CampaignOS labels capability by operating posture so teams can distinguish validated foundations, controlled beta workflows, near-term packaging, and future-platform direction.
AT A GLANCE
- Core workspace available now
- Beta capability clearly labeled
- Future work kept separate
Current capability map
A campaign workspace that grows in controlled layers.
Availability labels describe the current product posture, not a promise that every workflow fits every campaign.
Hosted campaign website
Campaign identity, content, media, website events, preview, publishing, and supported calls to action.
Field, signatures, and volunteer operations
Field and signature tools remain part of the core workspace. Campaign and Victory add beta volunteer operations subject to human review, campaign policy, and legal boundaries.
Guided starter packaging
Clearer onboarding, billing entitlement enforcement, launch guidance, and remaining workflow polish.
Clone-and-Modernize platform
Broader intelligence, migration tooling, cross-campaign collaboration, and dashboard modernization.
Operating boundary
CampaignOS remains the current brand and product track.
Future CampaignOS capabilities remain labeled until implementation, security review, deployment, and QA support stronger claims.
- CampaignOS v1 remains supported
- Current tenant safety remains a release gate
- Beta workflows require campaign judgment
- Future-platform work is not advertised as available
Start with the proven path
Use the validated foundation first.
Create the account and first campaign workspace; add beta workflows only where they fit your campaign.