.TH "GCLOUD_TRANSFER_AUTHORIZE" 1



.SH "NAME"
.HP
gcloud transfer authorize \- authorize an account for all Transfer Service features



.SH "SYNOPSIS"
.HP
\f5gcloud transfer authorize\fR [\fB\-\-add\-missing\fR] [\fB\-\-creds\-file\fR=\fICREDS_FILE\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

Authorize a Google account for all Transfer Service features.

This command provides admin and owner rights for simplicity. If that's too much
authority for your use case, see custom setups here:
https://cloud.google.com/storage\-transfer/docs/on\-prem\-set\-up



.SH "EXAMPLES"

To see what Transfer Service IAM roles the account logged into gcloud may be
missing, run:

.RS 2m
$ gcloud transfer authorize
.RE

To add the missing IAM roles, run:

.RS 2m
$ gcloud transfer authorize \-\-add\-missing
.RE

To check a custom service account for missing roles, run:

.RS 2m
$ gcloud transfer authorize \e
    \-\-creds\-file=path/to/service\-account\-key.json
.RE



.SH "FLAGS"

.RS 2m
.TP 2m
\fB\-\-add\-missing\fR

Add IAM roles necessary to use all Transfer Service features to the specified
account. By default, this command just prints missing roles.

.TP 2m
\fB\-\-creds\-file\fR=\fICREDS_FILE\fR

The path to the creds file for an account to authorize. The file should be in
JSON format and contain a "type" and "client_email", which are automatically
generated for most creds files downloaded from Google (e.g. service account
tokens). If this flag is not present, the command authorizes the user currently
logged into gcloud.


.RE
.sp

.SH "GCLOUD WIDE FLAGS"

These flags are available to all commands: \-\-access\-token\-file, \-\-account,
\-\-billing\-project, \-\-configuration, \-\-flags\-file, \-\-flatten,
\-\-format, \-\-help, \-\-impersonate\-service\-account, \-\-log\-http,
\-\-project, \-\-quiet, \-\-trace\-token, \-\-user\-output\-enabled,
\-\-verbosity.

Run \fB$ gcloud help\fR for details.



.SH "NOTES"

This variant is also available:

.RS 2m
$ gcloud alpha transfer authorize
.RE