Elite Dangerous Wiki:User groups: Difference between revisions
Align local group rights and policy for an independent Mistflux game wiki |
m Protected "Elite Dangerous Wiki:User groups": Protect the authoritative local permissions policy ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)) |
(No difference)
| |
Latest revision as of 23:49, 31 October 2026
| This page describes local permissions on Elite Dangerous Wiki. Special:ListGroupRights lists the permissions currently enforced by the software. |
User groups organise editing, moderation and technical responsibilities. They are not ranks or ownership of articles. Membership on Fandom, Wikipedia or another wiki does not grant access here.
Editors
| Group | Eligibility | Purpose |
|---|---|---|
| Readers | Everyone | Read public pages and register an account. Anonymous editing is disabled. |
| Registered users | A registered account | Edit and create ordinary pages, participate in discussions, translate content and manage personal preferences. |
| Autoconfirmed | Four days and ten edits | Edit semi-protected pages, move ordinary pages, upload files and replace local uploads. This does not grant moderation, pending-changes review or template protection access. |
| Confirmed | Explicit administrator appointment | The same capabilities as autoconfirmed, for a contributor whose experience has been checked before the automatic threshold. |
| Extended confirmed | Thirty days and one hundred edits | Also edit extended-confirmed-protected pages. It does not grant template editing or administration. |
Accounts remain subject to page protection, blocks, abuse filters, upload restrictions and other applicable checks. File renaming, shared-file overrides, root user-page moves and category-page moves are reserved to administrators.
Appointed responsibilities
| Group | Purpose | Appointed by |
|---|---|---|
| Reviewer | Review pending changes on pages where that protection is explicitly enabled. Includes confirmed editing capabilities. | Administrator, bureaucrat or site operator |
| Template editor | Edit template-protected templates, modules and shared styles. Includes confirmed editing capabilities. Does not grant site JavaScript or CSS access. | Administrator, bureaucrat or site operator |
| Administrator | Routine moderation: blocks, deletion/restoration, protection, rollback, patrol, local abuse-filter management and file maintenance. | Bureaucrat or site operator |
| Bureaucrat | Appoint or remove administrators, approved bots and editorial specialists. No unrestricted grant power and no authority to appoint another bureaucrat, interface administrator, privacy investigator or site operator. | Site operator |
| Interface administrator | Maintain site-wide JavaScript, CSS and interface resources. This is a separate trusted technical responsibility. | Site operator |
| Bot | Approved automation using a separate account. Bot status does not give administrator access or blanket spam-blacklist bypasses. | Bureaucrat or site operator |
| Site operator | Migration/import controls, authentication recovery, bulk messaging and appointment of technical or privacy roles. Kept separate from routine moderation. | Existing site operator or server-side operator process |
Administrators can appoint or remove confirmed users, reviewers and template editors. Bureaucrats can additionally appoint or remove bots and administrators. Only site operators can appoint or remove bureaucrats, interface administrators, site operators, CheckUsers and suppressors. There are no additional self-service grant exceptions. Multiple groups contribute permissions together, so a user holding several roles retains each role's powers.
Exceptional privacy permissions
CheckUser and suppression remain separate, explicitly appointed capabilities. They are not automatically included with administrator, bureaucrat, interface administrator or site-operator membership. CheckUser includes access to protected AbuseFilter investigation variables. Suppression controls access to material hidden beyond ordinary deletion. Neither group currently has an appointed member. Appointments require a specific operational need and appropriate handling of private information.
Requests and accountability
Use Project:Requests for permissions to request an editorial role, giving the task and relevant experience. Administrators should use proportionate tools, record reasons and follow Project:Protection policy and Project:Deletion policy. Permission changes are logged. An appointment can be removed when no longer needed.
Two-factor authentication is available to registered users and is strongly recommended for every privileged account. Do not share privileged accounts or bot credentials.
Other Mistflux wikis and future shared login
These are local appointments on this wiki. A future CentralAuth service may share account identity and login across Mistflux game wikis. Shared login must not automatically make a local administrator, bureaucrat or bot privileged on every wiki. Any future global role needs its own explicit rights and wiki scope. CentralAuth is not enabled by this permissions change.