What are Organizations?
Organizations in Devin Enterprise are logical groupings that provide structure and boundaries for your development teams. Each organization operates as a self-contained unit with its own shared Devin machine, repository access, and member permissions.Key Characteristics
Shared Devin Machine: Each organization has its own dedicated Devin machine that all members share. This ensures consistent environment setup and allows team members to collaborate on the same development context. Repository Isolation: All repositories granted to an organization are accessible to all members within that organization. Repository access is managed at the organization level, not per individual user. Member Boundaries: Users can belong to multiple organizations, but their access and permissions are scoped to each organization independently. Billing Separation: Each organization has its own ACU (Agent Compute Unit) limits and usage tracking, enabling clear cost allocation across teams.Organization Structure
Enterprise Hierarchy
Access Control Flow
- Enterprise Admin creates organizations and manages overall enterprise settings
- Team Admins invite members to their specific organizations
- Members access Devin and repositories within their assigned organizations
- Repository permissions are granted by Enterprise Admins to organizations
Planning Your Organization Structure
Recommended Mapping Pattern
An effective approach is to map each Devin organization to a GitHub/GitLab team, which often aligns with your Identity Provider (IdP) groups and logical business applications. This provides a systemic way to scale up usage and manage access to repositories.Example Mapping
| GitHub Team | Devin Organization | IdP Group | Business Function |
|---|---|---|---|
ecommerce-platform | E-commerce Platform | product-ecommerce | Customer shopping experience (web, API, etc) |
analytics-platform | Analytics Platform | product-analytics | Data insights and reporting |
payments-team | Payments Platform | product-payments | Payment processing and billing |
platform-infra | Infrastructure | eng-platform | Shared infrastructure and security |
Decision Framework
When planning your organization structure, consider these factors:Team Boundaries
Team Boundaries
Question: How are your development teams currently organized?Guidance: Create organizations that mirror your existing team structure. Teams that regularly collaborate on the same codebase should typically share an organization.Example: If your frontend and backend teams work closely on the same product, consider a single “Product Team” organization rather than separate frontend/backend organizations.
Repository Access Patterns
Repository Access Patterns
Question: Which repositories do different teams need access to?Guidance: Group teams that need access to the same set of repositories. Remember that all organization members can access all organization repositories.Example: If both your web and mobile teams need access to a shared design system repository, they might belong to the same organization.
Cost Allocation and Budgeting
Cost Allocation and Budgeting
Question: How do you want to track and allocate Devin usage costs?Guidance: Organizations provide natural cost centers for ACU usage tracking. Align organizations with your budgeting structure.Example: If you budget separately for each product line, create organizations that match those product boundaries.