Echoes of the Flesh:Access levels

This page summarizes how access works on the Sarkic Cults Wiki. For the exact live rights list, see Special:ListGroupRights.

Access model

The public areas of the wiki are readable by everyone. The Gatekeep workspace is restricted to the gatekeep and sysop groups. Editing is split by role, by namespace protection, and in some cases by page-level protection.

Public reading

Everyone, including visitors who are not logged in, can read the public namespaces and create an account. This does not include Gatekeep: or Gatekeep_talk:.

Discussion and personal space

Logged-in users can create and edit talk pages, manage their account settings and maintain watchlists. They can edit existing unprotected personal-space pages, including their own existing CSS/JS/JSON subpages. Creating a new non-talk page still requires the separate page-creation right, normally supplied by verified membership or a staff role.

Content namespaces

The main content areas of the wiki require the content-edit right. In practice, this means verified members and above can edit most wiki content, while ordinary registered accounts cannot.

Protected content areas currently include:

• Main namespace
• Project namespace
• File namespace
• Help namespace
• Category namespace

Special protected areas

Some parts of the wiki use higher trust levels:

• Template and Form pages require the template-edit right.
• MediaWiki interface messages and Lua Module pages require editinterface (normally interface administrators or sysops).
• Site CSS/JS/JSON additionally require the corresponding site-code right. Sysop alone can edit ordinary interface messages and site JSON, but does not grant site CSS/JS editing on this wiki; interface-admin supplies those rights.
• Editing your own existing personal CSS/JS/JSON uses the corresponding own-user-code right. Editing another user’s CSS/JS/JSON requires the corresponding other-user-code right; editinterface alone is not sufficient.
• The custom Solomonari namespace requires the solomonari right.
• The custom CotRH namespace requires the cotrh right.
• Some individually protected pages may also require the solomonari_hr or cotrh_hr rights.

Group summary

Unregistered members

Unregistered visitors can read the public namespaces and create an account. They cannot edit pages or upload files.

Registered members

Registered members can:

• Create and edit talk pages, and edit existing unprotected discussion/personal-space pages
• Mark minor edits
• Manage preferences, private account information, and watchlists
• Edit their own existing user CSS, JS, and JSON pages (new non-talk pages still require page-creation permission)
• Send email through the wiki when enabled

Registered members cannot:

• Edit protected content namespaces
• Create regular content pages
• Upload or reupload files
• Move pages or files

Verified members

Verified members are trusted contributors who have been approved by staff. They can:

• Edit the normally protected Main, Project, File, Help and Category namespaces; individually protected pages can require additional rights
• Create content pages
• Upload and reupload local files
• Move pages and files
• Edit semiprotected pages
• Purge pages

This is the normal contributor role for members who are actively helping with the wiki.

Solomonari

Solomonari is a separate access flag for editing existing pages in the custom Solomonari namespace. It does not automatically grant verified, upload or new-page creation rights. Creating a new Solomonari page normally needs verified (or an equivalent staff role) as well as the namespace flag.

CotRH

CotRH is a separate access flag for editing existing pages in the custom CotRH namespace. It does not automatically grant verified, upload or new-page creation rights. Creating a new CotRH page normally needs verified (or an equivalent staff role) as well as the namespace flag.

Solomonari_HR

Solomonari_HR is a separate page-protection access flag. It is intended for individually protected high-restriction pages and does not, by itself, grant the normal contributor or staff permissions ladder. The HR flag does not include the base namespace flag; editing an HR-protected Solomonari page requires both. It can grant and remove the solomonari group.

CotRH_HR

CotRH_HR is a separate page-protection access flag. It is intended for individually protected high-restriction pages and does not, by itself, grant the normal contributor or staff permissions ladder. The HR flag does not include the base namespace flag; editing an HR-protected CotRH page requires both. It can grant and remove the cotrh group.

Gatekeep

The gatekeep group gives access to the private lore workspace:

• Gatekeep: (namespace 3004): lore dumps, work-in-progress concepts and private drafts.
• Gatekeep_talk: (namespace 3005): discussions about those drafts.

Only members of gatekeep or sysop can read pages in either namespace. Verified, moderator, maintainer, interface-admin, bureaucrat and bot membership do not independently give read access. Groups combine: someone who is also a gatekeep member can read them.

Gatekeep members can create and edit pages in both namespaces using the gatekeep-edit right. The group does not grant public content-editing, uploads or staff tools. Ordinary page protection and account blocks still apply. Moving pages within the workspace follows existing move permissions; moving a private page into a public namespace requires sysop.

Sysops can grant and remove the gatekeep group through Special:UserRights. Bureaucrats retain their existing unrestricted group-management right and can also assign it. Editorial roles are not delegated management of this group. No one is automatically added to gatekeep.

Workspace boundaries

Use the standard wiki editor for Gatekeep pages. Page Forms editing and private-page preloads are unavailable in this workspace.

Use the namespace prefix when creating a private page, for example Gatekeep:Your draft. The corresponding talk namespace accepts Gatekeep_talk: (displayed as “Gatekeep talk”). Private pages cannot be transcluded, substituted or read with Lua title-content helpers, including by authorized editors; this prevents their text being included in public pages or parser caches. Public Cargo data storage and Discord activity messages are disabled for these namespaces. Authorized members can search the workspace by selecting its namespace; it is excluded from the default search.

