Move a file. But where, and what happens to access?
Moving, copying and shortcuts have different effects. Design folder selection, access information, name conflicts and the result of a partially completed operation.
Article language: English

In this article
A folder called “Ready” exists in three places. One is used by the team, another by the client, and the third is a reminder of a project that ended a year ago. The “Move here” button looks equally convincing in each one. Only after clicking do we discover which “here” we meant.
Changing folders does more than tidy a list. In a shared file system, it can change who can find a file and who can open it. The design should show the destination before the operation and its actual result afterwards. An animated row disappearing answers neither question.
First decide what should remain the same file
Imagine a ceramics studio. The team selects photographs of a new collection and shares approved material with a partner shop. Marta wants to move four photographs from a working folder to a client folder. She does not want four more versions: she wants the same selected set to be available for the next stage of work.
Before designing the dialog, define what each action means in this product. Moving changes the location of an existing object. A copy creates a separate object whose later edits may no longer match the original. A shortcut points to another object. Keep these distinctions clear in the interface, even if all three actions start from a similar menu beside a name.
Google Drive Help explains that a shortcut points to the original and creating one does not automatically update the original file's permissions. A visible shortcut therefore does not, by itself, mean that someone can open the content. This is a rule of one particular service; do not apply it to another library without checking.
At the studio, a shortcut may make sense if the same photographs need to be found in two places. A copy may suit a separate set prepared for the partner. Moving helps when the files really have finished their work in the working folder. The choice depends on what should happen if a photograph changes later. The appearance of a button cannot decide that for the owner of the material.
A copy also needs a clear relationship to the original, if the product is meant to maintain one. Do not suggest that two files synchronise merely because they have identical names. People should understand whether editing a description in one place will also change the material visible in the other. If it will not, the new set needs its own check for currency.
The principles of a download centre (in Polish) help explain the purpose and version of the photographs. Here there is another decision: where this particular object should be maintained. A good library does not make Marta guess whether a colour-corrected photograph will still be the one reached by the link sent to the partner.
“Here” needs an address people can recognise
In the selection dialog, show the workspace name and the full, recognisable path to the destination. “Partners / Półka Shop / Autumn collection / Ready” says more than a single highlighted row called “Ready”. When several companies are involved, the organisation name should remain visible while someone scrolls through folders. Similar names do not necessarily mean similar access.
Browsing and confirming a destination are two different actions. Pressing a folder might open its contents or select it as the destination. The design must show which action occurred. After expanding a branch, a person should not have to wait for the final message to discover that they selected the parent folder.
PatternFly's Tree view component supports separating the selection of a node from the expansion of its contents. A node is an item in the hierarchy, such as a folder containing more folders. That is a useful component capability, but confirming a destination in our library still needs its own design and testing.
Folder search should show where each result sits. Do not change the chosen destination to the first result just because the user types another letter. People need to distinguish a list of candidates from the folder already awaiting confirmation. Three “Ready” results without paths only reproduce the original problem faster. If choosing a result takes someone to the right branch, keep the destination visibly selected. If it confirms the destination without opening the branch, show the final path beside the action button.
Decide how unavailable destinations behave. You can explain why a move to a visible folder is unavailable, but the list should not reveal private projects to someone who is not entitled to know their names. The explanation must be consistent with information the user is actually allowed to see. A disabled row does not itself create permission.
Include the case of moving a whole folder. Choosing somewhere inside it as the destination needs different handling from moving a photograph. The interface should prevent an invalid choice and explain the restriction where it applies. Do not wait until the end of a long journey through the tree.
A destination can also change while the dialog is open. Someone might delete, move or rename the folder. On confirmation, the system needs to check whether the operation is currently possible. If Marta has to choose again, preserve her selected photographs and explain why she has returned. Creating a folder in the dialog deserves the same care: after saving its new name, show its parent, not just “Folder created”. Otherwise a correctly named folder may end up on the wrong branch.
Someone using a keyboard should be able to expand a branch, select and check a destination, and cancel the whole action. On a small screen, moving deeper must not remove the route back to the parent folder. An alternative to dragging (in Polish) should reach the same destination, not a reduced selection of nearby folders. Dragging can remain a quick route for people who use it.
In an Aeneia Design library project, the destination picker can be designed together with names, messages and the final view. A small example of a real structure, including similar names, is useful input. Redrawing a perfect tree with five empty folders will not expose the problems of a team working on several collections.

