In Apidog, an organization is used to centrally manage multiple teams and members. With organizations, you can control permissions, assign roles, and ensure efficient collaboration across your company.Creating an Organization#
You can create one or more organizations. To create a new organization:1.
In the main window, click Organizations from the left navigation panel to open the organization management page.
2.
Click the + New Organization button at the bottom left.
3.
Enter the organization name.
4.
Click Create. Your new organization is now set up.
Organization Members and Roles#
You can invite members into your organization and assign them different roles:Org Admin: Has the highest permissions (except the org owner). Can manage organization members, teams, and organization settings.
Org Member: Can join the organization and its teams, and collaborate on projects. Cannot change organization settings.
Inviting Members to the Organization#
As an Organization Owner or Admin, you can directly introduce personnel into the enterprise from the organization level. This is highly suitable for HR or IT departments centrally distributing accounts for onboarding employees.π‘ Prerequisite:
Before sending an organization invitation, your organization must have at least one created Team, otherwise there will be nowhere to assign team roles.
To invite members into the organization, go to Members under your organization:Click Invite, where you can choose an invitation method and grant permissions accordingly:Organization Role: Generally, new employees are uniformly assigned the Member role.
All Team Roles: While inviting them into the enterprise, you can directly push them into the corresponding subordinate business pools. You can universally set the same role for all teams, or click "Custom" to open details and precisely specify "They only join Team A as a Member, and remain unjoined in Team B".
2.
Invite via Email (or Bulk Import):
In addition to supporting independent settings for each email and CSV bulk import just like at the team level, you can similarly use the Bulk Config tool at the top to quickly and uniformly configure the Organization Role and specifically assigned Team Roles for this group of people.
Permissions cascade and Default Role Mapping#
It is crucial to understand that Organization Roles and Team/Project Roles operate on two separate tracks. Understanding how permissions cascadeβor don't cascadeβis essential when assigning roles:Organization Roles vs. Team Access: Organization Admins have administrative power over the company's structure (e.g., creating teams, managing billing, and overseeing the member directory). However, they do not automatically gain access to API data within individual projects. To access or edit a project, an Org Admin must still be added to the relevant Team or Project.
Team Admin β Project Editor: Users assigned as Team Admins automatically receive Editor permissions for all projects within that team.
Team Member β Project Read-Only: Users assigned as standard Team Members are granted safe, Read-Only access to the team's projects by default.
Forbidden / Unjoined: If a user is not assigned to a team (or set to Forbidden), they receive no project access within that team.
Note:
These are just the initial baseline permissions. Once inside the team, Team Admins can individually adjust project permissions or customize roles based on the actual business needs.
Custom Project Roles#
Custom roles only support Project level. Organization roles do not currently support customization.
Relation Between Organizations and Teams#
Organization: The highest-level management unit, representing a company or large group. It manages multiple teams.
Teams: A sub-unit within an organization, usually a department or smaller group. It manages multiple projects.
Organization vs. Team β Which Should You Choose?#
When using Apidog, a common question is: should you manage everything directly under an Organization, or mainly rely on Teams? The answer really comes down to two things β team size and business scope.If Your Team is Small and Focused#
Say you've got around ten people all working on the same product line. In that case, a single Team is more than enough. A Team can handle projects, APIs, and members in one place β simple and efficient, without the extra overhead of an Organization.If Your Company is Large and Spread Out#
If you've got lots of people and multiple, unrelated business lines, it's best to create an Organization first, then set up separate Teams inside it for each business area. Each Team manages its own projects and members, with clear boundaries and no overlap.Updating Organization Info#
Admins can update the organization's name or details from Settings. All members will see the updated info.Transferring the Organization#
The organization owner can transfer ownership to another member via Organization Settings β Danger Zone β Transfer.Dismissing the Organization#
The organization owner can permanently delete the organization under Organization Settings β Danger Zone β Dismiss Organization.Dismissing an organization is permanent and cannot be undone. All teams and projects within the organization will be deleted.
