Public help · open beta

Job Management

Colony Core uses the commercial drone job as a shared operating anchor. This public article explains the model and safety boundaries without publishing the exact screen flow, field schema, permissions, or controls.

Sanitized Colony Core job workflow fragment
Sanitized product-derived fragment; not a step-by-step UI map.
What to understand

The job is the context other operating records can reference.

Use the job-management area to keep the team oriented around the same body of work and its current operational context.

Public guidance

Three principles

Keep context current

Maintain accurate information about the work so office and field teams are not relying on outdated private notes.

Keep responsibility clear

Use the enabled workflow to make internal ownership and progress understandable to the people involved.

Review before acting

Software context supports coordination; users remain responsible for operational decisions, client commitments, permissions, and accuracy.

Why the public article stops here

Detailed instructions are account-specific during open beta.

Exact navigation, fields, status logic, imports, notifications, role permissions, automation, and client-facing behavior can evolve or vary by enabled account scope. Publishing a universal click-by-click guide would be both inaccurate and unnecessarily expose implementation detail.

Signed-in users should use the support path provided for their account, or contact Colony Core support for current instructions.

Need help with an enabled job workflow?

Use your signed-in account or contact support for the current account-specific procedure.