Instiq
Chapter 4 · Project Management and Security·v2.0.0·Updated 6/28/2026·~9 min

What's changed: Rewritten with structured blocks (diagrams, callouts, key points, quizzes)

4.1Permissions and Account Security

Key points

Learn the foundations of safe operation: the right permissions and strong authentication—repository roles and least privilege, granting via Teams, visibility (Public/Private/Internal), and account security with 2FA, PATs, and SSH.

Safe operation starts with the right permissions and strong authentication: who may do what and how far, and how you protect your own account. Getting these two right is the first step to protecting your team and yourself.

4.1.1Roles and least privilege

Repository roles increase in order: Read < Triage < Write < Maintain < Admin. Follow the principle of least privilege—grant each person only what their work requires, avoiding excess.

Diagram showing repository roles increasing in privilege: Read, Triage, Write, Maintain, Admin.
Repository roles (least to most privileged)

In an organization, grant permissions via Teams rather than to individuals. Teams can be nested, and a child team inherits the parent permissions. Base permissions set the default access for all org members, while non-members are invited per repository as outside collaborators.

Continue reading — free sign-up

You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.