Integrations

• Identity directory. Decide how user accounts and delivery team members are maintained so owners and usage reviewers remain current.
• Document storage. Keep the original files in your chosen repository and use attachment references where delivery evidence needs to be found.
• Finance system. Agree how approved usage and booking budget context are passed to the people who handle billing or cost review.
• Planning calendar. Decide whether your team needs booking dates shown beside schedules held in another tool.

Name the owner of each source and the direction of updates before importing records. Keep the booking and usage identities stable across handoffs. A failed operation receipt deserves review by the responsible lead before a downstream action is repeated. Start with a real booking and its approved usage to check that dates, people and hours retain their meaning across systems.