Ameeting space representsa virtual place or a persistent object (such as a meeting room) whereconferences are held. A meeting space also helps users meet and find sharedresources.

When you create a meeting space using thespaces.create method,it returns an instance of aspaces resource. The resourceincludes theSpaceConfig objectthat's the configuration for the meeting space. It also contains theActiveConferenceobject that's a link to the currentconferenceRecordsresource within the meeting space. For more information on managing a meetingspace, seeCreate and manage meetingspaces.

The following sections detail how to configure a meeting space using theseobjects and methods.

Set moderation and meeting access

You can set how users join a meeting, the moderation modes, the featurerestrictions, and the permissions users receive when they join a meeting,through theSpaceConfigobject.

Access meeting spaces

To determine who can join a meeting space without knocking, set theaccessTypefield using theAccessType object.You can choose from multiple settings on whether to automatically allowattendees to join. The field defaults to the user's default access settings.

To define the entry points that can be used to join meetings hosted in a meetingspace, set theentryPointAccessfield using theEntryPointAccessobject. Set toALL to allow all entry points orCREATOR_APP_ONLY to scopethe entry points to only those owned by the Google Cloud project that created themeeting space.

Moderate meeting spaces

To moderate a meeting, you can set themoderationfield using theModeration object.When themoderation mode ison, the meeting organizer has control over themeeting with features such as co-host management (seespaces.members)and feature restrictions using themoderationRestrictionsfield. For more information on members, seeManage spacemembers.

To define feature restrictions when the meeting is moderated (moderation ison), set themoderationRestrictions field using theModerationRestrictionsobject. The restrictions define who has permission within the meeting space tosend chat messages or reactions, or to share their screen.

To set the feature restrictions on themoderationRestrictions field, use theRestrictionTypeto apply thechatRestriction,reactionRestriction,presentRestriction. SettoHOSTS_ONLY to apply the permissions to both the meeting organizer andco-host, orNO_RESTRICTION to apply to all participants.

To restrict the default role assigned to users as viewer, set the booleandefaultJoinAsViewerTypefield using theDefaultJoinAsViewerType.IfdefaultJoinAsViewerType ison, users join as viewers. Ifoff, usersjoin as contributors. Default isoff. If an explicit role is set for a user inspaces.members, the user joins as that role.

Generate attendance report

To create an attendance report for the meeting space, set theattendanceReportGenerationTypefield using theAttendanceReportGenerationTypeobject. If a report is requested, Google Meet saves the attendance report tothe meeting organizer's Google Drive and an email is also sent.

Manage auto artifacts

Meeting organizers, but not co-hosts, can pre-configure auto-recording,auto-transcripts, and smart notes within the meeting space. When these settingsare enabled, the meeting space is recorded, transcripts are generated, andmeeting notes are captured and organized into Google Docsautomatically. Each feature is independent and is set per meeting space.Recording captions are only available in English.

You can pre-configure the auto artifacts either when youcreate a meetingspace or oncethe meeting space is created. Both methods require themeetings.space.settingsOAuth scope. For more information, seeOAuth scopes forsettings.

You can also set up auto artifacts for meetings created from Google Calendar.

To set auto artifacts, use theArtifactConfig object, within theSpaceConfigobject.ArtifactConfig is made up of therecordingConfig,transcriptionConfig, andsmartNotesConfig fields.

Each field is mapped to a similar object such asRecordingConfig,TranscriptionConfig,andSmartNotesConfig. To set each object, use theAutoGenerationTypeto toggle the config objecton oroff.

To retrieve the artifacts created during a conference, seeWork withartifacts.

Difference between transcripts and smart notes

While both meeting transcripts and smart notes (also known as "take notes forme") capture information from your meeting, these features serve differentpurposes and produce different artifacts.

The following table shows how they differ:

