Security and Permissions

What this is

This page explains how to think about access, scope, and governance for Hookshot in a company setting.

When to use it

Use it when connecting apps, preparing for rollout, or reviewing risk with technical stakeholders.

What you need first

• A proposed workflow

• At least one integration you plan to connect

Steps

1. Use least privilege

Connect only the integrations you need and keep the boundary as narrow as practical.

Examples:

• One team instead of every team

• One repo instead of every repo

• One channel instead of every channel

2. Separate trigger access from tool access

Ask two different questions:

• What should be allowed to start this Protege?

• What should the Protege be allowed to do?

3. Make ownership visible

Before rollout, confirm:

• Which team owns the Protege

• Who can change integrations

• Who is responsible for Audit review when something goes wrong

4. Pair security with observability

The safer workflow is the one you can quickly inspect:

• Event Feed shows the incoming signal

• Audit shows the resulting action

Engineer note: For company automations, good governance usually means narrow scope, clear ownership, and a reliable rollback path more than it means maximum complexity in the first version.

How to verify

• Connected integrations are limited to the intended workflow

• Trigger Access and Tool Access match the business need

• The owning team can inspect Event Feed and Audit

Common failures

• Overscoped integrations

• Shared ownership with no clear reviewer

• Treating a successful connection as a completed security review

Next step

• Quickstart for automation engineers

• Safe rollout