.nh .TH "GT-TEAM-VIEW" "1" "Nov 2026" "gitea-cli" "gitea-cli Manual" .SH NAME gt-team-view - View a team .SH SYNOPSIS \fBgt team view [flags]\fP .SH DESCRIPTION View a team: its access to each repository unit, its members and its repositories. .SS ARGUMENTS .EX A team can be supplied as ORG/TEAM, such as acme/developers, where TEAM is the team's name or ID, or as its numeric ID alone. .EE .SS JSON FIELDS .EX access, all_repositories, can_create_repo, description, id, name, organization, permission, units .EE .SH OPTIONS \fB-h\fP, \fB--help\fP[=false] help for view .SH OPTIONS INHERITED FROM PARENT COMMANDS \fB--csv\fP[=""] Output CSV with the specified comma-separated \fBfields\fR, or all fields .PP \fB--debug\fP[=false] Log the method, URL, status, and duration of each HTTP request to stderr .PP \fB--host\fP="" Gitea instance \fBURL\fR, including any base path .PP \fB--interactive\fP[=false] Allow prompts with machine output .PP \fB-q\fP, \fB--jq\fP="" Filter JSON output using a jq \fBexpression\fR; implies --json .PP \fB--json\fP[=""] Output JSON with the specified comma-separated \fBfields\fR, or all fields .PP \fB--no-input\fP[=false] Disable prompts and implicit editor/browser interactions .PP \fB--sudo\fP="" Perform API requests as this \fBuser\fR (requires an administrator account) .PP \fB--user\fP="" Account \fBname\fR on the selected instance .SH EXAMPLE .EX $ gt team view acme/developers $ gt team view 2 --json units .EE .SH SEE ALSO \fBgt-team(1)\fP