This wiki has had no edits or log actions made within the last 45 days and has been automatically marked as inactive. If you would like to prevent this wiki from being closed, please start showing signs of activity here. If there are no signs of this wiki being used within the next 15 days, this wiki will be closed in accordance to the Dormancy Policy (which all wiki founders accept when requesting a wiki). If this wiki is closed and no one reopens it 135 days from now, this wiki will become eligible for deletion. Note: If you are a bureaucrat, you can go to Special:ManageWiki and uncheck "inactive" yourself.

Wiki Administration: Difference between revisions

From Bristol Student Housing Co-operative
Content added Content deleted
(Created page with "This wiki runs on the [https://www.mediawiki.org MediaWiki] software and is hosted by [https://miraheze.org/ Miraheze]. The [https://meta.miraheze.org/wiki/User_groups#Bureaucrats bureaucrat] is the BristolSHC user, which is linked to the co-op email address and can be accessed by all members. == Permissions == Only users in the administrator group are permitted to create and edit pages. Additionally, the wiki is set as [https://meta.miraheze.org/w...")
 
mNo edit summary
Line 4: Line 4:
== Permissions ==
== Permissions ==


Only users in the administrator group are permitted to create and edit pages. Additionally, the wiki is set as [https://meta.miraheze.org/wiki/Private_wikis private], so only administrators can view pages in the Private [https://www.mediawiki.org/wiki/Help:Namespaces namespace] (pages with titles starting with "Private:"). This is because some pages may contain personal information or details of communications which we don't have permission to release publicly.
Only users in the administrator group are permitted to create and edit pages because the wiki is intended as a web presence for the co-op, and as a tool for internal organisation. Additionally, only administrators can view pages in the Private [https://www.mediawiki.org/wiki/Help:Namespaces namespace] (pages with titles starting with "Private:") because some pages may contain personal information or details of communications which we don't have permission to release publicly.


To give a member access:
To give a member access:
Line 13: Line 13:
* Add them to the <code>administrator</code> group
* Add them to the <code>administrator</code> group
* They can now log in at [[Special:UserLogin]]
* They can now log in at [[Special:UserLogin]]


=== Details ===

Most permissions for the <code>(everyone)</code> and <code>user</code> groups were removed on [[Special:ManageWiki/permission]], and those permissions added explicitly to the <code>administrator</code> group. The wiki is set as [https://meta.miraheze.org/wiki/Private_wikis private], and all pages not starting with "Private:" are whitelisted in [[Special:ManageWiki/settings#mw-section-permissions]] to allow public viewing of most pages.

Revision as of 19:49, 31 December 2022

This wiki runs on the MediaWiki software and is hosted by Miraheze. The bureaucrat is the BristolSHC user, which is linked to the co-op email address and can be accessed by all members.


Permissions

Only users in the administrator group are permitted to create and edit pages because the wiki is intended as a web presence for the co-op, and as a tool for internal organisation. Additionally, only administrators can view pages in the Private namespace (pages with titles starting with "Private:") because some pages may contain personal information or details of communications which we don't have permission to release publicly.

To give a member access:


Details

Most permissions for the (everyone) and user groups were removed on Special:ManageWiki/permission, and those permissions added explicitly to the administrator group. The wiki is set as private, and all pages not starting with "Private:" are whitelisted in Special:ManageWiki/settings#mw-section-permissions to allow public viewing of most pages.

Cookies help us deliver our services. By using our services, you agree to our use of cookies.