Show access changes before the click
Suppose the working folder is available only to the studio team, while the destination is shared with the shop. Before moving, Marta needs to know whether the partner will gain access to the photographs. The reverse matters too: moving to another area may remove access from people who relied on permissions inherited from the source folder.
Google describes how moving material into a shared drive can remove access for people outside that drive and does not carry over permissions inherited from folders. That concerns a particular My Drive and shared-drive scenario. Your own product needs a confirmed rule for its system, not a general promise that “access will stay the same”.
The designer needs an answer about which changes can be identified reliably before the operation. When the system knows who will gain or lose access, it can show a clear summary. When it cannot tell, it should not invent a complete list. The message should state the specific uncertainty and how to check sharing, rather than reassuring people about the safety of the entire action.
Do not reduce the information to a padlock colour. “Access for the shop team” helps people recognise the audience. “Public” and “people with the link” must match the service's actual access model. Information about the folder is not enough if an individual file retains different rules. Show such an exception in the design and decide where someone can check it.
Separate access from whether a link works. The same address may lead to a file that its recipient can no longer open. A new address may instead mean replacing an earlier link in existing materials. Do not promise that every address will survive a move. In testing, save a specific link from before the change and check it afterwards from the appropriate account, within the scope of the solution being commissioned.
Marta need not receive a long warning every time she moves a photograph within the same area. The design can vary the summary according to the effect. A more consequential change should be more visible than routine reorganisation. A wall of text repeated for every small action soon stops being information and becomes furniture to walk around.
Aeneia Design
Prepare the library structure and confirmed sharing rules. Let us design the folder picker, access-change message and move result, including cases where some files remain in place.
Discuss moving files in your library ↗
Four files do not always produce one result
Show the selection before the operation starts. Marta may have selected photographs on two pages of a list and then changed the filter. The dialog should show the set actually included and let her check the names. The number “4” alone does not explain whether it includes items now out of view. Keep the same file identities in the summary. Row position alone is not enough: after a move and a new sort, a completely different photograph may occupy that number.
The destination already contains a photograph called “wazon-bialy.jpg”. Asking only “Replace?” does not allow a comparison. Show distinguishing information, such as a preview and modification time, if reliable. People need to know which object will be kept and what will happen to the other. Identical names do not prove identical content.
Possible choices depend on the product: keep both under different names, skip, replace, or save another version. Do not treat these as interchangeable labels for the same button. If a decision will apply to every subsequent conflict, show its scope. With different file types, applying a bulk rule may need further limits.
Suppose two photographs moved, a third is waiting for a name conflict to be resolved, and the fourth cannot leave the source folder. “Something went wrong” conceals the completed part. “Done” conceals the remaining work. The result should separate these groups and let Marta reach each photograph. The totals in the summary must account for all four selected files.
Retry the right scope. Pressing “Try again” should not create extra copies of the two photographs already moved. If a confirmation was lost, the system may first need to establish the actual state. The design should distinguish no response from a confirmed refusal. A similar distinction appears in uploading attachments and making corrections (in Polish).
If the operation starts from a command palette (in Polish), its result should lead to the same summary. A quick entry point does not remove the need to show the destination and effect. For a long operation, people also need a way back to the result after closing the dialog.
Separate “Close” and “Stop” if they have different effects. Closing the summary may leave work in progress. Stopping does not necessarily undo two moves that have already completed. The message should say what stopped, what was done and what still awaits confirmation. When finished, provide a route to the destination folder, but keep access to the list of items that stayed in the source. Marta should not have to reconstruct the difference from memory or compare two folders in separate windows.
Undoing a move needs a separate decision. Another photograph with that name may have appeared in the source folder in the meantime, and access may have changed. The principles of recovering the right item (in Polish) help identify the object, but the library's actual behaviour must determine whether a move can be reversed. An “Undo” button should not promise to restore the entire history of collaboration.
A small, deliberately awkward set is enough to start acceptance testing: similarly named folders, one name conflict and a file with different access. Move it by the supported routes, check the old links and inspect the recipient's view. Success for Marta means finding all four correct photographs in the correct state. Four rows disappearing from the working folder is only the start of checking.







