Back to Delivery Hub

Quick Start Guide

Go from install to live in 7 steps. Follow along at your own pace.

1
2
3
4
5
6
7

Choose Your Environment

Pick where to install Delivery Hub. We recommend starting with a Sandbox.

Recommended

Sandbox (Testing)

Safe environment to explore features. No risk to production data.

Estimated time: 2 minutes
Install in Sandbox

Tip: Select "Install for Admins Only" during installation for best results.

Live Org

Production (Live)

Install directly in your live org. Your team can start using it immediately.

Estimated time: 2 minutes
Install in Production

Tip: Select "Install for Admins Only" during installation for best results.

Step 1 of 7

Ticket Flow · Intake → Sync → Auto-Schedule

Once you're live, here's how tickets actually move. Four supported intake paths feed the same WorkItem__c object, the cross-org sync chain replicates them downstream, and Auto-Schedule re-baselines the whole timeline in one click.

1 · cloudnimbusllc.com portal

External submitters land on /mf or /portal/wi/new. Form POSTs to /api/work-items. WIs land at Status=New for triage.

2 · Direct in Salesforce

Delivery Workspace → Ghost Recorder floating form, Kanban + New button, or Voice Notes tab. Native WorkItem__c records.

3 · Slack lightning-bolt

Reaction emoji on any Slack message creates a WI with the message body as description. Same Status=New intake state.

4 · Email-to-WI

DeliveryInboundEmailHandler parses subject + body. Replies to WI notification emails post as comments (T-XXXX pattern).

Cross-org sync · how downstream orgs receive tickets

The sync chain is linear: Client Org → Vendor Org → Portal. Each hop writes a SyncItem__c ledger entry and POSTs to the next via an HMAC-signed callout (X-Signature header validated by DeliveryWebhookReceiverApi). Echo suppression via GlobalSourceId stops loops. WL/Comment payloads that arrive before their parent WI go to a Pending queue and drain on arrival.

Detail in the Sync API Guide.

Auto-Schedule · re-baseline the whole timeline

Once tickets are flowing, the Gantt's Auto-Schedule button (release/0.239) runs CPM + capacity leveling client-side, previews every proposed change, and applies the selected deltas through the same audit-pass pipeline as a manual drag. One Submit click, one atomic batch.

Operator walkthrough

Need help? Check the in-app Delivery Guide or reach out.