File groups vs delivery folders: making the difference obvious

by•

I'm part of the team behind GJ File Manager. One distinction in our file-group workflow deserves a clear explanation: collecting references is different from preparing files to send.

Suppose a project has a logo in Images and notes in Documents. A file group can keep those items within reach while their originals stay where they are. That is useful for reviewing a project, but the group is not a portable delivery folder or an independent backup. Access still depends on the original locations and permissions.

For a handoff, a practical sequence is:

1. Use the group to locate the required items.

2. Copy the actual deliverables into a separate, clearly named folder.

3. Open the destination copies and check content and versions before sharing.

A filename or matching file count alone cannot confirm that a handoff is correct. Keeping the review step separate from the copy step makes it easier to notice a wrong version without rearranging the working folders.

For people who use reference-based collections: what would make this distinction clearest at the moment of sharing? A persistent label saying that originals stay in place, a reminder when opening the group, or something else? Specific confusing situations would be especially useful. This is a workflow discussion, not an announcement of a new sharing feature.

2 views

Add a comment

Replies

Be the first to reply

Have a question or a thought to share? Add a comment above to start the conversation.