- ThurWiki
- Administration
Administering it without a manual.
Spaces, users, groups, rights, templates, connections: all in one place, with a question mark next to every field.
The wiki administration.
The wiki administrator runs their wiki: spaces, users, groups, rights, templates, typography, connections, import. Everything you need for that sits behind one menu entry.
Nine rights, three levels, one rule.
Rights are inherited: from the user through the space down to the page. The finer level wins. A higher right includes the lower ones: whoever may write may also read and suggest; whoever may not read may do nothing at all. You do not have to tick the included rights one by one.
| Read | See the page |
|---|---|
| Comment | Write comments |
| Suggest | Submit changes for somebody to approve |
| Create pages | Make new pages |
| Write | Change existing pages |
| Delete pages | Move them to the recycle bin |
|---|---|
| Review | Approve or reject suggestions |
| Administer | Manage the space |
| Wiki administrator | Everything, across the whole wiki |
Users, sign-in, templates, typography, import.
Users
Create, set rights, lock. The credentials are shown once. When somebody leaves, the account is locked, not deleted: the history stays traceable, and the personal space remains so that a successor can go through it.
Signing in with your company account
SSO (single sign-on: one login for every program), part of the Enterprise package, over the common protocols OpenID Connect or SAML 2.0: Microsoft Entra ID, Google Workspace or your own company login system. SSO grants no rights and creates no accounts; the rules stay in the wiki. Signing in with a password remains available to everyone, as a lifeline should the login service fail. When somebody leaves, you therefore lock their account in the wiki as well.
Templates
Prepared pages for everything that recurs: meeting minutes, fault report, induction plan, project brief. The gain is not the typing saved but the completeness: whoever takes the template sees the empty heading they would otherwise have forgotten.
Typography
Fonts, sizes and colours per wiki. Your pages look like your company, without anybody writing styling code (CSS).
Import
From Confluence (Cloud, Server and Data Center), MediaWiki, DokuWiki, XWiki, BookStack, a Notion export and Markdown archives, in five steps with a preview. Nothing is written before the last step; a run can be repeated without pages appearing twice.
Statistics
Pages, versions, attachments, active users, changes per space: what is happening in the wiki, on one page. For the annual report, and for the question of which space is quietly being abandoned.
The API: anything the interface can do, a program can do.
For your IT people: every function can also be reached by a program, because the user interface uses the very same API; 36 endpoints with 257 actions, fully described. With it you can create pages from your monitoring, feed in reports, or connect the wiki to a tool we have never heard of.
An API key is a service account.
- It is the user account of a program and gets its rights like a person, can belong to groups and can be named in the rules of a space or a page.
- What it does appears in the log under its own name. A key is not a master key but as narrow as you cut it.
- 64 characters, shown once, after that stored only in unreadable form. It cannot sign in to the user interface and cannot manage further keys, even if its account is a wiki administrator.
The details.
What a call looks like and which actions exist is shown on the page for people switching and for specialists. The full description ships with the wiki.
Questions about administration
How do the rights work in ThurWiki?
Nine rights, inherited across three levels: user, space, page. The finer level wins. A higher right includes the lower ones: whoever may write may also read and suggest; whoever may not read may do nothing at all. Rules can be written onto groups instead of individual people.
What happens when somebody leaves the company?
The wiki administrator locks the account; it is not deleted. The history stays traceable, and the personal space remains so that a successor can go through it. With SSO over Microsoft Entra ID or Google Workspace, switching the person off there is not enough: signing in with a password remains available alongside SSO, which is why the account is locked in the wiki as well.
Is there an interface for our own programs?
Anything the user interface can do, a program can do as well; the interface uses the very same API. 36 endpoints, 257 actions, fully documented. Access runs through an API key, which is a service account with rights of its own and appears in the log under its name.
Who runs and maintains the wiki?
ThurData. You administer your wiki: spaces, users, rights, connections. Server, database, backups, updates and monitoring are our concern, in our own data centre in Switzerland.
You administer. We run it.
A wiki of your own for your company, set up by us, administered by you. With a person to talk to, not a ticket number.