Some sort of permission model so the head scout can control who edits what

[SUPERCILEX]

Internally, we've seen issues where newer scouts edit the template or delete scouts. There should be a way to limit that kind of editing access to the head scout.

[SUPERCILEX]

After several competitions, I've concluded that a simple setting to hide access to the template editor is enough—most members are simply poking around, meaning there's no need for password protection or anything like that.

Now, a member would have to intentionally enable template editing to change stuff which ensures they're most likely supposed to be doing so (otherwise, a mild repremant will do the trick 😉).