Skip to content
New to wikis?What is a wiki?
Request a demo

Administration without a marketplace and without an upgrade weekend.

Spaces, users, groups, rights, templates, access: all in one place, with a question mark next to every field. Operation, backup and updates are ThurData's job. Macros and connectors are part of the product and are tested again with every update.

The administration.

Overview of the wiki administration with tiles

One overview

Spaces, users, groups, templates, credentials, typography, import, statistics, security: one tile each, showing where things stand.

Rights matrix of a space

Rights as a matrix

Rows for groups and users, columns for the nine rights. What stands there applies. The page can refine it.

Group administration

Groups instead of people

"Administration may read" is one row. With individuals it would be twenty rows, and every new arrival would need somebody to add one.

Wiki statistics with a chart

Statistics

Pages, versions, attachments, active users, changes per space. For the annual report, and for the question of which space is quietly being abandoned.

Nine rights, three levels, one rule.

Inherited from the user through the space down to the page; the finer level wins. Whoever may write may read and suggest; whoever may not read may do nothing at all.

ReadSee the page
CommentWrite comments
SuggestSubmit changes for somebody to approve
Create pagesMake new pages
WriteChange existing pages
Delete pagesMove them to the recycle bin
ReviewApprove or reject suggestions
AdministerManage the space
Wiki administratorEverything, across the whole wiki
The rule you have to know: if a permission row names the user, only what stands there applies. His general right no longer counts in that space. That way no inherited right quietly opens a page that was meant to be restricted.

Users, SSO, templates, import.

Users

Create, set rights, lock. Credentials are shown once. When somebody leaves, the account is locked, not deleted.

SSO (Enterprise package)

OpenID Connect or SAML 2.0 with Entra ID, Google Workspace or your own login system. SSO grants no rights and creates no accounts; signing in with a password remains as a lifeline.

Templates

Meeting minutes, fault report, induction plan, project brief, per wiki or per space. The point: every new page has all its sections from the outset, including the ones people otherwise forget.

Import

Confluence Cloud, Server, Data Center, MediaWiki, DokuWiki, XWiki, BookStack, Notion, Markdown. Five steps, a preview, repeatable.

Typography

Fonts, sizes and colours per wiki, with a preview, without CSS.

Access

41 connectors in one place: kind, address, key, test the connection. Secrets stored encrypted, never shown again.

The template administration with four templates: project brief, meeting minutes, induction plan and fault report, each with its purpose and scope.
Templates per wiki or space, taken over from an existing page.
The import wizard: on the left the page tree of the source, on the right the finished page with table and sections, below the two buttons to take it over.
Import with a preview. Page by page, or with all sub-pages.
The SSO settings.
SSO with a connection test.

Anything the interface can do, a program can do.

36 endpoints, 257 actions, documented. Create pages from your monitoring, feed in reports, connect the wiki to a tool we have never heard of. Page content goes in and out as Markdown.

  • An API key is a service account. Rights like a person, membership in groups, nameable in the rules of a space, and in the log under its own name.
  • As narrow as you cut it. 64 characters, shown once, after that only as a checksum. It cannot sign in, cannot switch wiki, cannot manage keys.
WIKI=https://wiki.your-company.com

curl -s -H "Authorization: Bearer $TW_KEY" \
  "$WIKI/api/pages.php?action=get&id=412&format=markdown"

curl -s -H "Authorization: Bearer $TW_KEY" \
  -d action=create -d space_id=12 \
  -d title="Maintenance 12 October" \
  --data-urlencode content_markdown@minutes.md \
  "$WIKI/api/pages.php"

Questions about administration

How do the rights differ from Confluence?

Nine rights, inherited across user, space and page; the finer level wins. Whoever may write may also read and suggest. The rule is deliberately strict: if a permission row names the user, only what stands there applies to him.

What happens when somebody leaves the company?

The wiki administrator locks the account in the wiki, even when sign-in runs over SSO; it is not deleted. The history stays traceable. The personal space remains, so that a successor can go through it; other users do not see it, administrators can reach it.

Is there an interface?

36 endpoints, 257 actions, documented. The user interface uses the very same interface. An API key is a service account with rights of its own, can belong to groups and appears in the log under its own name. Page content goes in and out as Markdown.

Who runs and maintains the wiki?

ThurData. You manage spaces, users, rights and access; server, database, backups, updates and monitoring are ours, in our own data centre in Switzerland.

SecurityLocation, sign-in, intrusion detection, secrets AccessHow a connector is set up and what it may do MigrationImport with a preview from seven sources

Wiki administration for administrators: nine rights across user, space and page, groups, a rights matrix per space, users locked rather than deleted, SSO, templates, typography, import from Confluence, MediaWiki, DokuWiki, XWiki, BookStack, Notion and Markdown, statistics, 41 points of access to other systems, and an interface with 36 endpoints and API keys as service accounts. Operation, backup and updates are handled by ThurData.

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.

Request a demo +41 71 571 68 40