Feature	Transcripts	Smart notes
Overview	A verbatim, word-for-word record.	A concise summary of key points generated by Gemini.
Detail level	100% detail. Everything said is written down.	High-level. Focuses on decisions and action items.
Use case	Legal compliance, checking exact quotes, and user accessibility.	Allows late participants to catch up instantly; automates minute-taking and project tracking.
Real-time usage	Used for captions. The file is generated after the call.	You can view the summary building in the side panel during the call.
Output	A long Google Docs document with speaker name and timestamps.	A concise Google Docs document of meeting notes with sections and bullet points.
Citation	Contains the full text that can be linked to.	Includes citations (timestamps) that link back to the specific moment in the transcript for context, if both transcripts and smart notes are enabled. For more information, seeWhen both features are enabled.

When both features are enabled

While each feature can be used separately, both transcripts and smart notes canalso be used at the same time to create better post-meeting artifacts.

When both are enabled, you'll see citations in your generated smart notesdocument. These citations are located throughout the details section and link tospecific timestamps in the meeting transcript. By clicking on these citations,you can jump directly to the relevant section in the transcript to gain a deeperunderstanding of the discussion.

During the meeting, participants see indicators that both features are active.They must remain active for the duration of the meeting to generate clickablecitations. Even though the files are interlinked, the system still generates twodistinct documents in the host's Google Drive. Both files are alsoautomatically attached to the Google Calendar event.

OAuth scopes for settings

Setting or accessing meetings settings requires the following OAuth scopes:

Use case	Scope code
Set auto artifact generation for spaces created by other apps.	https://www.googleapis.com/auth/meetings.space.settings
Get or list artifacts from conferences created by other apps.	https://www.googleapis.com/auth/meetings.space.readonly
Get or list other pre-meeting settings of a meeting space created by a third-party app.	https://www.googleapis.com/auth/meetings.space.created https://www.googleapis.com/auth/meetings.space.readonly
Read and edit the settings for all meeting spaces a user can access through any other app, such as Calendar.	https://www.googleapis.com/auth/meetings.space.settings

For more information on OAuth scopes, seeMeet REST APIscopes.

Manage space members

Developer Preview: Available as part of theGoogle Workspace Developer Preview Program,which grants early access to certain features.

A space member is a user who's configured to have a role in the meeting space.These users can join the meeting space without requesting permission to connect(also known as "knocking").

While meeting organizers can automatically enter the meeting space, you can alsoconfigure additional members to join the meeting without knocking. Additionally,members can be configured to have aRole in the meeting, such asCOHOST which gives them the same abilities to managethe meeting as the meeting organizer. For more information about accessing ameeting space without knocking, seeAccessType.

Thespaces.members resource includes thename,user, androle fields.

Note that a member is different from aparticipant. A participant is aperson joined to a call or that usesCompanionmode, watching as a viewer, ora room device connected to a call. There's oneconferenceRecords.participantsresource for each person.

You can manage space members using the following methods:

• spaces.members.create
• spaces.members.delete
• spaces.members.get
• spaces.members.list

Note: To call these methods, use the/v2beta/ URL endpoint. For example, theHTTP request for thespaces.members.list method becomeshttps://meet.googleapis.com/v2beta/spaces/{space}/members.

Each method takes a path parameter with the create and list methods using theparent field to denote the meeting space, and the delete and get methods usingthename field to filter the results based on the meeting space and the membername. All methods, except delete, return an instance of thespaces.membersresource.

All methods, except delete, support thefields parameter inSystemParameterContext.When thefields parameter is omitted, the API response defaults to"name,email,role,user".

Thefields parameter relies on aFieldMaskfor response filtering. A FieldMask is a way for API callers to list fields arequest should return. It's a comma-delimited list of fields to specify onlycertain fields in an object are used while leaving the other fields unchanged.Using a FieldMask allows the API to avoid unnecessary work and improvesperformance. A field mask is used for create, get, and list methods. For moreinformation on field masks, see Google Sheets API'sUse fieldmasks.

Related topics

• Start or schedule a Google Meet video meeting
• "Take notes for me" in Google Meet
• Use Transcripts with Google Meet