This article explains the experience from a reader's perspective when trying to access a knowledge base portal that has been set to private by its administrators. Readers do not need a FastKnowledge account — they only need an authorized email address.
Who does this apply to?
Anyone who visits a private knowledge base portal. This is not a feature you configure — it is the experience your readers go through automatically when the portal's access type is set to Private.
Step 1 — Visiting the portal
The reader visits the portal URL (e.g., `https://app.fastknowledge.io/base/acme-help`).
Because the portal is private and the reader has not been verified yet, they are automatically redirected to the email verification page.
Step 2 — Entering your email
On the verification page, the reader enters their email address and clicks Send Code.
If the email is on the authorized list:
- A 6-digit one-time verification code is sent to that email.
- The subject line is: "Your access code for [Project Name]".
- The reader is redirected to the code entry page.
If the email is NOT on the authorized list:
- The reader is shown a Access Denied page.
- They can click Request Access to notify the project administrators that they want access.
- They can optionally include a message explaining why they need access.
- A confirmation is shown: "Your access request has been submitted."
Step 3 — Entering the verification code
1. Check your email for a message containing a 6-digit code.
2. Enter the code in the Verification Code field.
3. Click Verify.
If the code is correct and not expired:
- Access is granted and the reader is redirected to the portal content they were originally trying to visit.
If the code is incorrect:
- An error message is shown: "Invalid or expired code. Please check your email or request a new code."
- The attempt counter increases. After 5 failed attempts, access is blocked: "Too many failed login attempts. Please request a new verification code."
If the code has expired (older than 5 minutes):
- Same error message as above. The reader must go back and request a new code.
Step 4 — Browsing the portal
Once verified, the reader can browse all categories, read all published articles, search for content, and vote on articles (thumbs up / thumbs down).
The verification is tied to the browser session. The reader does not need to verify again until:
- They close the browser (depending on browser settings).
Logging out
If the reader wants to end their session manually:
1. Find the Log Out option on the portal.
2. Click Log Out.
3. They are redirected back to the email verification page.
What readers can do on the portal
✓ Browse categories
✓ Read published articles
✓ Search articles
✓ Vote on articles (thumbs up/down)
✓ Contact page
✗ Edit or delete articles (readers have no edit access)