Items
Items is the umbrella term we use for Projects and Drivers.
Projects
Projects are the foundation of Integrate. They can represent everything from missions and hardware to systems and programs—and form the backbone of your 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 provide a structured way to split a Project into manageable parts. They’re typically nested under a Project for organization.
|
|
|
|
Milestone: A major checkpoint that indicates meaningful progress. Use it to group the Drivers that contribute to the outcome, or link Tasks to it with Dependencies to keep scheduling accurate. Milestones are the only driver that can be displayed on the project bar using 'Milestones on Row' display feature.
Task: Captures the work that needs to be completed. They often roll up to a Milestone, and can be linked to a Requirement to provide clear evidence that the work was delivered.
Requirement: A defined standard or obligation that remains visible in the plan. Requirements show up on the Gantt/Timeline, connect to Tasks and Milestones, and require dates so they can be scheduled (even if approximate). They can be shared for verification with internal teams or external partners, often with evidence attached.
Component: An individual part or item that is specified on a bill of materials and used in the assembly of a subassembly or finished product.Nesting
Nesting is a hierarchy feature. Nesting a Build under another Build makes it a child of that parent.
Parent: A Project or Driver that has one or more items nested under it.
Child: A Project or Driver nested under a parent.
Dependencies
Dependencies are how you connect items in Integrate so the timeline reflects real relationships. 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 Projects and Drivers, so your schedule captures the full chain of work.
Collaboration
Collaborators can be internal users or external partners. In Integrate, permissions are assigned per Project 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 items 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 for items to require approval for edits.
