How to Let Organization Members Create Teams in Apidog

By default, Organization Members cannot create teams in an Apidog organization. An Organization Owner or Admin can enable this permission so members can create organization-owned teams from the Home page.

The creator becomes the new team's Team Owner but remains an Organization Member. Team creation does not grant access to organization management pages.

Before you start

You need:

• Organization Owner or Organization Admin access;
• an Organization Member account for testing;
• a naming and ownership convention for new teams;
• an active organization member who can act as a backup owner if needed.

This setting changes who can create organization-owned teams. It does not change organization roles, project permissions, or the permissions of existing teams.

Step 1: Allow Organization Members to create teams

1. Open the organization settings.
2. Go to Roles and Permissions.
3. Enable the option that allows Organization Members to create teams.
4. Save the setting.

The permission is disabled by default and can be changed by an Organization Owner or Admin.

Organization Owners and Admins can create organization teams regardless of this setting.

Step 2: Test team creation as an Organization Member

Use a pilot Organization Member account.

1. Sign in as the member.
2. Open the Apidog Home page.
3. Create a new team under the organization.
4. Enter the team name and complete the creation flow.
5. Open the new team.

Confirm all of the following:

• the team belongs to the organization;
• the member who created it is the Team Owner;
• the member can manage the new team according to the Team Owner role;
• the member still cannot access organization management pages.

The last check is important. A Team Owner manages that team but does not become an Organization Admin.

Step 3: Review teams and owner status

Organization Owners and Admins can monitor organization teams from the team management page.

1. Open the organization's team management page.
2. Review the Team Owner assigned to each team.
3. Check the owner status for inactive or otherwise unavailable accounts.
4. Search or filter by Team Owner and owner status when follow-up is required.

Use the team list to identify teams whose owners may be unavailable and require an ownership transfer.

A simple operating rule is to review owner status during regular access reviews and before removing a member from the organization.

Step 4: Transfer Team Ownership

Organization Owners and Admins can transfer one or more teams to another eligible organization member.

1. Open the organization's team management page.
2. Select the team or teams that need a new owner.
3. Select Change Owners.

Multiple selected teams can be assigned to the same new owner.

4. Select the new Team Owner.
5. Confirm the transfer.

The new owner must be an eligible, active member of the organization.

The new owner must:

• have a usable Apidog account;
• be an active organization member;
• have an SSO identity associated with the organization when the organization uses SAML SSO.

Pending, removed, disabled, or incompletely associated SSO users cannot be selected.

What changes after ownership transfer

After the transfer:

• the selected member becomes Team Owner;
• Apidog adds the new owner to the team if necessary;
• the previous owner becomes Team Admin if they remain in the team;
• the transfer is recorded in the organization's Audit Logs.

Transferring ownership changes the Team Owner only. It does not move the team into or out of the organization.

Verify the configuration

Run these checks before enabling the permission for all members:

After the pilot, communicate the required naming, owner, and project-creation conventions to members who will use the permission.

Troubleshooting

Important limitations

• The setting allows members to create organization-owned teams; it does not allow them to manage the organization.
• The creator receives the built-in Team Owner role. Custom permissions for team roles are not currently supported.
• Team-level ownership does not automatically determine every project role. Review project access separately.
• Ownership transfer does not transfer the team between organizations.

Related API governance tutorials:

These tutorials cover complementary controls for governing an enterprise API workspace:

• API Governance Framework — connect ownership, controls, evidence, and lifecycle decisions.
• SAML Group Mapping with Microsoft Entra ID — assign team access from identity-provider groups.
• Secret Scanner — review possible exposed credentials in supported Apidog assets.
• Audit Logs — investigate and export administrative organization activity.
• SCIM Provisioning — manage organization users through the identity lifecycle.
• Enterprise Policies — configure credential, membership, SSO-session, and invitation controls.
• Self-Service API Teams — allow member-created teams while retaining ownership oversight.
• GitHub Enterprise Cloud Integration — connect supported GHE.com repositories for OpenAPI workflows.

Related official documentation:

• Managing Teams in an Organization
• Organization Role and Permissions
• Team Roles and Permissions
• Audit Logs