Due to the recent occurances with the deletion of all the data on the server, It is clear to me that we need some kind of possition to help backup the server, and keep those backups secure while still being easy to access, I propose that we introduce an "Archiver" position. This role, unlike other high position roles, would go to whoever the owner deams is most trustworthy and most capeable of the task, regardless of rank (Basicly, you don't have to be an admin to become the Archiver)
This is my idea for how this possition would work:
-
Would act semi-similar to the System Administrator role
-
Would be appointed by the owner, as they must be trusted to have access to everything in the server. However, this would only be done after discussing if the person in question is fit for the role with the executive team
-
Would have full access to the server files (possibly no write access, only read)
-
Would make copies of the entirety of the servers files every week
The Archiver Position will also be responsable for following these procedures, so as not to risk the leak of server files and user data to those who shouldn't have access to it:
-
All the backups must be dated with the following structure: "M/D/Y Server Files" where M is month, D is day, and Y is year (e.g. if a backup was done on the 26th of October, In the year 2020, the file would be named "10/26/2020 Server Files")
-
The backups must be locked by a Password, this password would be help by the Archiver, and only the archiver
-
The Archiver Is only allowed to send backups to other users of the server if it is absolutely neccisary, and must never make these backups public for everyone.
-
If the Archiver needs to send backups to another user, they must first make a copy of the file that they need to transfer, and then change this password to something completely different from what the other server files password is, no password can be the same for these transfers.
-
Whevever the Archiver sends a backup to somebody, they must notify the owner, and all of the executives that they have sent these files, even if the person the files are being sent to are the owner or an executive. The Archiver must tell them who the files were sent to, which files were sent, and must also give a reason for the transfer.
-
The Archiver would also not be allowed to Modify and of the server backups unless explicitly permitted to do so by the owner. should the archiver wish to modify any server backups for their own use, they may make a copy of the backup and may modify the copy, but not the origional
-
Under any circumstance, If something accurs to the main server files, and a backup is needed, the Archiver is responsible for getting the most recent backup of the server files to whoever is the owner, If there is no owner at the time, they must send the files to the EAO, if neither of these roles are filled, they must send it to whoever they deem is most able to recover the server
On top of this, the following must be considered by all of the executive team and the owner:
-
Should there ever be a leak of the server files, the Archiver should be put under investigation for the distribution of files
-
If the Archiver is found to break the previously mentioned procedures without good reason (as deamed by a decision from the owner and executive team), they must be immediately removed, and must be blocked from any access to the main server files. After this, an announcement must be made by the owner stating that the archiver was removed and also stating what went wrong
-
Additionaly, if the archiver, for whatever reason, finds themselves indeffinitly banned from the server, they will be removed from their role as archiver, and a new archiver would be appointed. It is important to note that if a previously removed archiver was removed for this reason, and then became unbanned, they are eligable for getting the role again, provided that the owner and executives decide to appoint them again.
-
If the owner, or an executive wishes to remove the Archiver and appoint a new one, but the current archiver isn't able to be removed for the above reasons, they can be removed if, and only if, the owner and executive team come to an agreement about the removal of the current archiver and the appointment of a new one.
