---
title: "Documentation Hub"
slug: help-documentation-hub
section: In-App Help
status: stable
description: "In-app help · How to find answers in the documentation system"
last-updated: 2026-10-07
---

# Documentation Hub

In-app help · How to find answers in the documentation system

## What Is the Documentation Hub?

The Globus Documentation Hub is the central knowledge base for the platform. It contains architecture documentation, operational guides, in-app help articles, and reference material for every module in the system. The hub you are reading right now is part of that system.

> **Always Available**
>
> The Documentation Hub is accessible from the Help group in the left sidebar (the "Globus Documentation Hub" entry, at /guide).

## Help Pages Directory

Quick links to every in-app help article, organized by category. Each page is written for operational staff and covers the essentials of a specific feature.

> **More Pages Coming**
>
> New help articles are added with each platform release. This directory is always up to date with the latest available pages. You can also find the hub in the Help group of the sidebar navigation.

## Navigating the Hub

The hub is organized into sections accessible from the left sidebar:

## Search & Discovery

Use the search bar at the top of the sidebar to find content quickly:

## Contextual Help Links

Throughout the Globus application, you will find ? (question mark) icons next to complex features. Clicking these opens the relevant documentation section directly. For example:

The Workflow Studio canvas links to the Workflow Studio help page / The Document Review Hub links to the Document Review architecture section / The Role Groups admin page links to the Role Groups help article / The API Keys page links to the API Keys help article / Monthly check-in forms link to the Monthly Check-in guide

**Changelog entries.** The hub also carries release notes as changelog entries. They are served by `GET /api/changelog` (newest first; `dashboard.view`), `POST /api/changelog` and `PATCH /api/changelog/:id` (both `guide.manage`, audited as `changelog.create` and `changelog.update`). An entry has `title`, `description`, `category`, optional `version`, `details` and `relatedEndpoints`, and a `date` that defaults to now. `PATCH` takes any subset of those fields and returns `404` when the entry does not exist.
## Content Structure

Documentation pages follow a consistent structure:

## Common Questions