HELP CENTER

Answers, not avalanches.

Short articles, organized by what you're trying to do. Search above any time.

Learn CTC

Short lessons on using CTC and on content basics. Every lesson can be read instead of watched, and each one carries a full transcript. Sign in to open the library.

Open Learn CTC
Getting started

Welcome to CTC

CTC is a private console for turning ideas into finished, published work. It holds five things: your inbox of raw ideas, your projects and their stages, your production records, your files' whereabouts, and proof of what you published. Start at Home — it tells you the next useful action rather than showing you a wall of cards.

The four setup questions

Setup asks what you create, how often you publish, when you can work, and where your files live. Each answer becomes a real setting: your formats choose which workflows appear, your cadence becomes a weekly goal the planner measures runway against, your hours become planner availability, and your storage answer becomes a storage root used to build consistent paths. Change any of them later in Settings.

Quick Start, Full Setup, or skip

Setup offers three ways in. Quick Start answers the four essential questions and drops you straight into the app. Full Setup adds brands, channels and destinations while you are there. Skip takes you in immediately and leaves the Quick Start Guide pinned to Home so you can finish the steps whenever you like — your progress is saved as you go, and re-running setup never duplicates anything you already created.

Open the Quick Start Guide

Keyboard shortcuts

Press ⌘K (or Ctrl+K) to search across projects, episodes and publishing records. Press ? to list the shortcuts available on the current screen, and Esc to close any dialog. Every action reachable by shortcut is also reachable by a visible control.

Projects and workflow

Workflows are configuration, not code

A workflow is a named template with ordered stages and a terminal label. Projects move through the stages of the template they were created with, so a newsletter and an animated episode can follow genuinely different paths. Edit templates and stages in Settings — nothing about the pipeline is hard-coded.

Stages versus conditions

A stage is where work stands in its workflow. A condition — active, on hold, canceled, archived — is whether work is running at all. They are deliberately separate, so putting a project on hold never loses its place in the pipeline.

From an idea to a project

Anything half-formed goes to the Inbox. Triage it when you are ready: convert it into a project on a chosen workflow, or dismiss it. Converted items keep their link to the original note, so you can see where an idea came from.

Planning

What the planner does

The planner reads your availability, task definitions, effort estimates and due dates, then proposes work blocks that fit the hours you actually have. It groups compatible tasks together to cut setup time. It recommends — it never books anything by itself, and every recommendation states the reason it exists.

Finishing a work block

Accepted blocks can be completed in full, completed partially, rescheduled inside your availability, or cancelled. Recording what actually happened matters: CTC compares recorded minutes against your estimates and suggests adjustments once it has enough history, instead of guessing.

Reading your runway

Runway compares your publishing cadence with the work that is genuinely ready. When there is not enough finished work to hold your cadence, the planner says so and shows what does not fit rather than quietly producing an impossible schedule.

Files and publishing

What CTC knows about your files

CTC records where files belong and builds consistent paths from your workflow and project details. A browser cannot open a local drive for you, so a storage root is labelled honestly: mounted, external, disconnected, unavailable, or metadata only. CTC never claims to have touched a file it cannot reach.

Publish packages and records

A publish package collects what a piece needs before it ships — the deliverables for that content type. When you publish, CTC writes a publishing record: destination, timestamp and package contents. Those records are also what coverage freshness is derived from, so nothing is inferred from a title.

Trust

Connected, Manual, Mock, Not connected

Every integration displays one of four states. Connected means a real credentialed connection. Manual means you do that step yourself and CTC records it. Mock means the surface exists but the transport is simulated. Not connected means nothing is wired. Any action that would spend money on a paid service asks for explicit confirmation first.

Your data and who can read it

Content belongs to a workspace, and access is decided by workspace membership at the database level — not by which screen you happen to be on. You can export your data from Settings, and deleted records stay recoverable in Trash for 30 days before they go for good.