Projects
Projects are the core building blocks in Integrate—often called living datasheets or templates. Use them to represent anything from missions and hardware to systems, programs, and projects, and to create your product or system hierarchy.
 Robot |  Electrical Power System |  Antenna |  Ground Contact |  Cooling System |
 Fuel Tank |  Space Station Accommodation |  Chassis |  Ship |  Receiver |
 Propulsion |  Communication System |  Structure |  Plane |  Valve |
 Memory |  Microprocessor/ Printed Circuit Board |  Launch Vehicle |  Balloon |  Generic Program/ Spacecraft |
 Software |  Separation Mechanism |  Auto |  Sensor |  Robotic Arm |
 Generic Hardware |  Mission |  Effector |  Display |  Project |
 Generic System |  Motor Controller |  Avionics System |  Deployer |  Payload |
 Motor |
|
|
|
|
Drivers
Drivers capture the work and requirements behind a Project's plan. Use them for tasks, milestones, and requirements, and find them under “Drivers” throughout the app. The term is designed to scale as additional types are introduced.
|
|
|
|
Task: The actual work. Do the thing. These often roll up to a Milestone, or get linked to a Requirement when you need to prove you really did the thing.
Milestone: The “we made it” marker. Nest Drivers under it to show what counts toward it, or tie Tasks to it with Dependencies so the schedule behaves. Milestone are the only driver that can be displayed on the project bar using 'Milestones on Row' display feature.
Requirement: The rulebook entry that refuses to live in a dusty corner. In Integrate, Requirements sit right in your Gantt/Timeline like everything else, get linked to Tasks/Milestones, need dates to show up (think “roughly when”), and can be handed to internal or external folks to verify—often by uploading proof.
Component: A tidy little container Driver for grouping work in Integrate—give it dates, an owner, and a status so everyone can see what’s happening (and what’s stuck).Nesting
Nesting is a hierarchy feature—think “systems structure,” not a dependency link. Nesting a Build under another Build makes it a child of that parent. This is different from connecting items using Dependencies (blockers/flowdowns/relationships).
Parent: A Build or Driver that has one or more items nested under it.
Child: A Build or Driver nested under a parent.
Dependencies
Dependencies are how you connect items in Integrate so the timeline reflects real relationships—not just a list of dates. There are three options:
Fixed: Maintains a set offset between two items. Adjust one, and the other adjusts to match.
No Overlap: Lets slack absorb changes first. If the predecessor slips far enough, the successor follows to avoid overlap.
None: Creates a visual connection without pulling dates around.
Integrate lets you daisy-chain dependencies across Builds and Drivers, so your schedule captures the full chain of work—not just isolated dates.
Collaboration
Collaborators can be internal users or external partners. In Integrate, permissions are assigned per Build and Driver, giving you granular control over who can view and edit from Programs down to Sub-Drivers.
Add collaborators using 
on a Project/Driver card or via List Actions in the Omnibar.
Permission types
Owner: Manages the object and permissions. Ownership can be reassigned.
Editor: Can update allowed fields, dates, and files. Approvals may restrict edits when enabled.
Viewer: Read-only access for sharing schedules and program visibility.
Approvals
Enable Approvals per object to require approval for edits.