Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.codecobra.ai/llms.txt

Use this file to discover all available pages before exploring further.

Organizations let you work together with your team on shared Odoo projects. Instead of each person managing their own projects separately, you can group people, projects, and billing under a single organization.

​
Why use an organization?

BenefitDescription
Shared projectsEveryone on the team can access the same projects and tasks, reducing duplicate work
Team-based permissionsControl who can create projects, merge code to staging, and deploy to production
Centralized billingManage usage and payments from one place instead of individual accounts
Easy onboardingInvite new team members with an email or shareable link — they get access immediately
Role-based accessOwners, admins, and members each have appropriate levels of control

​
Create an organization

1

Open the Organizations page

Click Organizations in the sidebar navigation.
2

Create a new organization

Click New Organization and enter a name for your organization (e.g., your company name or department name).
3

Start inviting

You’ll be the Owner of the new organization. From here, you can invite team members, create teams, and start adding projects.

​
What you’ll see

Your organization page shows:
  • Projects — all projects that belong to this organization, displayed as cards. Owners and admins see everything; members see only projects assigned to their teams.
  • Collaborators — everyone in the organization with their role (Owner, Admin, or Member). You can change roles and manage membership from here.
  • Teams — groups within your organization, each with specific permissions and project assignments.
  • Settings — rename or delete the organization (owner only).

​
How organizations, teams, and projects fit together

Here’s how the pieces connect:
  1. An organization contains people (members) and projects
  2. Teams are groups of members with specific permissions (like “can merge to staging”)
  3. Projects are assigned to teams, controlling which members can see them
  4. Tasks live inside projects and inherit the project’s team-based access
This means you can have a “Developers” team that can merge to staging, a “Lead Developers” team that can also merge to production, and a “Stakeholders” team that can view projects but not make code changes.
Start simple. You can always add more teams and refine permissions as your organization grows. Many small teams start with just one team that includes everyone.

​
Next steps

Members and roles

Invite people and manage access levels.

Teams

Set up teams with specific permissions.