Set Up Projects for Team Use

Axe Developer Hub lets you create and manage multiple users per project to control access to your projects. This guide explains how to view, add, and manage project members and their permissions.

Understanding Member Roles

Projects have two permission levels for members:

Project member: can run tests and view results within the project.

Project admin: can do everything a project member can, plus manage project settings and control member access.

In addition, organizational administrators (org admins) can manage members and project settings for any project in their enterprise, regardless of whether they are a member of that project. Org admin status takes precedence over project-level roles. Org admins also see all projects in the enterprise on their projects page, not just projects they belong to.

Viewing Project Members

The members page displays everyone who has access to the current project. To access this page, navigate to your projects page and click on the Settings dropdown and select Members.

The members list shows each person's name, email address, and their assigned role. If a member lacks an active license, a License required warning appears beneath their name. Members without licenses cannot access the project, even if they appear on the list.

For projects with many members, use the pagination controls at the bottom of the list to navigate between pages. You can also sort the list using the dropdown menu above the member table.

Adding Members to a Project

To add new members, select the Add members button on the Members page. A dialog opens where you configure the new members.

You can add anyone from your Axe Account to a project. If the person you want to add does not appear in the list, an Axe Account administrator will need to add them to the Axe Account first.

Changing a Member's Role

To modify a user's permissions, find them in the members list and select Change role in the Actions column.

A dialog appears with the two role options. Select the new role you want to assign, then select Save to confirm the change. Select Cancel to keep the current role.

Removing Members from a Project

To remove someone's project access, locate them in the members list and select Remove in the Actions column.

A confirmation dialog asks whether you're sure you want to remove that person from the project. Select Remove Member to confirm, or Cancel to keep them in the project.

Leaving a Project

If you're a member of a project and want to remove yourself, select Leave next to your own name in the Actions column. If you are an admin on a project, there must be at least one other project admin for the leave option to appear. This option appears instead of Remove when viewing your own entry.

A confirmation dialog asks whether you're sure you want to leave the project. Select Leave project to confirm and remove your own access, or Cancel to remain in the project.

License Requirements

Only members with active licenses can access projects. When adding members, the dialog displays an important notice reminding you of this requirement. Members without licenses appear in the project's member list, but cannot use the project until they receive a license.

If you see the License required indicator next to someone's name, contact your org admin to arrange license assignment for that user.

• For Axe Dev Tools for Web APIs, CLI, or Axe Watcher, users need an Axe Developer Hub license.
• For Axe DevTools for Mobile, users need an Axe DevTools for Mobile license.