Integrations

• Workforce identity. Establish how signed-in people map to delivery team members. Use that mapping for assigned tasks, submitted time and the person recorded against an action.
• Calendar and planning sources. Arrange any import of project dates, package intervals and task dependencies from your existing planning sources. Preserve task identity and predecessor meaning before submitting the graph for feasibility checking.
• Document stores. Connect the approved location for requirements, designs and verification evidence. Keep each file reference attached to the correct delivery record and available only to its authorized readers.
• Time sources. If working hours arrive from another system, map the person, project, task and work date explicitly. Check the imported entry against the same positive-hours and submitted-state rules used by the time-entry workflow.

Admin establishes access and identity mapping. Project Manager agrees the meaning of imported dates, dependencies and recorded hours before those inputs affect the working plan. Delivery Lead and QA Engineer identify the evidence they need for commitment decisions and verification.

Rehearse a missing task reference, an ambiguous person mapping and a file attached to the wrong parent. Preserve source identifiers through the receiving process so a reviewer can trace the result. Keep credentials in the approved connection setup and avoid putting them in task descriptions or evidence notes.

Use Implementation to agree the import conventions and Data model for dependency order.