Repository boundaries belong in the permission model

Every team eventually writes the document that explains who is allowed to touch what. Very few teams manage to keep it true.

Encode it, do not describe it

An invitation in Trylle carries its scope: which repositories, which permission level, and when it expires. Revoking it removes the access immediately rather than adding a line to a spreadsheet that someone will act on later.

Bots follow the same rules

Automations and bots are subject to the same grants as people. A bot cannot read a repository that was never connected to its workspace, and every grant it holds is visible on the same access page as human collaborators.