Manage · Governance (hosted)
Governance
Hosted org-level view of spend and integrity governance across the team: budget status against thresholds, per-developer spend share, and integrity and sensitive-path alert counts.
Start here if you want to set spend and integrity policy across your team: Governance.
See it in motion
Where to find it
- Hosted route:
repoops.ai/team/governance - Auth: Org owner / admin role required
- Plan: Any paid plan. Enterprise adds the cross-team company repo view and the compliance control coverage read from the audit trail.
What it does for you
Companies: the org above a team
If your organisation runs more than one team, a company groups them under one owner. Most accounts are one team and no company, and that is the right answer: a team with no company is its own boundary and behaves exactly as it always has.
- Creating one is the team owner's decision, not an admin's. Whoever creates it owns it.
- Attaching a team needs you to own the company and to own or administer that team. There is no invite flow yet, so a team whose owner is someone else has to be attached by them.
- Detaching can be done by the company owner or by that team's own owner. A team can always leave, and a detached team goes back to being its own boundary.
What a company changes about your connectors: a connector you connect at the Company scope is usable by the other teams in that company. A Team-scoped one is not, and neither is a Company-scoped connector created before company reach shipped. Those keep the reach they had, and the Connectors tab marks a borrowed row with the team that owns it, because widening a credential's reach is a change you should choose rather than receive on a deploy. Re-connect one to give it company reach.
Nothing else about a company widens anything. It records which teams share an owner; the rollups and figures on this page are unchanged.
Read more
Last updated