AI-generated Key Takeaways
-
Permissions define access levels (OWNER, READER, WRITER) for users, groups, or service accounts associated with an issuer ID.
-
Permissions can be managed through the
get
andupdate
methods to retrieve and modify access rights. -
Permissions are structured with an issuer ID and an array of individual permissions, each specifying an email address and a role.
-
The
Permissions
resource provides a comprehensive list of permissions for a given issuer, enabling centralized access control.
Resource: Permissions
JSON representation |
---|
{
"issuerId": string,
"permissions": [
{
object ( |
Fields | |
---|---|
issuerId |
ID of the issuer the list of permissions refer to. |
permissions[] |
The complete list of permissions for the issuer account. |
Permission
JSON representation |
---|
{
"emailAddress": string,
"role": enum ( |
Fields | |
---|---|
emailAddress |
The email address of the user, group, or service account to which this permission refers to. |
role |
The role granted by this permission. |
Role
Enums | |
---|---|
ROLE_UNSPECIFIED |
|
OWNER |
|
owner |
Legacy alias for |
READER |
|
reader |
Legacy alias for |
WRITER |
|
writer |
Legacy alias for |
Methods |
|
---|---|
|
Returns the permissions for the given issuer id. |
|
Updates the permissions for the given issuer. |