Domain Setup

Written By Christopher Lee

Last updated 6 months ago

Knobase supports secure, domain-based access control to ensure that only verified members of your school community can sign in and interact with your AI environment. By configuring allowed email domains and external access policies, administrators can manage who gets access, how accounts are verified, and what level of control is required for onboarding.

This setup is essential for maintaining a safe, school-specific AI ecosystem—especially when generating student reports, managing agents, or sharing sensitive data.

🧠 Why It Matters
✅ Ensures only authorized users can access your Knobase instance
✅ Prevents unauthorized sign-ups and data exposure
✅ Supports flexible onboarding for internal and external users
✅ Aligns with school IT and safeguarding policies

⚙️ How It Works

✅ Allowed Email Domains

  • Specify which email domains are permitted to sign up (e.g., school.edu.hk, knobase.ai)

  • Users must use an approved domain to create an account

  • Helps restrict access to verified school members only

🔐 External Email Policy Choose how Knobase handles sign-up requests from outside your allowed domains:

Option

Description

Block All External Emails

Completely prevent sign-ups from unapproved domains

Manual Approval Required

Allow sign-ups but require admin approval before access

Allow All Email Addresses

Open access to anyone (recommended only for public pilots)

🧑‍💼 Admin Controls

  • Admins can approve, reject, or deactivate external sign-up requests

  • All domain settings are managed under Organization Settings → Authentication

📌 Use Case Highlights

Scenario

Domain Setup Feature

Benefit

School-wide deployment

Allowed domains + block external emails

Ensures secure, internal-only access

Partner school onboarding

Manual approval for external domains

Enables collaboration with oversight

Public pilot or demo

Allow all emails

Simplifies access for testing