Authentication today and future SSO support

BGMKB uses authenticated workspaces today and is designed for deeper enterprise identity options such as SSO.

Overview

BGMKB separates public reading from workspace management. Visitors can read published public content, while admins, writers, reviewers, and internal readers sign in before managing or viewing protected knowledge.

How it works

Authentication proves who the user is. Tenant membership, roles, groups, article visibility, and workflow status decide what that user can do after sign-in.

Recommended practice

The product direction includes stronger enterprise identity support, including SSO-style integrations for teams that want access managed through their central identity provider while keeping BGMKB permissions and publishing controls intact.

This starter article was copied into the BGMKB organization article database.