The restriction protects page content, including normal source, history/diff and API reads. It does not make page titles, authors, timestamps or edit summaries secret: they can still appear in public wiki listings and logs. Keep sensitive information out of titles and summaries. Categories are organizational tools, not privacy boundaries. Uploaded files remain in the public File namespace; linking one from Gatekeep does not make the file private. Moving previously public material here cannot withdraw copies already published elsewhere.

Gatekeep:TEST and Gatekeep_talk:TEST contain harmless placeholder text for access checks. Server-side maintenance created these as DivošiRunner without adding the account to gatekeep.

Moderators

Moderators have all verified member permissions, plus day-to-day workflow and trust-management tools. They can:

• Patrol and autopatrol edits
• Roll back vandalism or bad edits
• Suppress redirects when moving pages
• Bypass CAPTCHA where needed
• Manage certain user group assignments
• Grant and remove the verified, solomonari, solomonari_hr, cotrh, and cotrh_hr groups

Flow is disabled following the upgrade. Retained Flow-named rights do not make Structured Discussions available.

Moderators are intended to handle routine content review and contributor verification, not heavy administrative maintenance.

Maintainers

Maintainers have all moderator permissions, plus broader maintenance and administrative tooling. They can:

• Protect pages and edit protected pages
• Edit templates and forms
• Edit restricted fields and selected advanced content models
• Block users
• Upload by URL and reupload shared files
• Run Cargo queries and rebuild Cargo data
• View AbuseFilter logs available to this role
• Use selected advanced extension maintenance tools
• Grant and remove the moderator group in addition to verified, solomonari, solomonari_hr, cotrh, and cotrh_hr

Maintainers are the main high-trust content and operations role on this wiki. TemplateStyles in the Template namespace follow template permissions. Maintainer alone does not permit editing Lua modules or MediaWiki interface messages; those need an interface-administration role. Individual page protection and extension-specific requirements still apply.

Interface administrators

Interface administrators can edit site interface content, including MediaWiki pages and site/user CSS, JS, and JSON. This role is restricted because interface pages can affect the whole wiki.

Administrators (sysop)

Administrators have broad site administration permissions, including deletion, blocking, protection and the custom namespace rights. Sysop is the general administration role; site CSS/JS and other users’ CSS/JS still require interface-admin. Sysop alone does not grant unrestricted user-group management; it is delegated grant/removal of the gatekeep group and can read/edit the Gatekeep workspace.

Bureaucrats

Bureaucrats have unrestricted userrights under the current configuration. This allows management of all available local groups, not only the groups below. The configured delegation list is therefore not a restriction while that right is granted. Its listed operational groups are:

• verified
• solomonari
• solomonari_hr
• cotrh
• cotrh_hr
• moderator
• maintainer
• interface-admin
• sysop
• gatekeep

Bots

Bots are automated or semi-automated accounts with raised API limits, bot marking and selected automation exemptions. Bot membership alone does not grant content-editing, upload, template, module or custom-namespace access. A bot needs the relevant contributor/namespace/staff groups for ordinary API or web edits. The bot role is assigned manually. Official server-side maintenance tools may use an explicitly selected revision author without granting that account additional web/API rights.

Page protection and account security

Group rights combine; membership in one role does not remove rights granted by another. Namespace restrictions, individual page protection and account blocks are checked in addition to the role’s rights. The Main Page currently has cascading sysop-level edit protection, so verified or moderator membership alone cannot edit it; maintainers/sysops have the required protected-page rights. Pages transcluded there may inherit its protection.

Two-factor authentication is configured as required for moderator, maintainer, interface-admin and sysop groups. Bureaucrat alone is not in that required-group list; however, all current bureaucrat accounts also belong to a listed group. Enrolment and login enforcement are separate from this permissions reference; this page does not certify an individual account’s authentication setup.

For access problems, check your preferences and group membership, the namespace and the page’s protection. Ask through Discord or use the talk page to request an edit. Do not share passwords, bot passwords or authentication codes.

Legacy role names

The former Editor and Trusted page links now lead to the Verified contributor guidance. They are navigation aliases; they do not create, rename or assign user groups.

Practical summary

• Want to read public wiki content: no account needed.
• Want to read or work on private Gatekeep drafts: you need gatekeep or sysop.
• Want to discuss or maintain existing personal pages/account settings: a normal registered account is enough; new non-talk pages need page-creation permission.
• Want to edit articles, files, and core content: you need the verified group.
• Want access to the Solomonari namespace: you need the solomonari group.
• Want access to the CotRH namespace: you need the cotrh group.
• Want access to HR-protected pages: you need both the matching base namespace flag and solomonari_hr or cotrh_hr flag.
• Want to moderate contributors and review content workflow: moderator.
• Want to maintain templates, forms, and higher-trust wiki operations: maintainer.
• Want to edit Lua modules or ordinary interface messages: the required interface-editing role.
• Want to edit sitewide CSS/JS: interface administrator.

See Help:Editing guide for editing steps and Echoes of the Flesh:Templates for using existing templates. This documentation describes the configuration checked on 5 October 2026; Special:ListGroupRights is the live rights reference.