I'm encountering a problem creating a custom role in "IAM & Admin / Roles / Create role" with the intention of granting a service account access to Google Drive and Google Sheets.
Steps I've taken:
Created a Google Cloud project.
Did not use an organization
Enabled the Google Drive API and Google Sheets API.
Verified both APIs are enabled
Created Service Account
Created Custom Role
Successfully assigned "storage.objects.create" permission to role
I checked Organization policies, and it's the 12 that the account started with.
None of them look like they should impact this
Navigated to "IAM & Admin / Roles / Create role. (really edit)"
Clicked "+ Add Permissions."
Filtered by "sheet" nothing shows up
Paged through a crazy number of permissions, didn't see anything that looks like it would be the permission I'm looking for.
Problem:
When attempting to add permissions related to Google Drive and Google Sheets (e.g., drive.files.create, sheets.spreadsheets.create), the "+ Add permission" filter on the custom role I've created for a service account returns no results. I've tried filtering using prefixes like "drive.", "sheets.", "drive.files", and "sheets.spreadsheets", and still, no matching permissions are found.
APIs are enabled: The Google Drive and Google Sheets APIs have been enabled for this project for over 48 hours.
Account Details:
My account's "Role launch stage" is "Alpha."(?)
I'm the account owner, but I'm unsure if this "Alpha" status is preventing me from accessing the necessary IAM permissions. To prevent confusion, I didn't specify an organization to avoid having to deal with some sort of hierarchy permission problem.
Questions:
Is this "Alpha" status restricting access to certain IAM permissions?
Is there any verification process required to remove this limitation?
Thanks in advance, and apologies if I posted this in the wrong place.
Hi @gcloudfng,
Welcome to Google Cloud Community!
Thank you for sharing the detailed steps you’ve taken. It seems that you’ve exhausted all the steps and the “Alpha” stage typically should not hinder you assigning permissions in my experience. Although there might be some API restrictions tied to it or some other issue that I am not aware of as the Alpha launch stage means that the role is still being developed or tested.
It appears that a more thorough investigation of your project is necessary. I highly recommend that you reach out to our 1:1 support for a deep dive on this issue. Please see our Cloud Customer Care documentation.
Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.
@gcloudfng , hi, were you able to solve this problem?
If so, how did you do it.