Apidog affords powerful governance tools to efficiently manage your API workflows and team collaboration. By dividing your workspace into three architectural tiers β "Project", "Team" and "Organization" β you can oversee resources with precision, no matter how complex your setup becomes.Differences Between Project, Team and Organization#
In Apidog, each of these tiers represents a distinct level of management, designed to serve a very specific boundary:Projects#
A Project is the core workspace where your team designs, tests, and manages APIs and documentation.Creating multiple projects helps you easily categorize API resources to suit different team workflows. Each project operates with its own independent settings and permission controls, ensuring that your team can collaborate efficiently while maintaining strict data security.Read the following documents to learn more:Teams#
A Team is the fundamental collaborative unit that manages specific Projects and members. It can operate as part of a larger Organization, or function entirely as an independent, standalone workspace. Using a team allows you to:Isolate Data: Keep your team's data strictly segregated and invisible to any other teams to ensure privacy.
Control Access: Delegate specific, role-based permissions to team members.
Collaborate Securely: Empower members to share resources and co-edit APIs efficiently within a secure, dedicated environment.
Organizations#
An Organization is an optional, top-tier management workspace designed specifically for companies that need to scale and manage multiple teams.While smaller groups can collaborate perfectly well in a standalone Team, setting up an Organization allows administrators to:Manage Centrally: Oversee all API projects and resources across multiple teams from a single dashboard.
Unify Permissions: Assign and control global roles and administrative access company-wide.
Ensure Compliance: Enforce strict data boundaries and privacy policies between different teams.
A Project acts as the dedicated workspace where the hands-on API development gets done.
A Team provides a secure, isolated collaborative environment for specific departments to work together.
An Organization optionally centralizes management and oversight across your entire company.
Where Should I Invite Members From? (Project vs. Team vs. Org)#
To support precise access control for teams of all sizes, Apidog allows you to invite members from three different levels: Project, Team, and Organization.Because permissions cascade downwards in Apidog, the level at which you invite a user fundamentally dictates their baseline access. Choose the entry point that best fits your collaborative scenario:| Dimension | π Project-level Invitation | π₯ Team-level Invitation | π’ Organization-level Invitation |
|---|
| Entry Point | Enter a specific project -> Project Settings -> Members list  | Team Page -> Members / Invite in the top right corner  | Organization Settings -> Members in the Admin Console  |
| Primary Purpose | To accurately bring in relevant collaborators for a specific development project. | To divide specific business lines or departments, aggregating related development projects internally. | To build a centralized member pool for the enterprise/company, facilitating global control over structure and billing. |
| Best Scenario | Cross-departmental collaboration or outsourcing. Grant external personnel access to a single specific project while strictly limiting their access to other projects within the team. | Forming a new business line or department. Directly bring personnel into the team and grant them read/write access to all projects under that team with one click. | New employee onboarding. HR/IT admins batch import personnel into the enterprise pool and assign them to different business teams as needed. |
| Resulting Impact | Invitees enter the project. In addition to assigning project permissions, this will simultaneously establish their identity in the corresponding team (e.g., as a Team Member). By setting "Other Projects" to Forbidden, you can strictly restrict their vision to this project alone. | Invitees enter the Team. While assigning their internal team role (e.g., Team Member), you can simultaneously grant them uniform access to "All Projects" within that team. | Invitees enter the organization's "member pool". You can simultaneously set their identity in specific Teams (e.g., Team Member) when inviting them. |
Modified atΒ 2026-04-09 08:10:11
