.nh
.TH "GT-TEAM" "1" "Nov 2026" "gitea-cli" "gitea-cli Manual"

.SH NAME
gt-team - Manage organization teams and access


.SH SYNOPSIS
\fBgt team [flags]\fP


.SH DESCRIPTION
Manage the teams of an organization: what they may do in its repositories, who belongs to
them, and which repositories they can reach.

.PP
In JSON, access is the team's effective access as the text views show it, such as write or
"write (code, issues, pulls)"; permission is the team-wide level Gitea reports, which is none
for a team that grants its access per unit.


.SH OPTIONS
\fB-h\fP, \fB--help\fP[=false]
	help for team


.SH OPTIONS INHERITED FROM PARENT COMMANDS
\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--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 SEE ALSO
\fBgt(1)\fP, \fBgt-team-create(1)\fP, \fBgt-team-delete(1)\fP, \fBgt-team-edit(1)\fP, \fBgt-team-list(1)\fP, \fBgt-team-member(1)\fP, \fBgt-team-repo(1)\fP, \fBgt-team-view(1)\fP