The memberType field must contain a user with the user.name and
user.type fields populated. The server will assign a resource name
and overwrite anything specified.
When a Chat app creates a membership relation for a human user, it must use
certain authorization scopes and set specific values for certain fields:
Set user.type to HUMAN, and set user.name with format
users/{user}, where {user} can be the email address for the user. For
users in the same Workspace organization {user} can also be the id of
the person from
the People API, or the id for the user in the Directory API. For example,
if the People API Person profile ID for user@example.com is 123456789,
you can add the user to the space by setting the membership.member.name
to users/user@example.com or users/123456789.
Inviting users external to the Workspace organization that owns the space
requires user
authentication.
When a Chat app creates a membership relation for itself, it must
authenticate as a
user
and use the chat.memberships.app scope, set user.type to BOT, and set
user.name to users/app.
The memberType field must contain a user with the user.name and
user.type fields populated. The server will assign a resource name
and overwrite anything specified.
When a Chat app creates a membership relation for a human user, it must use
certain authorization scopes and set specific values for certain fields:
Set user.type to HUMAN, and set user.name with format
users/{user}, where {user} can be the email address for the user. For
users in the same Workspace organization {user} can also be the id of
the person from
the People API, or the id for the user in the Directory API. For example,
if the People API Person profile ID for user@example.com is 123456789,
you can add the user to the space by setting the membership.member.name
to users/user@example.com or users/123456789.
Inviting users external to the Workspace organization that owns the space
requires user
authentication.
When a Chat app creates a membership relation for itself, it must
authenticate as a
user
and use the chat.memberships.app scope, set user.type to BOT, and set
user.name to users/app.
Creating app memberships or creating memberships for users outside the
administrator's Google Workspace organization isn't supported using admin
access.
The memberType field must contain a user with the user.name and
user.type fields populated. The server will assign a resource name
and overwrite anything specified.
When a Chat app creates a membership relation for a human user, it must use
certain authorization scopes and set specific values for certain fields:
Set user.type to HUMAN, and set user.name with format
users/{user}, where {user} can be the email address for the user. For
users in the same Workspace organization {user} can also be the id of
the person from
the People API, or the id for the user in the Directory API. For example,
if the People API Person profile ID for user@example.com is 123456789,
you can add the user to the space by setting the membership.member.name
to users/user@example.com or users/123456789.
Inviting users external to the Workspace organization that owns the space
requires user
authentication.
When a Chat app creates a membership relation for itself, it must
authenticate as a
user
and use the chat.memberships.app scope, set user.type to BOT, and set
user.name to users/app.
[[["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 2025-01-28 UTC."],[],[]]
