Site administration
Every site has an admin panel for its settings, accounts, roles, content structure and moderation queues. How permissions are decided is described in Roles and permissions.
The interface is currently in Chinese. Each element is described below by its English name.
Opening the admin panel
The panel is at /-/admin/ on the site's domain, for example https://wiki.example.org/-/admin/. The panel has no sign-in page of its own: signed-out visitors are sent to the site's sign-in page, and Sign out signs you out of the whole site.
Superusers, site superusers of this site, and accounts holding a role on this site with Can enter the admin panel checked, can enter the panel. Entering is only the first step. Every screen needs its own permission (see Menu and required permissions). The menu shows only the screens you may use, and the address of any other screen answers "not found".
Every screen shows notices about pwikit updates at the top. Superusers can update now, postpone or skip the release from there; see Updating.
The first administrator
A new instance has no accounts. Create the first administrator on the command line:
pwikit admin create -name "Site Admin"If you are importing a Wikidot site, import it first and then run pwikit admin create with your Wikidot name, so the imported account and its pages stay yours. See Command line and Importing from Wikidot. pwikit admin grant and pwikit admin revoke give and remove superuser rights on existing accounts.
IMPORTANT
Soon after signing in, set Role after sign-up and Role after claiming; on a new site you can pick the member role it starts with. See Registration and accounts. Members who join before that hold only registered and cannot edit pages. Adjust the member and admin roles a new site starts with to match your site's rules soon as well; see Built-in roles.
Superusers and roles
| Superuser | Site superuser | Account with roles | |
|---|---|---|---|
| Scope | Every site on the instance | This site only | Only the site where the roles are held |
| Permissions | All of them, regardless of roles | All of them on this site, regardless of roles | The sum of its roles' permissions |
| Admin panel | Always allowed in | Allowed into this site's panel | Needs a role with Can enter the admin panel |
| The account itself | Can change usernames and email addresses, deactivate accounts and so on | Cannot | Cannot |
| Sign-in and address records | Can see an account's last login, latest IP and Suspicious activity | Hidden | Hidden, whatever the permissions |
| Full conversations behind message reports | Can read every private message between the two accounts in User reports | See only the messages the reporter chose to send | See only the messages the reporter chose to send |
| Can be edited by | Only another superuser can change the superuser flag or its roles | Superusers and site superusers can change the flag, roles and sanctions | Roles by anyone with Manage permission settings; sanctions by anyone with the needed permission and a higher rank |
| Made with | pwikit admin create / admin grant, or the Superuser checkbox on a user's screen | The Site superuser checkbox on a user's screen | The Users screen |
Superusers and site superusers have every permission only while the account is active. A deactivated account has none.
A site superuser can make others site superusers and can remove any site superuser, themselves included, so a site can have several at once who can replace one another. Their power stops at the site: they cannot change the account itself, deactivate it or stop it signing in, cannot open Suspicious activity, cannot delete mirrors on External mirrors, and do not see pwikit update notices. Manage permission settings does not let an account grant site superuser.
Menu and required permissions
The permission names below are the labels shown in the permission matrix; the full list is in The permission list.
| Group | Screen | Required permission |
|---|---|---|
| — | Dashboard | None |
| Site | Site settings | Manage site |
| Themes | Manage site | |
| Pages | Edit pages | |
| Page categories | Manage categories | |
| Tags | Manage tags | |
| Tag categories | Manage tags | |
| External mirrors | Superusers and site superusers; only superusers delete mirrors | |
| Plugins | Manage site | |
| Members | Users | Manage users |
| Roles | Manage roles | |
| Role categories | Manage roles | |
| Permission check | Any of Manage users, Manage roles or Manage permission settings | |
| Invite links | Manage users | |
| Announcements | Manage site | |
| IP bans | Ban members | |
| Forum | Forum sections | Manage forum |
| Forum categories | Manage forum | |
| Recent posts | Manage forum | |
| Queue | User reports | View user reports |
| Support tickets | View user tickets | |
| Membership applications | Review membership applications | |
| Membership quiz | Manage site | |
| Records | Admin log | View admin log |
| Suspicious activity | Superusers only |
Several screens contain parts that grant rights: permission matrices, category and section overrides, role checkboxes and the role fields of the site settings. Those parts appear only to accounts with Manage permission settings.
The admin panel checks permissions for the site as a whole. Category and section overrides do not affect which screens you can open.
Search admin above the menu finds screens by their names and the names of their fields, among the screens you can open.
Site settings
Site settings is one form, and all of its boxes are saved together. If any value is rejected, nothing is saved.
Site information
- Site identifier takes letters, digits,
-and_only. Command-line options such as-siterefer to it. Inline themes are stored per site identifier, so after changing it, open each inline theme and save it again. - Domain and Media domain are the host names requests arrive at, without a scheme or path. A port is allowed, such as
localhost:8080. See Changing the domain. - For Site language and Interface language, see Interface language.
Visitors always see times in their own local time; Site time zone does not change that. The site time zone sets where a day begins and ends when modules such as [[module ListPages]] filter pages by date. The date range of the site search counts days in UTC. Enter an IANA time zone name, such as Asia/Shanghai or UTC.
Interface language
The interface language each visitor sees is decided in this order:
- If the account has chosen an interface language in Settings, that language.
- Otherwise, if Follow each visitor's browser language is checked and the site has a translation for the language the browser asks for, the browser's language.
- Otherwise, the Site language.
Follow each visitor's browser language is checked by default. When it is cleared, visitors who haven't chosen a language see the site language. For example, the interface of a Chinese site stays in Chinese for a browser set to English. Members who chose a language in Settings are not affected.
Simplified Chinese and English are available. The interface language changes only interface text such as buttons, menus and messages; page content is not translated.
The admin and member roles a new site starts with are named in the language the site was created with (pwikit createsite -language). Changing the site language later doesn't rename them; rename them under Roles if needed.
Appearance
With — chosen as Site theme or System page theme, no theme is loaded and pages use the built-in styles. Icons must be PNG, JPEG, GIF, WebP or ICO, up to 2 MB; uploading a new file replaces the icon, and only Clear current icon removes it. Footer license text is wikitext in which only [[module time]] is rendered; other modules are shown as plain text.
Content defaults
Rating system and Allow users to create tags always name a value at site level. They apply to every page whose category does not say otherwise. A category left on Follow the site changes with them.
When users may not create tags, the tag editor says that only existing tags can be chosen, and saving tags that do not exist is refused with a list of them. Create such tags on the Tags screen first. When users may create tags, type the new tag in the tag editor and press Enter, or click Create tag in the suggestions.
With Self-voting ticked, authors cannot rate their own pages. No-permission message is the text shown to users without edit permission when they try to edit or create a page; leave it empty for the default. With Deletion notice ticked, authors are notified when their page is deleted, and Notice text may use {pagetitle}, {pagename}, {pageurl} and {source}.
Registration and accounts
Open sign-up is checked by default. When it is cleared, no new accounts can be made on this site and Wikidot accounts cannot be claimed on the sign-up page; existing accounts sign in as usual, and invite links and claim links keep working. The setting applies to this site only.
Role after sign-up and Role after claiming are shown only with Manage permission settings. If they are empty, new accounts hold only registered. registered has no permissions by default, so these members cannot edit pages, comment or rate. The role is given only at the moment of sign-up or claiming; assign it to accounts that joined earlier one by one under Users.
Welcome message is the notification a new member receives after signing up, accepting an invitation or claiming an account. It takes wikitext; modules are not rendered. Left empty, the default text is used, which the field shows greyed out.
Every sign-up requires an email address, and a verification email is sent to it. Email verification requirement decides what an unverified account can do:
| Option | Effect |
|---|---|
| Optional | New accounts are signed in right away. Verifying the address changes nothing about permissions |
| Required | New accounts are not signed in after signing up, and the sign-up page asks them to check for the verification email. Selecting Continue on the page the email links to verifies the account and signs it in; the sign-up page shows Continue too once reloaded. Until the address is verified, the account cannot change anything or send private messages |
The policy applies to existing unverified accounts as soon as it is saved. Without a mail server configured, emails are written to pwikit's log instead of being delivered, so nobody receives a verification link; see Configuration.
Membership by password
This box is shown only with Manage permission settings. Visitors enter the password through [[module MembershipByPassword]] on a page of your choice (see Modules), and a signed-in account that enters it correctly receives Role after joining. Joining works only when Membership by password is checked, a password is set and a role is chosen.
The membership password is stored, and shown on this screen, as plain text.
Role for membership applications
This box is shown only with Manage permission settings. Role granted on approved applications is the role an applicant receives when a membership application is saved as approved. New sites start with the member role. Left empty, approving an application grants no role.
Changing the domain
- The change applies on save. The site answers only at the new domain, and the old one shows a page saying that no site is bound to that name. You are not redirected, and you need to sign in again at the new address.
- Point the new name's DNS at this server before saving.
- If pwikit already serves HTTPS automatically, a new public domain gets its certificate on the first visit. If it served plain HTTP because no public domain was bound, restart pwikit to switch to HTTPS. See Deployment.
- If the site can no longer be reached, fix the domain with
pwikit site rebind.
Use a media domain that differs from the domain, such as wiki.example.org and files.example.org. Separate domains are a security boundary: uploaded HTML then cannot act as the site. Using the same name for both works, at the cost of uploaded HTML files and external="true" HTML blocks opening in isolation: their scripts still run, but cannot use cookies or local storage. When the two differ, requests for files on the page domain, and requests for pages on the media domain, are redirected to the right one. A media domain can belong to only one site on the instance.
Pages
Pages lists every page on the site. Checked pages can be acted on together, and each page can be edited or renamed on its own.
Actions on selected pages
| Action | Effect |
|---|---|
| Delete | Deletes the pages with their history, attachments and ratings. Cannot be undone |
| Exclude from search | Keeps the pages out of search results. See Search exclusions |
| Include in search | Returns the pages to search results |
| Revert | Takes each page back the given number of revisions, from 1 to 50. Title, tags, parent page, ratings and attachments are restored along with the source |
Deleting and reverting show a confirmation page first, and the result is reported for each page.
Editing one page
Deleting, reverting, editing and renaming are done as your account, and each is checked against your permissions on that page, as on the page itself: deleting needs Delete pages, renaming needs Move pages in both the old and the new category. Edits, renames and reverts appear in the page history under your name.
Page categories
A page category is the part of a page name before the colon: forum:start is in the forum category. Pages without a prefix are in _default. Every category that holds pages is listed on this screen. A category that has never been saved uses the site's content defaults and has no overrides; clicking it opens a new form with its name filled in.
- With Include in index unchecked, pages in the category are left out of search and carry a
noindextag for search engines. - Rating system, Allow users to create tags and Theme can be set to Follow the site, which uses the site's value; new categories start that way. For the first two, Follow the site names the value it currently resolves to. A category with its own theme no longer loads the site theme.
- An empty Top bar page or Side bar page uses
nav:topornav:side. - With Manage permission settings, the form also has a Permissions box for overriding a role's permissions in this category. Ticking Own settings changes no permission by itself; only entries set to Allow, Withhold or Deny take effect in this category.
- In the Permissions box, ticking Hide from this role under Bottom toolbar for a role hides the bottom toolbar (the edit, rate, history and other buttons) on this category's pages from visitors holding that role. The page information is still shown. A visitor holding several roles loses the toolbar if any one of them has the box ticked. Superusers always see it. This only changes what is displayed and takes away no permission, so a page's source and the like can still be reached in other ways; use permissions to restrict actions.
Required tags takes one group per line. Creating a page in the category or changing its tags needs at least one tag from each group. Tick Not bound by required tags for a role in the Permissions box to exempt it.
Deleting a category removes its settings and overrides. Its pages are not deleted; they use the site's content defaults again.
Themes
A theme is either inline CSS or an external link. An inline theme is served at /-/theme/<identifier>.css and is updated as soon as it is saved. A theme takes effect once it is chosen as the site theme or system page theme in Site settings; a category can also use a theme of its own, set in Page categories.
Deleting a theme the site uses leaves the site with no theme, and categories using it follow the site again.
Tags
With Include in index unchecked, every page with the tag is left out of search.
On a page, a tag written name belongs to the tag category whose identifier is _default, and slug:name belongs to the tag category with identifier slug. A tag created here with no category goes into the _default tag category. Two tags in the same tag category cannot share a name. Tags created here keep their case, while tags typed on a page are lowercased before matching, so use lowercase names.
Click the number in a tag's Pages column to see every page carrying it on the Pages screen.
Deleting a tag removes it from every page. When users may create tags, a tag no longer on any page is removed the next time any page's tags are saved.
Tag categories
A tag category's Identifier is the prefix used in page tags (slug:name). Categories with a smaller Priority come first in a page's tag list, and two categories on a site cannot share a priority.
A category that still holds tags cannot be deleted; move its tags to another category or delete them first. Two categories on a site cannot share an identifier either.
Click the number in a category's Tags column to see every tag in that category. The search bar of Tags can also filter by category.
External mirrors
Superusers and site superusers can open it; only superusers can delete a mirror. The screen lists the external pages this site is missing and the mirrors, and can scan the site, fetch missing pages, and fetch a single mirror again or delete it. See Mirroring pages from other wikis.
Users
Accounts belong to the whole instance, so Users lists accounts from every site; roles are assigned per site. The email column is shown only to superusers, and only a superuser's search matches email addresses.
Editing an account
Anyone who can open this screen can open any account, their own included. Sanctions and vote resets are available only on accounts ranked below you, whose Rank number is larger than your own; superusers and site superusers are not limited. Only a superuser or another site superuser can sanction a site superuser. Rank is the smallest order number among the account's roles on this site; an account with no roles shows 2147483647.
The screen has three parts: the account itself, which only a superuser may change; what this site has done to the member; and the roles held on this site. See Roles and permissions for why the split runs where it does.
- Only a superuser can change account details such as username, display name, email and bio; anyone else sees the current values. Email, the last sign-in time and the last sign-in address are shown only to superusers. A superuser can help someone who no longer receives mail get back in by changing the address: the change takes effect 7 days after the new address is confirmed, and until then the owner or a superuser can cancel it, as can the old address through the notice it receives. Once the change is in, have them use Forgot password on the sign-in page. A bot's API key can be read by those with Manage bot accounts on the site that created it; otherwise only a superuser sees it.
- Last login and Latest IP are shown to superusers only. Latest IP is the most recently used of the addresses recorded for Suspicious activity, so it can also come from rating or checking notifications.
- Sanctions on this site: ban, silence, no editing and no rating. Each row appears only to accounts holding the matching permission. End time is read in your own local time; leave it empty for a sanction that lasts until lifted. What each sanction removes is listed in Sanctions.
- Roles: checkboxes for this site's roles, shown only with Manage permission settings. They add and remove roles on any account, your own included. The roles of a superuser can be changed only by a superuser, and those of a site superuser only by a superuser or a site superuser. If you untick every role that lets you into the admin panel on your own account, you are asked to confirm before saving, since you could no longer enter the admin panel afterwards.
State and restrictions is shown to superusers only. Its settings are written on the account and apply on every site of the instance; to restrict a member on this site alone, use a sanction.
- With Account active unchecked, the account cannot sign in and its open sessions stop working.
- With Account active unchecked and a date in Deactivated until, the account is treated as signed out and cannot sign in until then, and works again afterwards. Without a date it stays off until the box is checked again.
- Forum active and Forum inactive until restrict forum posting the same way on every site; the effect is described in Locks, authors and the forum.
- With Can send private messages unchecked, the account cannot send private messages. Sending also needs the Send private messages permission.
- A superuser is not held back by a deactivation with an end date, a forum restriction or a private message restriction. A superuser with Account active unchecked and no date still cannot sign in.
Creating accounts and inviting people
- New user: creates an account with a password, which the user can change later.
- Mail invitation: creates a deactivated placeholder account and mails an invitation link to the address given; the account becomes active when the person completes the link.
- Generate invite link: the same, but the link is shown on screen instead of mailed. It is shown only once, so copy it.
- Generate claim link: creates a link for an imported Wikidot account nobody has claimed. Whoever uses it takes over the account and keeps its Wikidot username. The account is unchanged until the claim succeeds.
- Activate account, on an account's screen: binds an email address to the account and mails an acceptance link; for an imported Wikidot account the link is a claim link. It appears only on accounts that have never had a password, that is invitation placeholders and unclaimed imported accounts. The new address does not count as verified until its owner verifies it.
- New bot: see Bot accounts.
All of these need Invite members, except New bot, which needs Manage bot accounts. Roles can be chosen at the same time, which needs Manage permission settings. An email address that already belongs to an account is refused. Invite and claim links are valid for three days and work once.
Without a mail server configured, invitations are written to pwikit's log instead of being sent, although the screen reports them as sent. Use generated links, or configure mail in Configuration.
Bot accounts
A bot account gives a script a fixed identity on the site. It has no password and cannot sign in on the sign-in page.
- On the Users screen, click New bot and enter a username. This needs Manage bot accounts. The API key is shown on the bot's screen.
- The script sends
Authorization: Bearer <API key>with every request. A request carrying it is handled as the bot, without the CSRF check. With a wrong key, or once the bot is deactivated, the request is handled as signed out. - What a bot may do depends on its roles, as for any account. A new bot holds only the built-in
everyoneandregistered. To let it edit pages or post, check the roles on its screen. Roles work only on the site that granted them.
- A bot remembers the site that created it. Only staff with Manage bot accounts on that site, and superusers, can read its API key; staff on other sites cannot. A bot made before this was recorded, with no creation in the admin log, belongs to no site, and only a superuser can read its key.
- To stop a bot at once, a superuser unchecks its Account active or sets Deactivated until.
- The API key cannot be regenerated yet. If it leaks, deactivate the bot and create a new one.
- Exporting a site clears the API keys of bot accounts; see Exporting a single site.
Resetting votes
Reset ratings needs Reset member ratings. Confirming deletes every vote the account has cast on this site, and the ratings of the affected pages change at once. Votes the account cast on the instance's other sites are kept. This cannot be undone.
View activity on an account's screen lists the account's edits, votes and posts on this site. Vote times are shown only with View vote times.
Roles
A smaller Order number ranks higher. Rank decides which accounts a non-superuser may sanction, which role of a role category is displayed, and which role a vote is grouped under.
- Group votes: every vote is filed under one grouping role:
registeredoreveryoneif that role has it checked, otherwise the voter's highest-ranked role that has it. - Badges and icons: within one role category, only the highest-ranked role is displayed for each style next to a name, and only one role of the category appears on a profile. Roles without a category are all displayed.
- The list's Management permissions column shows Yes when the role allows any permission under Tickets, Member actions or Admin panel.
- The Permissions box is shown only with Manage permission settings. Every permission has Allow, Inherit and Deny; see What a role holds.
Deleting a role removes it from every account and every category and section override. Site settings that named it are cleared, and votes grouped under it lose their group.
Built-in roles
Every site has two built-in roles. They cannot be deleted, their identifiers cannot be changed, and they are not assigned by hand.
| Role | Held by | On a new site |
|---|---|---|
everyone | Every visitor, signed in or not | View pages, page comments, forum sections, forum categories, threads and posts |
registered | Every signed-in account | No permissions |
With Manage permission settings, the edit screen of either role has a Reset to default button that puts its permissions back to the new-site values above.
To change what anonymous visitors or all members can do, edit these roles. Other roles are assigned on the Users screen, through the sign-up and claim role settings, membership by password, invite links and approved membership applications.
Sites created with pwikit createsite also start with two ordinary roles. They are no different from roles you create yourself and can be changed or deleted. They are only a generic starting point; adjust them to match your site's rules soon.
| Role | Name | Settings |
|---|---|---|
admin | The word for administrator in the default interface language | Order 0; Can enter the admin panel checked; every permission set to Allow; profile display Status |
member | The word for member in the default interface language | Order 1; permissions in the pages, forum and member interaction groups set to Allow, except Lock pages, Reset page ratings, Manage page authors, Delete forum posts, Create forum threads, Edit forum threads, Pin forum threads, Lock forum threads and Move forum threads, which stay on Inherit; the tickets, member sanctions and admin panel groups all stay on Inherit; profile display Status |
On a new site, Role after sign-up and Role after claiming are both empty, so member is not given automatically. Set both to member, or to another role, under Registration and accounts.
Role categories
Role categories group roles so that an account shows one role per category. A category that still holds roles cannot be deleted.
Permission check
The Permission check screen shows why an account can or cannot do something. Anyone with Manage users, Manage roles or Manage permission settings can open it. It can also be reached from Check permissions on the user screen, Check a user's access to this page on the page screen and Check this role on the role screen.
The screen has four tabs:
| Tab | Use |
|---|---|
| Check a user | Whether an account can do something, and why |
| Check a role | How a role sets each permission, and the result after a page category's override |
| Who has a permission | Which accounts hold a permission, and why the others do not |
| Configuration check | Settings in roles, category overrides and section overrides that commonly cause problems |
Checking a user
Enter a username, or select Check as a signed-out visitor. The permission and Page or post are both optional.
- With a permission, the line at the top gives the answer, the step that decided it and the reason, with a suggested fix and a link to the screen where it is made. Other rules that also refuse the permission follow Also, and have to be dealt with as well. Expand Full evaluation to see all eight steps; How a decision is made describes each.
- Without a permission, every permission of the account is listed with its reason. Details opens the full evaluation for one of them.
Page or post takes a page name, a link copied from the address bar, a forum thread (t-123), a post (post-456) or a forum section (s-7). Left empty, the check is for the whole site. A page that does not exist yet is checked as a new page in its category.
Next to the answer, the screen shows the relevant state of the account and the object. Account, forum and private message deactivation apply to the whole instance, and only a superuser can change them on the user screen.
Checking a role
Choose a role and, optionally, a page category. The table lists Role setting, Category override and Result for each permission. Only this one role is considered. An account's final answer also depends on its other roles.
Who has a permission
Choose a permission and, optionally, a page or post. The answer for a Signed-out visitor and for an Ordinary signed-in user comes first, followed by the accounts that hold the permission and those that do not, each with the reason.
Only accounts that hold roles on this site, are under a sanction here or are superusers are checked one by one, up to 300 of them. Every other account gets the same answer as the Ordinary signed-in user line. Accounts with an unverified email address and page authors can differ, so check them one at a time with Check a user.
Configuration check
| Level | Finding |
|---|---|
| Serious | everyone or registered denies a permission |
| Serious | everyone or registered allows a permission from Admin panel, Member actions or Tickets |
| Serious | A category or section override denies a permission to everyone or registered |
| Warning | Another role denies a permission, and some accounts hold that role |
| Warning | A category or section has more than one override for the same role. Only the first takes effect |
| Warning | Role after sign-up or Role after claiming is not set |
| Note | A role still sets a permission that no longer has any effect |
Invite links
Invite links lists every invitation and claim link and whether it has been used. Unused links can be revoked; used links cannot.
IP bans
IP bans bans a single address or a range of addresses. Visitors from a banned address can still read the site, but cannot sign up or change anything, including editing pages, uploading files, rating, posting and sending private messages. Signing in still works, but changes stay refused afterwards.
- Address or range takes a single IPv4 address such as
203.0.113.7, a single IPv6 address such as2001:db8::1, or a range in CIDR form such as203.0.113.0/24or2001:db8::/32. - End time is read in your own local time; leave it empty for a ban that lasts until lifted. An expired ban stops applying and stays in the list until it is lifted.
- Banning the same address or range again updates the reason and end time of the existing entry.
- Superusers and accounts holding Ban members are not affected by IP bans.
- An IP ban applies to this site only.
When the site sits behind a reverse proxy, set trusted_proxies in the configuration, or every visitor appears with the proxy's address.
Forum sections
Forum sections are the top level of the forum. A section marked Hidden is left out of the forum's section list unless the reader chooses to show hidden sections, and a direct link still opens it. Its threads still turn up in site search and in the sitemap.
Threads in a section with Include in index unticked are left out of site search and the sitemap, and tell search engines noindex.
With Manage permission settings, the form also has a Permissions box for overriding a role's permissions in this section. It works as on page categories.
Deleting a section that still has categories fails. Move or delete its categories first.
Forum categories
Forum categories hold threads and must belong to a section. A category marked Holds page comments lists the comment threads of pages, and readers cannot start threads in it.
Deleting a category that still has threads fails.
Recent posts
Recent posts lists the site's newest forum posts, with or without page comments.
User reports
Members can select Report in a page's options, on a forum post or on a user's profile, or select messages in a private conversation and report them. Every report needs a reason. A reported page is filed against its first author. Every member who can open this screen is notified of a new report.
For a message report, the full conversation between the two accounts is shown only to superusers. Private messages belong to no single site, so site administrators see only the messages the reporter chose to send. Setting any status other than Pending records you as the handler and the time. Reply to submitter and Processing notes work as in Support tickets.
Support tickets
Support tickets are submitted by signed-in members through [[module ApplicationForm]] on a page (see Modules). Every member who can open this screen is notified of a new ticket, and the same goes for membership applications. Setting any status other than Pending records you as the handler and the time.
The text in Reply to submitter is sent to the submitter with the status and shown under Tickets in their account menu; Processing notes are seen by staff only.
Membership applications
Membership applications are submitted through [[module ApplicationForm type="membershipapply"]] and handled like Support tickets. When you save an application as approved, the applicant receives a role in the same step.
Role granted on approval defaults to Site default, the Role granted on approved applications in the site settings. An account with Manage permission settings can pick another role for a single application; a reviewer without it always grants the site default.
Membership quiz
Turn on Quiz, write the questions and choose the Role given on passing, and members can take the quiz through [[module MembershipQuiz]] on a page (see Modules). Leave a blank line between questions, and under each question put one option per line, starting with + for a right answer and - for a wrong one. After using up their Tries, a member waits out the Cooldown before trying again.
Announcements
Announcements are sent as notifications to the members of this site. Superusers can also send them to every user on the instance. An announcement must be previewed before it is sent.
Admin log
Admin log records every creation, change and deletion made in the admin panel of this site: who did it, when, on which screen and to what. Granting and removing site superuser, and every step of an email change made by a superuser, are recorded too, with the addresses masked. The log is read only.
Suspicious activity
Suspicious activity opens only for superusers. It helps find accounts run by the same person. pwikit records the network addresses an account uses when it signs in, rates pages and checks notifications, at most once per hour per address. The screen draws a graph linking accounts to the addresses they share.
Using the screen
- Leave out the addresses many people share first. Schools, offices, public Wi-Fi and mobile networks put many unrelated accounts behind one address; in the graph such an address links to a crowd of accounts.
- Look at the links that remain. Two accounts sharing one address says little. Accounts that share several different addresses are worth a closer look.
- A wider mask such as
/24groups the addresses of one network, which finds accounts that moved to a new address. It also groups unrelated people, so weigh it against other signs. - Filter by an account name to see the addresses and accounts it links to. The latest address of a single account is also shown as Latest IP on its screen.
The graph only shows that accounts used the same address; it does not prove they are the same person.
Clear IP records deletes every recorded address on the instance. Records build up again as accounts sign in or act, and existing links disappear with them.
Search exclusions
Three switches keep pages out of the site's search. A page is left out if any of them applies:
| Excludes | Where |
|---|---|
| All pages in a category | Uncheck Include in index on the Page categories screen |
| All pages with a tag | Uncheck Include in index on the Tags screen |
| Individual pages | Select them on the Pages screen and choose Exclude from search; Include in search undoes it |
Exclusions affect search only. Excluded pages still open normally and still appear in page lists built with modules. Pages in an excluded category also tell search engines not to index them.
Multiple sites
One instance can run several sites. Create each with pwikit createsite; the admin panel cannot create sites. Open a site's admin panel at /-/admin/ on that site's own domain.
| Separate for each site | Shared across the instance |
|---|---|
| Domain and media domain | Accounts: usernames, passwords, email, and the State and restrictions fields on the Users screen |
| All site settings, including language, time zone and email policy | Superusers, who manage every site |
| Themes, page categories, tags and tag categories | Recorded addresses on the Suspicious activity screen |
| Roles, role categories and each account's roles | |
| Sanctions on members, and the votes cleared by Reset ratings | |
| Pages, forum, user reports, tickets, applications, invite links and admin log | |
| Site superusers |
An account signed up on one site can sign in on another, but holds only everyone and registered there until it is given roles on that site. The User list on any site shows every account on the instance; changes to an account's own details apply everywhere, while sanctions apply only on the site that set them. Which is which is set out in Roles and permissions.
A new site starts with:
- the built-in roles only, and no role marked Can enter the admin panel, so only superusers can administer it at first;
- no themes;
- home page
main, time zoneUTC, email verification requirement Optional, rating system Upvote/downvote and Allow users to create tags set to Not allowed.
