> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.superpath.io/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Managing Access to Knowledge & Roadmaps

# Managing Access to Knowledge & Roadmaps

**In this article:**
* Overview
* Why use access control?
* Access levels explained
* How to configure access control
* Example use cases
* Things to keep in mind
* Who can do this

## Overview

SuperPath lets you control **who can access Knowledge and Roadmaps** within your organisation. This gives you the flexibility to manage visibility, maintain quality, and roll out content at the right time — for example, building content quietly before opening it up to everyone.

${frame}[](https://www.loom.com/embed/740559c5f5e54774ac8d8d48f974fdee)

## Why use access control?

Access control helps you:

* **Build before publishing** — create and refine Knowledge content without it being visible to everyone.
* **Maintain quality and consistency** — limit visibility and use to experienced team members.
* **Control strategic tools** — ensure only Managers or Admins can create and manage Roadmaps.
* **Roll out gradually** — introduce features to employees when you're ready.

## Access levels explained

Each feature offers three access levels:

* **Everyone** — all users can access the feature.
* **Managers & Admins** — only Managers and Admins can view and use the feature.
* **Admin Only** — restricted to Admins (and Owners).

## How to configure access control

1. Go to **Settings → Features**.
2. Locate the **Knowledge Base** or **Roadmaps** section (each feature must be switched on before its access control appears).
3. Under **Who can access Knowledge?** or **Who can access Roadmaps?**, choose your access level: **Everyone**, **Managers & Admins**, or **Admin Only**.
4. Click **Save**.

![](https://storage.crisp.chat/users/helpdesk/website/-/c/0/6/4/c0645e580ffc0800/image_1n4lkoz.png)

## Example use cases

* **Knowledge Base (Admin Only)** — build and structure content before making it available to the wider team.
* **Roadmaps (Managers & Admins)** — let leadership create and manage Roadmaps without exposing drafts to employees.

## Things to keep in mind

* Knowledge and Roadmaps each have their own access control in the **Features** area. The **Library** is controlled separately under **Settings → Library**.
* A common rollout is to start with **Admin Only** while setting up, move to **Managers & Admins** for collaboration, then switch to **Everyone** when you're ready to launch.

## Who can do this

**Owners** and **Admins** can change these access settings — the whole **Settings** area is restricted to those two roles. **Managers**, **Instructors**, **Employees** and **Restricted** users cannot open Settings and so cannot change this.