Known limitations — Wikigui.de

Permissions are set per workspace, not per page

LimitationAccess & securityPlanned

What this means: Roles are Owner, Editor and Viewer, and they apply to a whole workspace. Everyone who is a member of a workspace can read every page in it. You cannot currently restrict one folder or page to a subset of that workspace’s members.
Who it affects: Teams that need one workspace to hold content with different audiences — an HR handbook alongside engineering documentation, for example.
Today’s workaround: Use a separate workspace per audience. Members, groups and roles are managed per workspace, so this is workable for a handful of audiences and awkward beyond that.
Our position: Space-level visibility with inheritance is the next significant piece of access work. It is the most common request we get and we are treating it as such.

The assistant does a set list of things, and does not answer questions

Limitation

What this means: The assistant in the corner of every screen can build a Kanban board from a plain-language brief, create pages and folders, find and open pages, and switch theme. Anything else you type is treated as a search of your workspace. It does not read your pages and answer questions about them, and it does not carry out open-ended instructions such as reorganising a folder.
Who it affects: Anyone evaluating us for AI-assisted question answering over their own documentation, or expecting an assistant that can act on any request.
Today’s workaround: Ask it a question in ordinary words and it returns the pages that match. Type help in the assistant to see everything it can do.
Our position: The set list is deliberate for now: nothing you type can delete, share or overwrite anything, because no such action exists for it to take. Question answering scoped to your permissions is on the roadmap and is not built. We would rather say that than let the word “AI” imply it.

Charts from other pages show what was last saved

Limitation

What this means: A chart or dashboard drawing from a table on another page shows that page as it was last saved. Charts from a table on the same page update as you type. Page exports include a caption naming each chart rather than the chart itself, and a page shared by public link cannot show charts that read from other pages.
Who it affects: Teams building a dashboard page over tables kept elsewhere, and anyone exporting or publicly sharing pages with charts.
Today’s workaround: Save the source page and the chart catches up. For exports, every chart’s table view and PNG download give its exact numbers and image.
Our position: Reading saved pages keeps a dashboard from showing someone’s half-finished edits. Charts in exports are on the list.

No offline access

LimitationUnder consideration

What this means: Wikigui.de needs a network connection. There is no offline reading and no local draft cache.
Who it affects: On-call engineers reaching for a runbook without connectivity, and anyone working while travelling.
Today’s workaround: Export a workspace before you travel — see below.
Our position: Offline reading is under consideration. Full offline editing with sync is a much larger undertaking and is not planned.

No native mobile apps

LimitationUnder consideration

What this means: There is no iOS or Android app. The web app is responsive and works on a phone browser.
Who it affects: Teams expecting an app-store install, push notifications or a home-screen presence.
Today’s workaround: Use the site in a mobile browser; it can be added to your home screen.
Our position: Under consideration. Improving the mobile web experience comes first.

The editor is slow to open on a phone

LimitationPerformance

What this means: The editor is the largest part of the application and is loaded only when you first open a page for editing. On a slow mobile connection that first load is noticeably slow. Reading pages is not affected.
Who it affects: Anyone editing on mobile data.
Today’s workaround: Once loaded it is cached for the session.
Our position: Splitting the editor into smaller pieces is planned work. We measure this against real visitor data, not lab scores.

Exports are HTML, not Markdown

Limitation

What this means: You can export an entire workspace as a zip: one HTML file per page, nested as your sidebar nests them, plus a manifest listing every page with its identifiers, versions, authors and timestamps.
Who it affects: Anyone wanting Markdown files for a static-site pipeline.
Today’s workaround: The manifest makes the archive straightforward to convert with your own tooling.
Our position: This is deliberate. Toggles, tri-state to-dos and boards have no Markdown equivalent and would be flattened or lost in conversion. We would rather give you everything in a format that keeps it. A Markdown rendition may be offered alongside, never instead.

Import covers Markdown, not yet Confluence or Notion

LimitationPlanned

What this means: You can upload a .zip of Markdown files and have them become pages, with folders preserved. Direct importers for Confluence and Notion exports are not built yet.
Who it affects: Teams moving from a tool whose export is not Markdown.
Today’s workaround: Both Confluence and Notion can export Markdown, which our importer accepts. Talk to us if the shape of your export gives trouble — we would rather help than have you find out halfway through.
Our position: Format-specific importers are planned. Note that Markdown import converts a documented subset: headings, lists, quotes, code, emphasis and links. Anything outside it is kept as readable text rather than dropped.

No self-serve billing

LimitationPlanned

What this means: You cannot currently sign up, enter a card and be charged. There is no automated trial-to-paid flow.
Who it affects: Small teams who would rather buy without a conversation.
Today’s workaround: Get in touch and we will arrange access directly.
Our position: Self-serve billing is planned. We are not going to publish prices we have not settled on.

Notifications reach you by email and in the app only

LimitationUnder consideration

