.png)
Publish branded external portals to share SOPs, process maps, checklists, and training with verifiable certificates.
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 — exportable as CSV.
Pick a template, drop in your content, set your colors. It looks like yours, not like ours.
Four starter templates: Certification, Knowledge Base, Auditor & Onboarding.
Four page layouts: cards, hero, sidebar, or document register.
Full theming - logo, colors, cover image, footer text
A portal is a stakeholder hub, not just a course list. Arrange any Wikidoc content into named sections, and it stays read-only and current.
SOPs, process maps, checklists, modules, and programs in one portal
Sections you name - "Our SOPs," "Key processes," "Certification program"
Fix the process once, every section content gets updated
From a public catalog to an auditor-only package - each portal decides who gets in, and every invite is on record.
Open - anyone with the link, optionally behind a shared passcode
Org-only - visible to your members alone
Invite-only - tokenized links to named emails
External learners get lightweight guest accounts tied to a verified email - never a login to your workspace.
Magic link or email + password - sign in from the portal page
Guests don't join your workspaceor see your other content
25 active guests included in the Team plan
A PDF is a claim; a verification URL is proof. Every certificate carries an ID and QR code pointing at a public page - no account needed to check it.
Unique certificate ID + QR code printed on every certificate
Public verification: status, name, module, org & dates—no email.
Expiry & renewal - set validity in months; renewal is a retake, not a phone call
"Of the 40 people my client sent, how many are certified?" - one screen. And for regulated content, evidence stronger than a completion tick.
Funnel analytics - visitors → registered → started → completed → certified
Per-guest table - progress, scores, certificates, last activity, CSV export
Read receipts - when each invited guest viewed each item
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 license.
Visiting practitioners and product partners certify on your protocols behind a shared passcode, with a certificate the client can verify.
Anita
Small Business Owner
No. Portal visitors sign in as guests with just an email - magic link or email and password. Guests never join your organization, 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 organization, 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 tokenized 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 organization's reporting, and guest accounts survive independently.
Yes. Set your logo, colors, cover image, and footer text, pick one of four page layouts, and hide the "Powered by Wikidoc" mark - all included in the Team plan.
