---
title: "Get a deployment RBAC team"
method: GET
path: "/api/permissions/v2/deployments/{deploymentId}/teams/{teamId}"
tags: ["TeamsService"]
---

# Get a deployment RBAC team

`GET /api/permissions/v2/deployments/{deploymentId}/teams/{teamId}`

Get a deployment's Role-Based Access Control team

## Path parameters

- `deploymentId` integer, required — The unique numerical identifier for the deployment.
- `teamId` integer, required — The unique numerical identifier for the team.

## Response `200`

OK

- ProtosPermissionsV2GetDeploymentTeamResponse
  - `team` ProtosPermissionsV2Team — An individual RBAC team
    - `id` string, int64 — The unique numerical identifier for the team.
    - `deploymentId` string, int64 — The unique numerical identifier for the deployment.
    - `name` string — The name of this team.
    - `slug` string — The slug of this team's name.
    - `parentTeamId` string, int64 — The Team ID of this team's parent team. If unset, the team is an organization-level team.
    - `repositoryCount` string, int64 — The number of repositories directly assigned to this team.
    - `userCount` string, int64 — The number of users directly assigned to this team.
    - `childTeamCount` string, int64 — The number of teams directly assigned to this team.
    - `isProjectDefault` boolean — Whether new repositories are automatically assigned to this team.
    - `isUserDefault` boolean — Whether new users are automatically assigned to this team.
    - `authorizedScopes` string[] — The scopes the the caller has for this team. | value | description | |-------|---------------| | TEAM_SCOPE_DIRECT_MEMBER | Indicates that the user is a direct member of the team | | TEAM_SCOPE_MANAGE | Indicates that the user can manage the team |

---

[API](https://skmtc.net/semgrep/apis/semgrep-web-app.md) · [All operations](https://skmtc.net/semgrep/apis/semgrep-web-app/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/semgrep/semgrep-web-app/versions/6483eeecd582/schema)