> ## Documentation Index
> Fetch the complete documentation index at: https://ihub.learnille.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Roles and publishing workflow

> Recommended access, review, and publishing controls for iHub

## Recommended roles

| Role | Responsibility |
| - | - |
| Reader | Search and use published iHub content. |
| Contributor | Draft changes through Mintlify or Git. |
| Reviewer | Verify subject accuracy, clarity, and information safety. |
| Publisher | Merge approved changes to the primary branch. |
| Space administrator | Manage Git Sync, membership, domain, and publishing settings. |

Use least privilege. Most teammates should be readers or contributors; a smaller group should be able to merge and administer the project.

## Review rules

* Routine corrections need one reviewer familiar with the subject.
* Policies require the named approval authority.
* Security-sensitive or production runbook changes require an appropriate technical reviewer.
* Authors should not be the only reviewer of material that creates an obligation or operational risk.

## Recommended repository controls

Protect the deployment branch and require pull requests, at least one approval, and the documentation validation check. Limit direct pushes to administrators. Keep the repository private and grant the Mintlify GitHub App access only to this repository.

## Publishing model

Connect the `main` branch to Mintlify as the deployment branch. Repository changes deploy to the site, while web-editor publishing commits back to Git or creates a pull request when the contributor works on a feature branch.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.