Confirm your workspace
Your workspace is the boundary for your company’s projects, users and records. Check the workspace name before entering customer data.
This guide shows the recommended order for setting up a deployment so testing, issues, approvals and handover stay connected to the right customer, site and system.
help-dashboard.webphelp-dashboard.pngYour workspace is the boundary for your company’s projects, users and records. Check the workspace name before entering customer data.
Create the organization receiving the deployment. Keep the customer record stable so multiple projects can sit beneath it.
Add the delivery project and the dates/status information your team needs to track execution.
Create each physical or logical deployment location. Sites keep systems grouped where the work is actually happening.
Create one system record for each delivered system or operational unit. This is the record that testing, issues and acceptance will follow.
Add or associate the equipment that makes up the system so serial numbers and delivered assets remain traceable.
Select FAT, SAT or commissioning templates, or create a controlled test template for the project.
Run the test, record evidence, turn failed items into issues and retest after corrective action.
Submit completed testing to the authorized approver instead of relying on informal email confirmation.
Review readiness, capture customer acceptance and create the final handover package from the records built during delivery.

Once the project structure is clear, learn how the hierarchy works in detail before importing or creating large quantities of system data.
Read Projects & deployment structure →