Connected systems

• Project source. Agree how project identity, owner and status enter the change workspace when another system owns them.
• Identity service. Link team members to Users so the person doing work can be matched to the right account.
• File storage. Decide how files used for record attachments are stored and made available to permitted reviewers.

Choose one owner for each incoming project and person identifier. Confirm which updates may change an existing record and how a conflicting revision is handled. Use the operation key and receipt result when investigating repeated or failed governed actions. A connection should preserve the package and review decision history when upstream details change.

Begin with a small project and one sample attachment. Verify the project relationship, account link and reviewer access to the file before expanding the import. Reconcile the affected package and its source revision after any correction.