For an alternative way to control access
to individual objects in your buckets, see Access Control Lists.
For more information about controlling access to Cloud Storage
resources, read Overview of Access Control.
Required roles
To get the permissions that you need to set and manage IAM
policies for managed folders, ask your administrator
to grant you the Storage Folder Admin (roles/storage.folderAdmin)
IAM role for the bucket that contains the managed folders.
This role contain the following permissions, which are required to set
and manage IAM policies for managed folders:
storage.managedFolders.getIamPolicy
storage.managedFolders.setIamPolicy
You can also get these permissions with custom roles.
In the list of buckets, click the name of the bucket that contains the
managed folder you want to set an IAM policy on.
In the Bucket details page, click the More options icon
more_vert in the
Folder browser pane next to the managed folder you want to set an
IAM policy on.
If you want to control access within a folder or a simulated folder,
follow the steps in Create a managed folder to enable management on the
folder or simulated folder.
Click Edit access.
In the Permissions for MANAGED_FOLDER_NAME
pane, click Add principalperson_add.
In the New principals field, enter the principal for which you want
to grant access. For more information about principals you can include,
see Principal identifiers.
In the Assign roles section, use the Select a role drop-down to
specify the level of access you want to grant to the principal.
Click Save.
Command line
Create a JSON file that contains the following information:
IAM_ROLE is the IAM role
you are granting. For example, roles/storage.objectViewer.
PRINCIPAL_IDENTIFIER identifies who you are
granting managed folder access to. For example,
user:jeffersonloveshiking@gmail.com. For a list of principal identifier
formats, see Principal identifiers.
PRINCIPAL_IDENTIFIER identifies who you are
granting managed folder access to. For example,
user:jeffersonloveshiking@gmail.com. For a list of principal identifier
formats, see Principal identifiers.
In the list of buckets, click the name of the bucket that contains the
managed folder for which you want to view IAM policies.
In the Bucket details page, click the More options icon
more_vert in the
Folder browser pane next to the managed folder for which you want to
view the IAM policy.
Click Edit access.
The Permissions for FOLDER_NAME pane displays the
permissions on the managed folder, including the principal,
role, inherited roles, and IAM conditions.
In the list of buckets, click the name of the bucket that contains the
managed folder for which you want to view IAM policies.
In the Bucket details page, click the More options icon
more_vert in the
Folder browser pane next to the managed folder for which you want to
remove a principal.
Click Edit access.
In the Permissions for FOLDER_NAME pane,
enter the name of the principal in the Filter field.
Click the Delete icon delete
to delete the principal.
Cloud Storage deletes the principal from your managed folder.
BUCKET_NAME is the name of the bucket that
contains the managed folder you are revoking access to. For example,
my-bucket.
MANAGED_FOLDER_NAME is the name of the managed
folder whose IAM policy you want to remove. For
example, my-managed-folder/.
PRINCIPAL_IDENTIFIER identifies who you are
revoking access from. For example, user:jeffersonloveshiking@gmail.com. For a
list of principal identifier formats, see Principal identifiers.
IAM_ROLE is the IAM role
you are revoking. For example, roles/storage.objectViewer.
JSON_FILE_NAME is the path for the file
that you created in Step 3.
BUCKET_NAME is the name of the bucket that
contains the managed folder you are revoking access to. For example,
my-bucket.
MANAGED_FOLDER_NAME is the name of the
managed folder whose IAM policy you want to remove.
For example, my-managed-folder/.
Use IAM Conditions on managed folders
The following sections show you how to add and remove
IAM Conditions on your managed folders. To view the
IAM Conditions for your managed folders, see
Viewing the IAM policy for a managed folder. For more
information about using IAM Conditions with
Cloud Storage, see Conditions.
Create a JSON or YAML file that defines the condition, including the
title of the condition, the attribute-based logic
expression for the condition, and, optionally, a description for
the condition.
BUCKET_NAME is the name of the bucket that
contains the managed folder to which you are granting the principal
access. For example, my-bucket.
MANAGED_FOLDER_NAME is the name of managed
folder to which you are granting the principal access. For example,
my-managed-folder/.
PRINCIPAL_IDENTIFIER identifies who the
condition applies to. For example, user:jeffersonloveshiking@gmail.com. For a
list of principal identifier formats, see Principal identifiers.
IAM_ROLE is the IAM role
you are granting to the principal. For example,
roles/storage.objectViewer.
CONDITION_FILE is the file you created in the
previous step.
Alternatively, you can include the condition directly in the command
with the --condition flag instead of the --condition-from-file flag.
VERSION is the
IAM policy version, which is required to be 3
for managed folders with IAM Conditions.
IAM_ROLE is the role to which the
condition applies. For example, roles/storage.objectViewer.
PRINCIPAL_IDENTIFIER identifies who the
condition applies to. For example, user:jeffersonloveshiking@gmail.com.
For a list of principal identifier formats, see
Principal identifiers.
TITLE is the title of the condition. For
example, expires in 2019.
DESCRIPTION is an optional description of
the condition. For example, Permission revoked on New Year's.
You should set the minimum role possible that gives the principal
the required access. For example, if a team member only needs to view
the managed folders in a bucket, grant them the Storage Object Admin
(roles/storage.objectAdmin) role instead of the Storage Folder Admin
(roles/storage.folderAdmin) role.
Similarly, if the team member needs full control of the managed folders
in a bucket, grant them the Storage Folder Admin (roles/storage.folderAdmin)
role instead of the Storage Admin (roles/storage.admin) role.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2026-06-09 UTC."],[],[]]