Application: Twinny

[Twinny]

Thought I might just add a new piece to my work. For my playerworld policies, I'd also like to enforce basic playerworld staff structure.

It's foolish to have about 1 manager and 5 co-managers (which doesn't make sense, "co" wise but happens anyways) and a whole pile of staff with unnecessary rights.

I'd like to be able to establish a working staff system that ensures only the manager and perhaps one or two high, trusted and verified admins can change rights whilst everyone else only gets the bare minimum rights.

For example, instead of having all LATs with access to the gmap, each should only have access to their folder where they can upload test levels. Once approved by someone high up (lat admin, manager) the level can then be moved across to the main levels folder. This practice would limit damage made to gmaps through errors and abuse/deletion). Just a small part of the policy i'd like to implement.

[cbk1994]

Originally Posted by Twinny

For example, instead of having all LATs with access to the gmap, each should only have access to their folder where they can upload test levels. Once approved by someone high up (lat admin, manager) the level can then be moved across to the main levels folder. This practice would limit damage made to gmaps through errors and abuse/deletion). Just a small part of the policy i'd like to implement.

Sounds fine, but would never work on UC servers.

[Twinny]

Originally Posted by cbkbud

Sounds fine, but would never work on UC servers.

May only end up being guidelines but PWAs should help implement them on a server if requested

[coreys]

Originally Posted by cbkbud

Sounds fine, but would never work on UC servers.

I think it should be enforced completely on Classic tab servers.

And Twinny, you have my support.

[Tigairius]

Originally Posted by Twinny

Thought I might just add a new piece to my work. For my playerworld policies, I'd also like to enforce basic playerworld staff structure.

It's foolish to have about 1 manager and 5 co-managers (which doesn't make sense, "co" wise but happens anyways) and a whole pile of staff with unnecessary rights.

I'd like to be able to establish a working staff system that ensures only the manager and perhaps one or two high, trusted and verified admins can change rights whilst everyone else only gets the bare minimum rights.

For example, instead of having all LATs with access to the gmap, each should only have access to their folder where they can upload test levels. Once approved by someone high up (lat admin, manager) the level can then be moved across to the main levels folder. This practice would limit damage made to gmaps through errors and abuse/deletion). Just a small part of the policy i'd like to implement.

Well, the PWA already tried doing that but it didn't work out very well. It's still somewhat enforced and generally if someone has too many unnecessary rights then they will confront a manager or someone in charge. It would be difficult to establish an actual system for that without completely controlling the staff list of each server. The managers should be responsible enough to know which staff they're able to trust and which staff they aren't able to trust. When you hire someone you're taking a risk of trust, it's the managers job to decide whether or not that risk is worth taking.