Integrations and source ownership

• Calendar. Choose how scheduled meeting dates and organizers reach the team’s calendar, and which system owns invitation changes.
• Conferencing. Add the chosen meeting link to the team’s invitation process when remote attendance is needed.
• Document storage. Use a stable file URL for an attachment associated with a supported project record.
• Identity. Map staff sign-in to the person and project access they are allowed to use.

Name one owner for each connection. Agree which record supplies the project, person, date and identifier. Test a changed meeting time, a deleted file link and a departed team member before routine use. Preserve the source record when a connected system is temporarily unavailable. Use the implementation plan to assign these decisions.