Start here
For a new workspace, create a Work item, choose its type, add tasks and dates, then connect the files, approvals, and collaborators that move it forward.
Start guided trialLoading workspace. Content is loading.
Loading workspace
Loading workspace
Help
Learn how Cedria connects strategy, execution, approvals, assets, content, launch, reporting, and learning.
For a new workspace, create a Work item, choose its type, add tasks and dates, then connect the files, approvals, and collaborators that move it forward.
Start guided trialBrowse concise self-serve guides for first sessions, Work setup, reviews, files, billing, data export, private preview limits, and troubleshooting.
Browse articlesUse demo data for a quick tour, or create a real Work item from guided setup when you want to test your actual workflow. Avoid highly sensitive production data during private preview.
Compare pathsStart with guided Work setup when you want structure from day one, or use the simple create path when you already know the plan.
Start guided setupUse templates when you want starter tasks, goals, KPIs, content ideas, and launch checks for common motions like product launches, webinars, paid ads, newsletters, client reviews, and lead generation. Start blank when the plan is already custom or very small.
Browse templatesA workspace holds your team and the work you are moving forward. Work can include campaigns, projects, launches, client engagements, and operational efforts.
Open settingsUse work detail pages as the operating center for briefs, tasks, approvals, assets, content, launch readiness, budget, risks, and learning loops.
Open workTasks track ownership, priority, due dates, blockers, completion, and archived execution work.
Open tasksApprovals help teammates request decisions on work, assets, tasks, and review notes.
Open approvalsAssets are link-based deliverables and references such as landing pages, creative, documents, ads, social posts, and emails.
Open assetsContent items plan what will go out, on which channel, when it is scheduled, and what asset or approval supports it.
Open contentLaunch plans track go-live dates, launch owners, readiness status, rollback notes, and pre-launch or post-launch checks.
Open calendarBudgets and spend items help teams compare planned, committed, and actual spend without becoming accounting software.
Open reportsRisks track what might go wrong, issues track what is going wrong, and decisions record important calls the team has made.
Open risksExperiments capture hypotheses and outcomes. Learnings and retrospectives preserve what the team should reuse next time.
Open learningsReports summarize campaign progress, health, launch readiness, client waits, tasks, approvals, assets, content, budget, risks, team workload, and recommendations.
Open reportsAttention collects Work with current operational health signals. Its Notifications view keeps delivery updates and read state separate. Activity shows recent workspace changes.
Open AttentionScheduled digests use your saved timezone and send-hour preference. Settings can suggest your browser timezone, but it is never applied without your action.
Open settingsAutomation rules are private-preview reminders that run when manually evaluated and create in-app notifications or activity.
Open automationsUse CSV exports for portability and pasted CSV imports for starter campaigns or tasks. Imports are owner/admin guarded.
Open toolsOwners and admins can review data inventory, download a safe JSON workspace export, inspect archived/demo counts, and read current private preview lifecycle limitations.
Open data controlsRead the private-preview terms, privacy summary, and security overview. These pages are not final lawyer-reviewed documents and make no compliance certification claims.
Open securityDemo data creates clearly marked sample campaigns for QA and demos. It never sends real emails and can be cleared without deleting non-demo records.
Open demo dataClient portal and public review pages let stakeholders review selected packages without exposing internal tasks, budgets, risks, reports, or private notes.
Open reviewsWorkspace members are internal collaborators with roles like owner, admin, and member. Stakeholder contacts are external reviewers and do not get workspace access.
Open settingsBilling is in foundation mode for private preview. Owners and admins can review plan usage, Stripe setup readiness, and hosted checkout or portal actions when Stripe prices are configured.
Open billingPublic plan comparison shows Free, Starter, Studio, and Agency limits aligned with the billing foundation. Signed-in users can continue from pricing to billing settings.
Compare plansContacts are clients or reviewers for review packages and portal workflows. Add them when you need external feedback, not internal workspace collaboration.
Open contactsLaunch readiness turns strategy, tasks, content, assets, approvals, feedback, risks, budget, and checklist progress into a practical readiness view.
Open workReview packages create public token links for selected work items. Anyone with the link can view the package, so share carefully.
Open workThis private preview is ready for work workflow testing, but some production features are still being refined. Avoid storing highly sensitive production data for now.
Open readinessOwners and admins can review private preview and paid beta readiness across billing, email, storage, trust pages, data export, feedback, errors, usage, docs, and demo workflows.
Open launch controlOwners and admins can track invited testers, onboarding status, feedback, and usage signals from the private preview tester cohort.
Open testersUse the cohort dashboard to review activation pipeline stages, follow-up needs, feedback highlights, usage signals, and paid beta candidates.
Open cohortNot included yet: hard production paywalls, external publishing, external calendar sync, custom client branding, advanced file annotations, AI planning, and custom report builders.
Review limitsWhen reporting issues, include the workspace, Work name and type, route, what happened, what you expected, and whether demo data or test data was used.
Get support tipsUse support when you need help getting unstuck. Use product feedback when you want to suggest an improvement or share a reaction.
Open support requestOwners and admins can triage customer issues, connect support to feedback or errors, and track resolution from the internal support inbox.
Open support inboxUse in-app feedback for bugs, confusing workflows, missing features, rough copy, performance issues, or product reactions from private preview testing.
Send feedbackA coordinated effort such as a project, campaign, launch, client engagement, or operational initiative.
A Marketing Campaign Work type for coordinated promotional activity across channels.
The shared team space where work and operating records live.
Assigned work with status, priority, and optional due date.
A request for a teammate to approve or request changes on work.
A link-based deliverable or reference tied to work.
A planned piece of channel content with schedule and status.
Go-live details, owner, status, and launch checklist context.
The planned campaign budget and current budget status.
A planned, committed, or spent budget line.
Something that might hurt delivery or performance.
An active problem that needs ownership or resolution.
A recorded choice with context and rationale.
A hypothesis or test the team wants to learn from.
A reusable insight or recommendation from work.
A post-campaign summary of what worked and what to improve.
A shareable stakeholder review bundle with selected items.
A manually evaluated reminder rule for operational issues.
A private-preview usage boundary for active work, members, assets, reviews, or automation rules.
A reusable filtered list view for repeated workflows.
A derived view of current Work that needs a person to notice, decide, or act.
A delivery update addressed to the current user with persistent read state.
Recent workspace updates across Work and operating records.
Cedria is in private preview. Test work planning, guided setup, tasks, content, assets, reviews, client portal flows, readiness, reports, workload, automations, and demo data. For now, avoid highly sensitive production data and report anything confusing, slow, broken, or unexpectedly visible on public pages.
Include the workspace, campaign name, route, what happened, and what you expected.
Screenshots help, but do not include secret values or sensitive production customer data.
Public data exposure, failed uploads, broken review links, and email safety issues are highest priority.