What this means: Comments, mentions, review requests and to-do assignments notify you in the app and by email. There is no Slack or Microsoft Teams delivery. Two further limits are worth knowing: the in-app bell checks for new notifications about once a minute rather than pushing them instantly, and there are no per-person notification settings yet — you cannot mute one kind or switch to a daily digest.
Who it affects: Teams who live in a chat tool and treat email as an archive, and anyone who wants finer control over what reaches their inbox.
Today’s workaround: Email notifications can be routed into a channel by most chat tools, and filtered by subject line — each kind has its own wording.
Our position: Chat delivery is under consideration. Notification settings are planned. Until they exist we hold the volume down at the source instead: you are never told about your own actions, and saving a page without changing its to-dos notifies nobody.

Assigned to-dos are not gathered into one list

LimitationPlanned

What this means: A to-do on a page can be assigned to a colleague, who is notified when it is given to them, and you are notified when they complete it. What does not yet exist is a single view answering “everything assigned to me” across a workspace. Assignments live on the pages they belong to.
Who it affects: Anyone picking up items across several pages who wants one place to see what they owe.
Today’s workaround: Your notifications list every item you have been given, with a link to the page it is on. Search also finds pages by content.
Our position: A “my to-dos” view is planned. Treat the current feature as accountable checklists rather than task management: it tells the right people what changed, but it is not yet a place to work from. We would rather say that than have you discover it in week two.

Two people editing one page at the same time can overwrite each other

LimitationPlanned

What this means: Editing is not yet collaborative in real time. A page is saved whole, so if two people have the same page open and both save, the second save wins and the first person’s changes are replaced. That includes things like a to-do assignment made while someone else had the page open.
Who it affects: Teams editing the same page simultaneously, which is most likely during a live meeting or an incident.
Today’s workaround: Nothing is lost permanently: every save is a version, and version history will show you what the page held before and let you restore it. For live co-editing, agree who is typing.
Our position: Real-time collaborative editing is planned and is a substantial piece of work. A smaller step we expect to ship sooner is a warning on save when the page has changed underneath you, so you are asked rather than overwritten.

Content is encrypted in transit and at rest, but not end-to-end

LimitationAccess & securityUnder consideration

What this means: Traffic is encrypted in transit and data is encrypted at rest by the database platform. Content is not end-to-end encrypted, so it is readable by the service in order to provide search, versioning and permissions.
Who it affects: Organisations whose policy requires the vendor to be unable to read stored content.
Today’s workaround: You can choose the storage region for a workspace.
Our position: Under consideration, and honestly assessed: end-to-end encryption is incompatible with server-side search and several governance features, so it would be a distinct mode rather than a setting.

Hidden secrets in a page are encrypted by us, not by you

LimitationAccess & security

What this means: A secret placed in a page is encrypted before it is stored, is masked until somebody chooses to reveal it, and every reveal is recorded in your audit log. It is kept outside the page’s content, so it does not appear in search results, in a page’s version history, in an export, on a page you publish publicly, or to the assistant. It is not end-to-end encrypted: the encryption key is held by the service, so this protects a secret against being read out of stored data or turning up somewhere it should not, and not against us.
Who it affects: Teams who want credentials beside the runbook that uses them, and anyone assessing whether this replaces a password manager.
Today’s workaround: Keep anything that must be unreadable by us in a dedicated secrets manager and put a reference to it in the page. Note also that anybody who can open the page can reveal the secret — it is deliberately not a second permission, because a runbook whose credentials the on-call reader cannot see does not work when it is needed. Control access to the secret by controlling access to the page.
Our position: This is not a password manager and we will not describe it as one. It is the safe version of something teams already do, which is pasting the password into the page in plain text. Two limits are worth knowing before you rely on it: we cannot yet rotate the encryption key without making existing secrets unreadable, and removing a secret from a page does not by itself delete the stored value.

Editing a page as Markdown cannot carry every kind of block

Limitation

What this means: Any page can be opened as Markdown, edited as text and saved back. Markdown has no way to express some of the richer blocks — charts and dashboards, boards, toggle sections, the part-done state of a to-do, and links that point at another page by identity — so replacing a page’s content with Markdown removes those.
Who it affects: Anyone who prefers to write in Markdown and works on pages that also hold boards or charts.
Today’s workaround: Before switching, the editor lists exactly what that page would lose and how many of each, and will not proceed until you confirm. A page of ordinary text, lists, tables and code converts both ways without loss, and gets no warning.
Our position: A limit of the format rather than of our implementation, so we show the cost rather than hiding it. Writing Markdown into a page, and using Markdown shortcuts while typing normally, both work everywhere.

Accessibility: where we stand

Accessibility

What this means: Colour contrast across the interface is tested against WCAG 2.1 AA in both light and dark themes. Motion on our marketing pages respects your system’s reduced-motion setting and every animated element has a still resting state.
Who it affects: Anyone procuring against an accessibility standard.
What is not yet done: We have not completed a full independent audit, including screen-reader testing of the editor. We will not claim conformance we have not verified.
Keyboard note: Inside a code block, Tab indents and accepts code suggestions, as in any code editor, instead of moving to the next control. Use ↓ past the last line (or ↑ above the first) to leave the block. Everywhere else on the page, Tab works as normal.
Our position: If you need a VPAT or a formal accessibility statement for procurement, contact us and we will tell you exactly what we have tested.