Overview
LockPass lets you reorganize your tree structure by moving a category to another location. The category moves as a single block: its passwords, their attachments and all of its subcategories follow it.
Moved passwords are not modified (name, username, password, URL, two-factor authentication code, tags, description, optional fields, attachments and dates), and each password keeps its owner.
Who can move a category?
To move a category, you need rights on the category to be moved and on the destination category. Destinations you do not have rights on are greyed out in the tree.
- Administrators and moderators: can move a category from the personal space to the personal space or to the shared space, and within the shared space (including to its root).
- Blind administrators and blind moderators: same options, except moving a personal category to the shared space. They can move a category without seeing the passwords it contains.
- Category managers (or members of a manager group): can move their personal categories, move a personal category into a shared category they manage, and move a shared category from and to categories they manage (including to the root of the shared space).
- Standard users: can only move categories within their personal space.
- External users: cannot move categories.
Good to know: the right to move passwords, set on a category, does not allow moving the category itself.
Moving a category
Using the "Move" action
- In the tree, open the menu of the relevant category and click "Move". The action is also available from the category panel.
- In the "Move "category name"" window, select the destination in the Favorites, Personal space or Shared space tree.
- Review the "Impact" panel on the right: it shows what changes for access and the password policy.
- If a category with the same name already exists at the destination, accept the name suggested in "New category name" or enter another one.
- Click "Move".
Using drag and drop
- In the tree, click and hold the relevant category.
- Drag it onto the destination category, which becomes highlighted.
- Release: the "Moving "category name"" window opens.
- Check the impact, rename the category if needed, then click "Move".
When dragging and dropping, unavailable destinations are not highlighted.
Moving a category back to the root of the shared space
- Open the menu of the relevant category and click "Move".
- In the destination tree, select "Shared space".
- Rename the category if a category with the same name already exists at the root, then click "Move".
Only a shared category can be moved back to the root of the shared space. Administrators, moderators and managers of the category can do this.
During the operation, the message "Move in progress" is displayed, followed by a confirmation message once it is complete.
What happens to a category after it is moved
Access is added, not replaced
Everyone who had access to the category keeps it. People with access to the destination category also get access to the moved category and its content. No access is removed.
Example: an "Accounting" category shared with the Finance team, moved into a "Management" category shared with the executive committee, becomes accessible to the Finance team and the executive committee.
- Moving the category back to its previous location does not remove the access added during the first move. To remove access, edit the category's access settings.
- A category moved back to the root of the shared space keeps exactly the same access, with nothing added or removed.
- People who have just been granted access see the category immediately.
The password policy follows the destination
The moved category and all of its subcategories take on the password policy of their new location:
- if your organization enforces a policy on the destination space, it applies and can no longer be changed on the moved categories;
- otherwise, they take on the policy of the destination category (or none if it has none), and this policy remains editable.
A category moved back to the root of the shared space takes on the policy enforced by the organization on the shared space, or none if the organization does not enforce one.
The policy only applies to passwords created or generated after the move. Existing passwords are neither modified nor blocked.
All or nothing
If an incident interrupts the move, the message "The move failed, no changes were made." is displayed. The category stays in its original location, with its content and access, and you can start the move again.
Moves that are not allowed
Regardless of your role, the following moves are not allowed:
- A shared category to a personal space: the personal space is greyed out. Passwords in a shared space belong to your organization's scope (controlled access, tracked views) and cannot leave it.
- A personal category directly to the root of the shared space: first move it into a category of the shared space.
- A category into itself or into one of its subcategories: these categories are greyed out.
- A category to another organization: categories from other organizations are not offered.
- Several categories at once: only one category can be moved at a time.
If the destination already contains a category with the same name, you are asked for a new name before confirming.
Viewing the move history
Administrators and moderators can find out who moved a category, from where, to where and when:
- Go to the Dashboard, "Logs" tab.
- Apply the "Category" filter.
- Open the entry for the move you are looking for.
Each entry shows the author, the date and time, the category with its origin and destination, as well as the IP address and browser used.
A move creates a single entry, at the level of the moved category: its subcategories do not have their own entry.
Updated