> For the complete documentation index, see [llms.txt](https://docs.dogq.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dogq.io/documentation/team/squads.md). # Squads ### What are Squads Squads in DogQ are essentially access groups that you can create inside your team and assign to different projects, enabling you to flexibly organize the workflow to fit your needs. By default users that you add to your team have a **member** role and without a squad such users have no access to any project and cannot create one by themselves. **Members** can only have access to scenarios through squads.

This tab provides an overlook of your squads, which project(s) they're associated with and how many members they have

To create a new squad, go to the Team page and click on

button. Give it a name and save. Once created, your new squad will be empty. It's now time to add users to it and define which project(s) its members will have access to. To do that, click on

and

buttons, respectively. Here is an example of a squad already with users and projects in it.

In this example, if these two users have **member** roles in the team, they will only be able to see and interact with these three projects. They will not see any other execution records or projects unless they're also enrolled in other squads. ### Squad Roles Like teams, squads have their roles too: Admin and Member. These roles are lower in the permissions hierarchy and do not overlap with team roles permissions, i.e. if a **team member** becomes **squad admin**, they still won't be able to interact with any projects outside of what their squads allow them, unlike **team admins**. #### Squad admin Squad admins can't create new projects or gain access to projects. Their admin privileges are only for squad management: * see the assigned projects * view the records of the assigned projects * configure and edit the assigned projects * execute and schedule the assigned projects * change the squad name * manage squad members and roles * delete the squad * detach the squad from the assigned projects (revoke access) #### Squad member Squad members can only see and edit the projects they have access to: * see the assigned projects * view the records of the assigned projects * edit the assigned projects, i.e. create, edit and delete modules and scenarios inside the assigned projects * execute and schedule the assigned projects * view the squad(s) they're enrolled in {% hint style="info" %} Since **team owner** and **team admin(s)** have access to and can manage all existing projects, the permissions and limitations squad roles entail are only only really relevant for **team members**. {% endhint %} ### Squad Management #### Edit Members 1. click

at the top of the Members panel 2. select the users you want to be in this squad 3. click

to confirm #### Edit Projects Access 1. click

at the top of the Projects panel 2. select the projects you want the members of this squad to have access to 3. click

to confirm #### Assign role 1. click on the "Actions"

icon 2. select "Change Role" 3. in the modal window select a new role and click

#### Remove user 1. click on the "Actions"

icon 2. select "Remove User" 3. in the modal window click

The selected user will be removed from the squad but remain in the team. #### Remove Access to Project In the Projects tab on the right side of each project associated with the squad there is a "Remove Access"

button. Clicking on it will revoke the access the squad's access to the selected project. It is also possible to configure the squad permissions by clicking on the

button. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.dogq.io/documentation/team/squads.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.