Docs › Daily use
Daily use: who does what
What engineers, heads of department, DevOps engineers and IT administrators do in MCDock each day.
MCDock has one program for everyone, and each person sees what their access allows. Pick your guide:
| You are | You mostly | Guide |
|---|---|---|
| Developer or engineer | clone, branch, commit, open and review pull requests, lock CAD and PCB files | Daily use for developers |
| Head of department (HOD) or team lead | approve work, watch progress, manage your team's access | Daily use for heads of department |
| DevOps engineer | pipelines, runners, environments, releases and deployments | Daily use for DevOps |
| IT administrator | keep the server healthy, backed up, secure and licensed | Daily use for IT administrators |
A normal change, end to end
- A developer creates a branch, pushes commits and opens a pull request.
- The pipeline builds and tests it. The DevOps engineer owns how that pipeline works.
- Reviewers, and the CODEOWNERS for the files that changed, approve it. A head of department approves where the branch rules ask for it.
- With Merge when ready, MCDock merges by itself once the approvals and checks pass.
- A deployment to production waits for its environment approvers, with a two-person rule if you turn it on.
- The IT administrator never has to step in. Backups, health checks and alerts run by themselves.
Updated 21 Nov 2026 · Something missing? Ask in the community.