Handbook exposure options
Gitlab projects support varying levels of exposure depending on the purpose of your handbook.
The following checklist will get the configuration aligned with your intended usage of this handbook.
Exposure options:
| Exposure | Employees | Public | Purpose |
|---|---|---|---|
| GitLab way, fully public | Interact on issues, submit changes | Interact on issues, submit changes | Share entire process as a differentiator and way to attract top talent |
| Private authoring, published openly | Interact on issues, submit changes | read published handbook only | Share final result for publicity, keep sausage-making internal |
| Private authoring and published internally | Interact on issues, submit changes | No visibility | Include competitive advantages or specufuc oocess guidanvce in handbook, stuff that can't be public |
GitLab way, fully public
Project visibility is public. protected branches keep master safe but anyone can contribute by submitting a Merge Request. Pages enabled, and "Access control" is disabled.
Project Settings > General > "Visibility, project features, permissions"
Project Settings > Repository > "Protected Branches"
Private authoring, published openly
Project visibility is private. Pages enabled with access control disabled.
Project Settings > General > "Visibility, project features, permissions"
Repository configuration is not as relevant since it's private.
Private authoring and published internally
Project visibility is private. Pages enabled with access control enabled. This matches gitlab project permissions and requires authentication before loading the handbook published site.
