
Copy when you need a separate working edition while retaining the source arrangement. Move only when the asset should change location and the destination's rules are understood. A cross-organization move can change broader access even when named direct collaborators remain associated with the content.
Decide what the handoff should own
Write down whether the destination receives a deliverable, a reusable source or responsibility for maintaining the asset. That decision determines whether a new independent copy or a move is appropriate.
Suppose a hypothetical agency prepares a client's campaign. The agency needs to retain its approved source, while the client needs a version for later edits. Copying may suit that brief better than moving the only source into a different organization's Project.
Adobe documents Copy files into projects and Move assets to a project separately. Copying requires appropriate editing permission in the destination; moving across organizations involves destination restrictions and changed access context.
Record the source and destination
Before either operation, identify the exact asset, source Project, destination Project and organizations involved. Keep a reference proof and a record of the intended owner. Similar names are not enough to distinguish two campaign editions later.
For a copy, use the documented Copy to Project route, select the destination and save a clearly named copy. Confirm that the destination actually contains the expected content.
For a move, read the destination context before confirming. Adobe explains that directly shared collaborators can retain access unless changed, while broad organization access does not carry over in the same way. Future moves also depend on the destination organization's permissions.
Review access after the operation
Test with the actual accounts that need to work on the destination edition. Check both a named collaborator and, where relevant, someone whose former access depended on organization membership.
Avoid interpreting one person's successful open as proof of universal access. If a colleague loses access, determine whether the lost permission was direct or organization-wide before repeatedly moving the file back and forth.
A Save a Copy workflow preserving an open master reflects the same ownership distinction. A linked-content update overwriting local InDesign edits warns against leaving two teams unsure which source controls future corrections.
Accept an editable handoff with clear ownership
For the agency example, acceptance means the source remains as agreed, the client can make a representative authorized correction and the exported proof matches the intended campaign. State whether future corrections belong in the client copy or the agency master.
If dependencies are unavailable, resolve them explicitly rather than assuming a Project operation is equivalent to packaging every linked source image.
If destination restrictions prevent the intended arrangement, stop that transfer and agree on an authorized deliverable. Preserve the current editions while the owner resolves access; do not sacrifice the source merely to make the destination appear populated.
Related tasks
- Save a Photoshop Delivery Copy Without Switching the Master
- Why Does Updating Linked InDesign Content Undo My Local Changes?
- Why Are Images Missing When Someone Else Opens My InDesign or Photoshop Project?
Sources and scope
- Adobe: Copy files into projects: Copy to destination Project, naming and destination editing permission.
- Adobe: Move assets to a project: Cross-organization destination restrictions, direct collaborators versus broader organization access.
Documentation-based guidance. Examples are hypothetical and acceptance checks are proposed; no installed-application test is claimed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.