Inkpilots Documentation
Inkpilots is a collaboration based content engine. It combines editorial planning, scheduled execution, article production, automation, public presentation, and operational governance inside one system. Helps users to build well structured content base. With cannibalization check, scheduling, topic clustering and powerful agent reviews your content becomes efficient and fits the standart without worrying about technical issues.
This handbook is written for product users. It explains how to use the application as a working operating model, not as a collection of isolated features.
Start here
If you are new to the platform, read these guides first:
That reading order follows the real logic of the product: define the workspace, plan the work, schedule it, produce it, then scale and publish it.
What Inkpilots helps you do
Inkpilots helps teams manage:
- topic and cluster planning,
- content cycles and assignment tracking,
- article creation and structured editing,
- agent-based and batch automation,
- public Display Window delivery, out of the box publishing instead of relying on third parties, customize your display windows to fit your brandbook.
- digest subscriber capture and broadcast preparation,
- collaboration, permissions, usage, and API access.
The product is especially valuable when content work is no longer just writing. It becomes an operational system with multiple people, repeated output, external visibility, and resource limits, as a result your content is high quality no matter how you work.
Documentation map
Foundations
Planning and execution
Automation and system scale
Public workspace and audience-facing experience
Governance and operations
Choose the right guide by responsibility
For planners and strategists
Start with clusters, editorial workflow, and schedules.
For editors and content operators
Start with schedules, articles, and automation.
For workspace owners and administrators
Start with collaboration, settings, usage, domains, and integrations.
For teams shaping the public experience
Start with domains, presentation, digests, and public chat.
How to read this handbook well
Each guide is written to explain one part of the real product. You do not need to read every page immediately, but the handbook becomes much clearer when read in workflow order rather than by curiosity alone.
If you are unsure where to begin, start with Getting Started. If you already have a running workspace and want to improve how it operates, start with Editorial Workflow.