SkieHow do I copy (fork) a policy, and who owns it?
Forking makes your own editable copy of a policy, leaving the original untouched for the groups that still use it. The new copy is owned by whoever forked it, and only the owner can edit it. Use it to prepare a new batch, a new branch or a stricter exam version without risking live groups.
A policy is shared. If ten groups use the same policy and you edit it, ten groups change at once. That is useful when you really mean it, and risky when you do not. Forking gives you a safe route: copy the policy, edit the copy, then attach the copy only to the group that needs it.
Ownership follows the fork. The person or level that created a policy owns it, and ownership decides who may edit or delete it. A branch head can fork an organisation policy to adjust it for one branch, but the organisation's original stays as it was. Others can still see and attach policies they are allowed to use without being able to change them.
Forks are numbered, so a family such as 'Classroom 2026' can have a v2 for a new intake and the history stays readable. If you later want a change to reach every group, edit the owner's version and use the impact preview to confirm the reach before saving.
A practical tip: fork before every term. Take last term's policy, fork it, adjust it, and attach the copy to the new batch. If something goes wrong, the old policy is still there. Nightly backups keep earlier versions too, and a restore preview lets you see what would come back before you commit to it.