Inkpilots

Getting Started

Start Here

Getting started in Inkpilots is not about clicking through every tab once. It is about setting up one workspace that can run a real content process repeatedly: people know their roles, planning turns into scheduled work, articles move forward clearly, and the public surface reflects the output intentionally.

This page is the shortest practical route from an empty workspace to a functioning operating model.

What success looks like

You are set up correctly when these things are true:

  • the workspace represents a real boundary such as a brand, client, product, or editorial team,
  • the team knows how planned topics become assignments and articles,
  • there is at least one reliable path to produce content,
  • workspace settings and public identity are coherent,
  • usage, permissions, and public-facing features are under control.

Success in Inkpilots is not a fully populated dashboard. It is a workflow the team can repeat on purpose.

The recommended first path

1. Set up the workspace itself

Start with the workspace as the unit of operation. In the current product, the workspace holds:

  • members,
  • roles,
  • usage,
  • library files,
  • domains,
  • public presentation,
  • API access.

If the workspace boundary is unclear, everything else becomes harder to govern.

2. Configure the general workspace identity

Set the workspace name, slug, visibility, language, and related defaults. These are not minor setup details. They affect how the workspace behaves internally and how it appears publicly.

If you need have your own domain, instead of our public slug, connect your domain to serve content.

3. Build the planning structure

Use Clusters and Topic Planning to create the first meaningful themes, place planned titles into the right clusters, and write notes before anything gets scheduled.

4. Create the first content cycle

Use Schedules and Content Cycles to create or select the first operating window, assign work, and begin moving it through explicit states.

You can create everything in single content cycle, however, cycles creates an emergency effect to follow a due date, a way to stream in constant speed.

5. Create real article output

Use Article Lifecycle and Editor to create empty drafts or AI-assisted drafts, then turn them into structured articles with metadata and publishable quality.

6. Add automation only after the manual path works

Once the team understands what good output looks like, use Agents and Libraries to automate recurring work and introduce reusable file-backed context.

7. Shape the public surface

Only after the internal path is reliable should you finalize domains, presentation, CTA behavior, and public chat settings.

A practical first-week checklist

  • Confirm the workspace name, slug, and visibility.
  • Invite the right initial members.
  • Decide who owns planning, editing, and publication.
  • Create the first clusters and topic titles.
  • Create the first content cycle.
  • Produce at least one article from start to finish.
  • Decide whether automation is needed immediately or later.
  • Review presentation and domain readiness before sending external traffic.

Three starting models that work well

Manual-first

Use this when the team still needs to define quality standards, ownership, and workflow habits. Plan first, schedule second, draft manually, and add automation later.

Automation-assisted

Use this when the team already understands its publishing rhythm and wants to speed up recurring drafting with scheduled or batched agents.

Public-surface-first

Use this when the external workspace matters immediately. In that case, domain settings, presentation, CTA design, and public chat policy need attention earlier in the setup.

What new teams often get wrong

The most common early mistake is jumping straight into article creation without building a planning and scheduling model first.

The second common mistake is enabling everything at once. Agents, public chat, custom domains, notifications, and API access are all useful, but they become much more effective after the core editorial path is stable.

Despite the expertise of your team, workflow can guarantee a quality on the overall output. Use plan, create, edit, review cycle to ensure quality.

Where to go next