NOTICE:
This is a sandbox page.
It is not approved or active policy. It is a draft, and as such, may be incomplete.
Congratulations! You have just been hired as the head of a nuclear reactor. Your abilities and public trust have gotten you far.
As the new head, you have keys that let you into nearly every part of the facility. Now imagine, as you walk around the grounds, you decide to let yourself into the reactor's main control room. There are so many knobs, dials and switches!
You should totally mess with them. See what these cool buttons do. What's the worst that could happen?
A story about the Wikidot admin panel.
Admin Onboarding Guide
|
Table of Contents
|
This page serves as a reference for all responsibilities and tasks that are shared between the admin team as a whole, including step-by-step instructions, and important details to keep in mind.
General Admin Tasks
The following section outlines admin tasks, gives instructions on how to do them, and serves as a reference guide.
Running Bans/Revokes
As an admin, you are now able to revoke membership from the wiki, and ban users. Yay! If you aren't scared, you should be — Wikidot is a complex beast, and wrangling it is half the battle.
Relevant Resources: An incredibly helpful tool is the Easy Ban Script, which means you don't have to do this manually! Yay! But, in the event that it doesn't work, the following steps are a guide on how to execute a revoke/ban from the Wiki.
Manual Site Bans
The easiest way to ban somebody is if the user is flagged — this can be done by any user, from the profile, choosing to 'flag as abusive'. Once this is done, you are ready to begin the ban process:
- From your Wikidot profile, under Sites, open the admin panel for the SCP Wiki.
- Once open, navigate to the 'Security' tab.
- From the security tab, select 'Abuse'.
- From there, select 'User Reports' (The third option). This displays a list of all users who have been flagged as abusive.
- Copy the flagged user's username, you will be using this in the next step.
- While still in the Admin Panel and Security Tab, select the 'Blocks' tab. This will show a list of all banned users.
- At the top of the list, select the green 'Add' button.
- Once the ban window has opened, paste in the username of the user in question.
- Fill out the ban reason appropriately; it is very important to ensure you do this, otherwise it will have to be fixed after the fact. (When filling out the ban date, please fill them as DD Month YYYY, ie: 23 June 2025.)
- Once everything is filled out, press 'Block' and the ban will be completed.
- Now that the user is banned, you must PM them, informing them of the ban, duration, and the reasons why.
- Additionally, you are responsible for ensuring that the action is noted as such in relevant o5 thread (most often the disciplinary records). If the user has an existing thread, reply to it with the ban reason and duration. If there is no pre-existing thread for the user, make a new one.
Once that is done, note that the ban has been handled in the relevant thread/chat, and you are done!
Manual Revokes
The easiest way to revoke membership from a user is if the user is flagged — this can be done by any user, from the profile, choosing to 'flag as abusive'. Once this is done, you are ready to begin the revoke process:
Using The Abuse Panel
If the user has been flagged, they can be revoked with the following steps:
- From your Wikidot profile, under Sites, open the admin panel for the SCP Wiki.
- Once open, navigate to the 'Security' tab.
- From the security tab, select 'Abuse'.
- From there, select 'User Reports' (The third option). This displays a list of all users who have been flagged as abusive.
- Find the user you are revoking. Choose 'remove, and the revoke will be executed.
- Now that the user is revoked, you must PM them, informing them of the revoke, and the reasons why.
- Additionally, you are responsible for ensuring that the action is noted as such in relevant o5 thread (most often the disciplinary records). If the user has an existing thread, reply to it with the revoke reason. In most cases there will not be a pre-existing thread, so, in that case, make a new one.
Using The Member List
The second option for revoking membership is using the members panel. This is a worse option, as not only do you need to identify the user's join date, you need to navigate to that tab of the list. Note: This guide is written with the assumption that you have installed the More User Info Script and the Find Member Script, otherwise, you will need to find the user manually.
- Open the wikidot profile for the user, and find the user's Site join date by clicking their name on the site. A modal box will open, listing the site join date. Copy that.
- From your Wikidot profile, under Sites, open the admin panel for the SCP Wiki.
- Once open, navigate to the 'Members' tab.
- From the members tab, select 'Members List'.
- An additional search bar should appear, if you have the Find Member script installed correctly. Paste in the user's join date, and click 'Search'. This will navigate to the page the user is listed on.
- From the members tab, select 'Members List'.
- Scroll down to the member in question, and select 'Options'.
- Click 'Remove', and the revoke will be implemented.
- Now that the user is revoked, you must PM them, informing them of the revoke, and the reasons why.
- Additionally, you are responsible for ensuring that the action is noted as such in relevant o5 thread (most often the disciplinary records). If the user has an existing thread, reply to it with the revoke reason. In most cases there will not be a pre-existing thread, so, in that case, make a new one.
Revoke/Ban Templates:
The following are templates that can be used when creating your O5 threads, and PMing users accordingly:
AI Revoke O5 Thread Template:
Noting that site member [[*user NAME]] (account age days, site membership days) recently posted a page that contains indicators of AI-generation: [link here]
[[collapsible]]
[[code]]
[[/code]]
[[/collapsible]]
Excerpts of note:
>
Membership revoked, PM sent. AI TEAM MEMBER NAMES supporting.
AI PM Template:
This is a notification from the SCP Foundation wiki. As you submitted AI-generated content to the site, your membership has been revoked. All AI-generated and AI-assisted content is not permitted on the SCP wiki, including use of AI to reword or revise material, use of AI to generate images which an artist then traces, and use of AI to produce content that an author then adds surface edits to.
If inclined, you may re-apply for membership in 24 hours.
Ban O5 Thread Template:
Noting that [[*user NAME]] (account age XXX days, site membership XXX days) was recently issued a ban for [[INSERT REASON(S)]]
[[PROVIDE ANY FURTHER CONTEXT, QUOTATIONS, OR DETAILS AS NEEDED]].
Due to the above, staff voted to enact a [[DURATION]] ban for [[REASON]]. [[LIST DISCIPLINARY VOTERS]].
Permaban enacted, PM sent.
Note: If the information was raised to staff by a user, replace 'Noting that' with:
It was brought to staff attention that
Ban PM Template:
You have been banned from the SCP Foundation Wiki for BAN REASON, for DURATION. An appeal is available to you by replying to this PM or by [https://scp-sandbox-3.wikidot.com/chat-guide joining #site17 on SkipIRC]. If you have any questions, you may contact me or another member of the Disciplinary Team.
REPLACE ME
SCP Foundation Wiki, Disciplinary Team
Processing Wiki Applications
While, at first glance, processing Wiki Applications may seem simple in just checking the password matches, in reality, it is a much more complex beast to untangle. The following section highlights step-by-step best practices for processing applications, uncommon application rejection reasons, and more.
Step-By-Step Application Processing Best Practices
When you are processing SCP Wiki applications, the key is being thorough; as a result, having a list of steps can be a huge help to make sure you have checked everything. The following lays out a step-by-step best practices, according to Zyn, for handling wiki apps:
- Open the admin panel for the SCP wiki.
- Once open, navigate to Members
- Next, select Applications. This will open a list of the currently pending applications.
- Once you are on the right page, grab the password and then Find (Control-F) the current password. The easiest way to begin is by handling the standard rejections.
- Going down the applications list, look for the applications that do not match the current password.
- For each incorrect application, grab both the username, and the text of the application. These should be logged in the Discord. Note:If the password is incorrect by missing a word, or the like, it is still rejected, but does not count towards the maturity ban minimum, and is not logged. If only a period is missing at the end, it is considered acceptable.
- In the Discord, paste both the text, and username.
- Once you have copied the information over, return to the admin tab and press decline. A window will pop up, asking if you want to add a reason to the decline - this does nothing, and can be safely ignored. Instead, click Send Decision, and it will be declined.
- Track how many applications you have declined, so that you can provide the information in the Discord.
- For each incorrect application, grab both the username, and the text of the application. These should be logged in the Discord. Note:If the password is incorrect by missing a word, or the like, it is still rejected, but does not count towards the maturity ban minimum, and is not logged. If only a period is missing at the end, it is considered acceptable.
- Once you have caught all overtly incorrect passwords, begin by going through all of the usernames, to look for slurs, dogwhistles, NSFW content, or the like.
- If you find a username that is against the rules, decline the application, and note the reason in discord as 'for name'. Ban as/if needed, following the above steps.
- Username declines should also be logged in the Username Log.
- If you find a username that is against the rules, decline the application, and note the reason in discord as 'for name'. Ban as/if needed, following the above steps.
- Once all usernames have been checked, begin to look for the rest of the Uncommon Application rejection reasons.
- To start, in batches of ~5, right click the user's name, and open their profile in a new tab. (Note: This next step requires the More User Info Script, so be sure to install that.)
- Click Site Member Modal: Open Dialog, and check to see if there is any inappropriate content in their 'About' field. You can check their icon at the same time.
- Next, check the sites they are members/admins of. Look for hostile sites, or ones indicative of vandalism.
- Finally, check their recent contributions/recent posts and comments — look for any overt red flags, or problematic posts.
- Specifically, check any sandbox pages for AI usage.
- Bonus Tip: If you see a Mnemosyne link, you can check their Discord profile in the main discord server, via command.
- If any of the Uncommon Application rejection reasons were met, note the username and specific reason in the Discord, and decline the application.
- To start, in batches of ~5, right click the user's name, and open their profile in a new tab. (Note: This next step requires the More User Info Script, so be sure to install that.)
- Finally, once you have checked all of the above, you can accept the application. A modal window will appear, and click send decision. Note the number of applications you accepted, for noting in discord.
- Rinse and repeat until all applications have been processed! Post the message, and then do any clean-up needed (see next block).
Applications Cleanup
Once you've processed the pending applications, there is still a bit of cleanup that needs to be done. Specifically, check if any users are at 4 failed applications and insert more if there is.
Common Application Rejection Reasons
The following items are the most common reasons for rejecting an application to the SCP Wiki:| Reason | Summary | Link to Documentation |
|---|---|---|
| Incorrect Password | The password provided does not exactly match the current password. | N/A |
| AI Generated | The password provided shows signs of being AI Generated. | AI Application Log |
Uncommon Application Rejection Reasons
The following items are uncommon reasons for rejecting an application to the SCP Wiki. When processing applications, it is important to be thorough in verifying a user's profile. Each item in the table below is a valid reason to decline an application:
| Reason | Summary | Link To Documentation |
|---|---|---|
| Disallowed Username | The user's username violates the rules regarding acceptable names. (IE: 'SCP', Foundation characters, positions of authority, etc.) | Rejected Username Log |
| NSFW Icon | The user's account icon contains NSFW content (IE. Graphic Sex Scenes, Topless Women, Characters from Porn Games etc.) | N/A |
| Roleplay Profile | The user has roleplay content in their profile (IE. 'I'm a Level-4 admin of Site-17, ask me your questions in PMs!') | N/A |
| Underage | The user's profile indicates they are not of age to join the site. | Because the users are underage, this is not tracked on O5 |
| Age Discrepancy | The user has an age discrepancy somewhere on their profile/application (IE. their profile lists a date of birth that doesn't match what their "About Me" and/or application says) | N/A |
| Hostile Site Member | The user is currently a member of a know hostile site or a similar site | N/A |
| Troll Activity Elsewhere | The user has troll/spam/vandalism/etc. activity on other sites (IE.the user who made personal wikis for "the best fapping experience" and "miraculous ladybug porn") | N/A |
| Dogwhistle | The user's name has hate speech/a dogwhistle/any indication of bigotry | N/A |
| Sockpuppet | The user is a sockpuppet/attempting to ban evade | N/A |
| Duplicate Names | The user applied back-to-back with another account with a near-identical name (typically the same person) | N/A |
Depending on the above reasons, these may also result in immediate bans from the wiki.
Applications-Related Templates
1 Year Maturity Ban PM Template
This is a notification from the SCP Foundation wiki. As you have submitted four consecutive declined applications, you have been issued a yearlong site ban.
If you wish to appeal for the ban to be lifted or shortened, you may do so in the official Discord: https://discord.com/invite/scp or the IRC help chat: http://scp-sandbox-3.wikidot.com/chat-guide
You can also reply to this message with the text of the appeal you wish to submit.
1 Year Maturity Ban Admin Panel Template
Yearlong maturity ban due to four declined applications. [link to O5 thread here] Ban elapses # Month Year.
1 Year Maturity Ban O5 Log Template
Noting that [[*user NAME]] has NUMBER declined applications:
MM/DD/YYYY
> submitted application [with password removed, if needed]
Admin Resources
This section outlines multiple resources that are at provided to admins, to assist in their duties, and to make Wikidot easier to wrangle:
Userscripts
There are a number of userscripts that are made to enable Admins to do their tasks more efficiently. These are mentioned in high-level below, with details on https://05command.wikidot.com/user-scripts.
More User Info Script moreUserInfoScript
Link: https://github.com/scpwiki/user-info-script
Install: https://github.com/scpwiki/user-info-script/raw/refs/heads/main/user-info.user.js
Purpose: Provide additional information and convenient links on the user info page.
Find Member Script findMemberScript
Link: https://github.com/scpwiki/find-member-script
Install: https://github.com/scpwiki/find-member-script/raw/main/find-member.user.js
Purpose: Jumping to a particular user in the admin panel member list.
Delete Applications Script
Link: https://github.com/croque-scp/delete-applications
Install: https://github.com/croque-scp/delete-applications/raw/main/delete-applications.user.js
Purpose: Automatically cleaning out spammy Wikidot application messages for your inbox.
Easy Ban Script
Link: https://github.com/scpwiki/easy-ban-script
Install: https://github.com/scpwiki/easy-ban-script/raw/main/easy-ban.user.js
Purpose: Easily revoke or ban users on the site user page.