Knowledgebase

Create a controlled variation

Choose Create Template or clone an existing definition. Select its kind, business, category and name. Add the tables, fields, stages, tasks and document categories your process requires.

Supported fields include text, long text, number, date, email, phone, URL, select and checkbox. Set required fields and select options deliberately. Save validates the definition and rejects concurrent edits instead of silently replacing a newer version.

Export and import

Export produces a .pcmo-template.json configuration file. Import validates the format and references and accepts a document up to 1 MiB. It does not import staff, permissions, work records or attachments. Local team identifiers are removed from exported definitions.

An installed template cannot be moved between businesses. Export and import a separate copy when another business needs its own variation.

Keep sensitive details out of shared defaults, template names and starter tasks. Store private information in the appropriately restricted work record instead.

Browse and preview

Open Template Library → Browse Templates. Filter by project or case, choose a category or search for your process. Preview the definition before installing it into the correct assigned business.

The library contains 200 starting points: 100 projects and 100 cases. Templates contain configuration rather than sample customer records. Review their fields and stages before using them for live work.

Create a record

1. Install the chosen starter into the business.
2. Open My Templates and choose the installed template.
3. Create a project or case with the required details.
4. Review the starter tasks and assign the appropriate people and documents.

You need access to the business, an active assigned template and permission to create work. Template authorship alone does not provide access to other people's records.

Keep existing work stable

Each record keeps its template snapshot. A later edit to the reusable template affects future work. Use the separate project and case lists and their completed or archived filters to find older records.

The package

PCMO is listed at USD 69 once for one domain. The licence is bound to the domain rather than a fixed server IP, and domain changes are allowed. Update and support terms are confirmed separately with the purchase.

Before changing a domain

Back up the database, configuration and private storage together. Keep the original encryption key. Prepare HTTPS and test the new hostname in an isolated copy before changing the live canonical URL.

Use the available licence-management transfer process for the new domain. A domain change does not authorize two simultaneous production installations. Keep the old installation restricted during the move and verify the new installation before retiring the old one.

Accounts and access

Your PCMO owner and staff remain local to the installation. The Orbit purchase account does not grant vendor access to your projects, cases or server.

Commercial activation availability is shown separately from the package description. Do not publish licence secrets, setup keys or private configuration in a support ticket or community post.

Prepare a new installation

Use a fresh directory and a new empty MySQL 8.0+ or MariaDB 10.6+ database. PCMO needs PHP 8.2+ with PDO MySQL, OpenSSL, mbstring, fileinfo, JSON, session, ZIP, DOM, GD and cURL. Enable HTTPS and include the release's .htaccess rules.

Do not extract over an existing workspace or import its schema manually. Confirm that direct requests for app/, config/, storage/, plugins/, database/, bin/, tests/, docs/ and vendor/ return 403 or 404.

Check and open setup

Run these from the application directory as the same operating-system user that runs its PHP worker:

php bin/install.php --check
php bin/setup-key.php

Keep the generated setup key private. Open /install.php on your HTTPS workspace, enter the key and supply the canonical URL, organisation, dedicated database details and your own new owner account.

After setup

The installer removes its one-time key and locks itself. Sign in, review the local users and business settings, then configure your templates. Back up the database, private storage and config/app.php together; its original application key is needed to decrypt protected data.

External mail and payment services need your own configuration. The fresh installer is not an upgrade or migration tool. Follow the instructions shipped with the exact release if setup is interrupted; never reset a database containing real work.