October 2025 role update

New access control roles: viewer and team admin

Note: No permissions of existing Swarmia users were changed. You can start using the new roles at your own pace or continue with the existing ones. You can find the detailed permissions for each role in the roles and permissions article.

Viewer and team admin roles

On October 17th, 2025, Swarmia introduced two new roles to give organizations more granular access control:

• Viewer role can't edit organization or team settings, and they don't have access to software capitalization or to create developer experience surveys or initiatives. Use the viewer role to limit who can edit team and organization settings.

• Team admin role grants access to team configuration and settings for a specific team and its sub-teams, and they can assign more admins to their team(s). A user can be a team admin role for one or more teams. Using the team admin role is recommended for organizations that want more control over who can access Swarmia settings, while delegating team configuration to specific people.

Each Swarmia user has one organization-wide role (organization admin, editor, or viewer), and in addition, they can have a team admin role for one or more teams.

Other changes:

• Renaming the member role to editor to reflect the broad permissions better

• Renaming the admin role to organization admin to distinguish it from the team admin role

Permissions of existing Swarmia users were not changed. The editor role (old member role) remains the default role for new users, and organization admins can change the default to viewer or organization admin.

Taking the new roles into use

If you want more control over who can configure Swarmia settings, start by changing user roles from 'editor' to 'viewer', set the default role to 'viewer', and assign one or more team admins for each team. In role settings, you can filter users with the editor role, select them, and change their roles to viewer in bulk.

Select one or more contributors to assign roles.

Next, change the default role from 'editor' to 'viewer' to ensure the new members of your Swarmia organization get the viewer role.

Set default role to define which permissions new members have when they join your Swarmia organization.

Finally, assign team admins in team settings by editing one team at a time. If you are using parent teams, you can assign admins for the parents and ask them to assign admins for their sub-teams. In team settings, you can find admins for all teams and identify which teams don't have one.

Assign team admins by editing a team.