Public help · open beta

Help without publishing the product blueprint.

This public Help Center explains Colony Core concepts, safe operating boundaries, and where to get support. Detailed screen flows, field schemas, role logic, configuration, automation, and account-specific procedures are intentionally not published anonymously.

Signed-in users should rely on the current guidance available for their account rather than treating public pages as version-specific product documentation.

Public guides

Understand the model and boundaries

Getting Started

Understand the access and onboarding path without publishing the internal setup sequence.

Open public guidance →

Job Management

Understand why the commercial job is the operating anchor and what remains account-specific.

Open public guidance →

Flight Records

Understand the recordkeeping concept and compliance boundary without exposing the schema.

Open public guidance →

Equipment

Understand shared fleet context and the safety boundary without publishing maintenance logic.

Open public guidance →

Invoicing

Understand business follow-through and financial boundaries without publishing billing mechanics.

Open public guidance →

Compliance Approach

Review the role Colony Core records can play and the decisions that remain human-owned.

Review boundaries →

Detailed support

Exact product instructions belong with authenticated access.

Why

Open-beta screens, fields, permissions, and workflows can evolve or differ by account scope.

Security

A public training manual can disclose more product architecture than a buyer needs to evaluate the platform.

Accuracy

Current account-specific guidance is safer than anonymous instructions that may no longer match the enabled product.

Need help with your account?

Sign in or contact Colony Core support for current account-specific instructions.