Repository and Deployment Access
Who controls each critical account and can another authorised person recover the service during an incident? Use company-owned organisations, named accounts, least privilege, protected production access, and documented recovery.
What You Will Be Able to Decide
- Explain repository and deployment access in product and business terms.
- Apply this decision: Use company-owned organisations, named accounts, least privilege, protected production access, and documented recovery.
- Recognise this material risk: one credential can silently change both source and production without review or attribution.
- Use this review: Exercise contractor offboarding, secret rotation, backup restore, and the first incident handoff for the customer portal.
A founder is clarifying who controls the product and how the company will respond when something goes wrong. This lesson gives you a concrete question to take into a build brief, proposal review, or product decision.
Who controls each critical account and can another authorised person recover the service during an incident? The course example is A small team's customer portal with contractors and external integrations; use it to decide what evidence would justify the choice before a builder implements it.
What Does Repository and Deployment Access Mean for Your Product?
A founder is clarifying who controls the product and how the company will respond when something goes wrong.
Use the illustrative service for this course (A small team's customer portal with contractors and external integrations) to make the choice concrete. Who controls each critical account and can another authorised person recover the service during an incident?
Technical term
Repository and Deployment Access
Repository access controls the product's source history, while deployment access controls the systems that release and run it.
How Should a Founder Use Repository and Deployment Access?
For a small team's customer portal with contractors and external integrations, ask what would happen if one credential can silently change both source and production without review or attribution.
For this decision, the useful standard is that access, ownership, recovery, and response responsibilities are explicit and can be exercised without one individual.
- Decision: Use company-owned organisations, named accounts, least privilege, protected production access, and documented recovery.
- Evidence to request: show that access, ownership, recovery, and response responsibilities are explicit and can be exercised without one individual.
- Owner: name who will respond if one credential can silently change both source and production without review or attribution.
- Record the result in the security, ownership, and handover record.
- Practical review: Exercise contractor offboarding, secret rotation, backup restore, and the first incident handoff for the customer portal.
How Do You Choose an Approach to Repository and Deployment Access?
Who controls each critical account and can another authorised person recover the service during an incident? Use company-owned organisations, named accounts, least privilege, protected production access, and documented recovery.
The risk is that one credential can silently change both source and production without review or attribution. Compare a simpler option with the proposed one, including who will operate either choice.
- Describe the user or business outcome that must be protected.
- Identify the most credible failure and its consequence.
- Compare the simplest adequate approach with one realistic alternative.
- Set a review point for when the decision may need to change.
What Evidence Should You Accept for Repository and Deployment Access?
What Warning Signs Should You Look For?
- The proposal does not address this risk: one credential can silently change both source and production without review or attribution.
- Nobody can show whether access, ownership, recovery, and response responsibilities are explicit and can be exercised without one individual.
- The decision has no named owner or review point.
What Should You Ask a Consultant?
- What changes for the user if we choose this approach to repository and deployment access?
- How have we reduced or accepted this risk: one credential can silently change both source and production without review or attribution.
- Can you demonstrate that access, ownership, recovery, and response responsibilities are explicit and can be exercised without one individual?
- Who owns the result, and when will we reconsider it?
Key takeaway
Key Takeaway
Use company-owned organisations, named accounts, least privilege, protected production access, and documented recovery. Ask for evidence against the specific risk: one credential can silently change both source and production without review or attribution.