Move content to a folder without changing access

A team lead at an insurance agency wants to move a quoting-basics draft from her private drafts into the New Hires folder. Last time someone moved a file, a folder-level share exposed an unreviewed draft to the whole office. She wants the identity, links and permission change shown before the move happens.

A draft moves to the New Hires folder with its identity and links retained where the product supports it.

• Select the item in the Web workspace, choose Move, and pick the destination folder.
• Elvina shows how permissions would change through folder inheritance and which references point to the item.
• Confirm; the item keeps its identity and links where the product supports it.
• The Learning Platform records the move in the audit log.

A fictional agency, Keystone Insurance Partners, has a draft called Quoting Basics in a Drafts folder visible only to its author. The team lead moves it to New Hires, a folder shared with three onboarding mentors, and reviews the permission preview first.

• The item kept its ID, and two links from a checklist still opened it after the move.
• The permission preview showed three additional people would gain view access; the lead confirmed knowingly.
• The move was logged with actor and time.

Verify permission inheritance and broken references. A folder move should not be used as an unreviewed sharing action.

• The item ID is unchanged after the move.
• Existing links resolve to the moved item.
• The permission difference was displayed before confirmation.
• Assignments tied to the item are unaffected.
• An audit entry exists for the move.

A move is organization, not a sharing decision; if a destination folder widens access, Elvina shows it, but the person decides. Learner data does not move with content. Some link types may need updating depending on your workspace setup. Confirm inheritance rules with your administrator before moving compliance material.