A branded portal in minutes
Pick a template, add content and apply your brand.
Publish branded external portals to share SOPs, process maps, checklists, and training with verifiable certificates.
When procedures are scattered across drives, chats, and people's heads, your team asks instead of searching. Wikidoc gives everyone one searchable portal with answers from your own documents so you can focus on the work, not the interruptions.
Start from a template, add sections of docs, maps, checklists, and programs, and apply your branding.
Publish open with a passcode, restrict to your org, or send expiring invites to named emails.
Certificates issue with QR verification, and the funnel dashboard shows who's certified.
Pick a template, add content and apply your brand.
SOPs, policies, checklists and training shared are always up to date.
Each portal sets who gets in, and every invite is recorded.
External learners get guest accounts, never workspace logins.
Every certificate has an ID and QR code anyone can verify.
See how many of a client's people are certified on one screen.
A members' portal in your studio's branding with no "Powered by Wikidoc" covering at-home sequences and injury modifications between classes.
Franchisees and casual staff get the brand standards always showing the approved version. Fix the recipe once and every venue has it.
Hand a client's finance team your month-end process and the checklist they follow as guests, not seats, invite-only, with nobody new to licence.
Visiting practitioners and product partners certify on your protocols behind a shared passcode, with a certificate the client can verify.
See what's related.
The certification paths your portal delivers - sequenced modules with a credential at the end.
The source of truth your guests read on the portal - captured once, governed by approvals.
Internal and external audiences, one reporting surface - completion, scores, and certificates.
No. Portal visitors sign in as guests with just an email - magic link or email and password. Guests never join your organisation, never appear in your org chart, and never consume a member seat. The Team plan includes 25 active guest learners, with additional capacity available as your external audience grows.
Every certificate carries a unique ID and a QR code pointing to a public verification page. Anyone - a client's auditor, a regulator - can open it without an account and see the status (valid, expired, or revoked), the learner's name, the module or program, your organisation, and the issue and expiry dates. No email address or other personal data is exposed.
Yes. A portal presents curated sections of any Wikidoc content: documents and SOPs, process maps, checklists, training modules, and full training programs. Everything renders read-only in the portal and always reflects the approved version - fix the process once and every guest sees the update.
You choose per portal: open (anyone with the link, optionally protected by a shared passcode), org-only (your members), or invite-only (named emails). Invites are tokenised links with optional expiry - you can see per-invite status and revoke or resend at any time.
Certificates persist - they are the learner's credential and keep verifying at their public URL. Completion records are retained in your organisation's reporting, and guest accounts survive independently.
Yes. Set your logo, colours, cover image, and footer text, pick one of four page layouts, and hide the "Powered by Wikidoc" mark - all included in the Team plan.