Organizations & teams
An organization is inline’s workspace and tenancy boundary. Everything — GitHub connections, repositories, reviews, findings, learnings, settings, and spend — belongs to exactly one organization. It’s how a team’s work stays separate from everyone else’s.
# Personal vs. shared
- Every user automatically gets a personal organization the first time they sign in — a private space to try inline against their own repos.
- Shared organizations are for teams. Create one, connect GitHub, enable repos, and invite your teammates.
# Switching organizations
If you belong to more than one, switch the active organization from the switcher at the top of the sidebar. Everything you see — repos, reviews, dashboards, settings — is scoped to whichever organization is active.
# What’s scoped to an organization
| Scoped per organization |
|---|
| GitHub connections (App install or OAuth) |
| Enabled repositories and their overrides |
| Reviews, findings, conversations, and dashboards |
| Learnings, skills, and repo memory |
| Security, Actions, Cloud, Compliance, and Pentest configuration |
| Notification channels (Teams, email) and MCP settings |
| Monthly budgets and spend |
Because the boundary is complete, two organizations never see each other’s code, findings, or settings — even if the same person belongs to both.
# Members & roles
People join an organization as members with a role that governs what they can change — see roles & permissions. Owners can rename the organization, manage members, and transfer ownership; admins manage the configuration; members work within it.
# Ownership transfer
An owner can transfer ownership of a shared organization to another member — an atomic hand-off that swaps the owner role in one step, so there’s always exactly one owner.
Next: Roles & permissions and Members & invites.