A Released Meeting Recording Points to the Wrong Access Roster: Revoke and Reauthorize

A released recording linked to the wrong access roster should be treated as an access-association error. Freeze new shares and preserve the current access state. Establish which approved roster actually governs the recording.

Do not use the roster currently visible in a project folder as authority by default. Match the recording itself to the meeting and its approval record. Verify the approved scope against the recording hash and roster version. Then make one documented correction from the observed binding to the authoritative binding.

For Google Meet recordings, the file is saved in the meeting organizer's Google Drive, and its link can also be added to the Calendar event when recording starts at the scheduled meeting time. That creates more than one place to inspect before access resumes. Google Meet Help

How do you identify the roster that belongs to the recording?

Start with immutable and time-bound evidence. Record the file ID and recording hash. Also record the meeting identifier, organizer, recording creation time, and the release event that exposed it. Compare those fields with the approval that named the intended audience.

The approved roster should identify people or groups, their permitted role, the approved purpose, the approving reviewer, and the time or scope limit. If a roster is only attached to another artifact, treat it as context, not authorization for this recording.

Keep the observed roster separate from the authoritative roster. The point is to prove the correction, not to make the present state look tidy.

• Capture the recording hash and file ID before changing access.
• Locate the approval record that explicitly covers this recording.
• Compare principal IDs and roles, not display names alone.
• Record which roster version and reviewer establish the authoritative binding.

Which access routes need to be frozen and checked?

Check direct file permissions, general link access, group-based access, folder inheritance, calendar links, copied links, and downstream shares. A direct-share cleanup is incomplete when a parent folder still grants access.

Google Drive states that files and folders inside a shared folder inherit the folder's permissions, and the parent folder is the primary source of truth for access. If a principal has higher access through a parent, reducing access on the individual file may not solve the exposure. Google Drive Help

Record each route as observed, revoked, retained, or reauthorized. Do not infer that a removed direct share eliminated access without rechecking the full permission path.

• Disable any broad link setting that is outside the approved scope.
• Remove direct access for principals on the wrong roster.
• Inspect parent folders and groups for inherited access.
• Preserve approved access only after the authoritative roster is confirmed.

How should mistaken viewers and shares be revoked?

Revoke the wrong access first. In Google Drive, the owner and people with edit access can change sharing permissions, while the available role controls differ for viewers, commenters, editors, and owners. Google Drive Help

Use the platform's access-management control for each specific principal or broader sharing route. Google Drive documents removing a person's access and changing general access to Restricted. Those are platform actions, not proof that every inherited route has been removed. Google Drive Help

Where a release copied the recording into another system, revoke access in that system too. Microsoft 365 video and audio sharing can be managed through Manage access, including Stop sharing. Microsoft Support

• Timestamp the revocation and identify the actor.
• Record the principal ID, access route, previous role, and result.
• Check for inheritance or duplicated files after each revocation.
• Keep any exception open until a reviewer confirms its approved scope.

When can the approved roster be reauthorized?

Reauthorize only after revocation evidence confirms both the recording identity and authoritative roster. Add the approved principals with the minimum role required by the approved scope, then verify the final state from the file and any controlling parent folder.

Do not treat an access correction as a reason to widen sharing. Google Drive distinguishes Viewer, Commenter, Editor, and Owner roles, and the owner can control whether viewers and commenters can download, print, or copy a file. Choose only the approved role and settings. Google Drive Help

If a group is the approved audience, verify the group itself rather than assuming every current member belongs in scope. Record the group identifier and its approved use. Also identify the reviewer who accepted it.

What should the audit record prove before access resumes?

The audit record should let a reviewer reconstruct the mistake and the correction without reading private meeting content. Keep identifiers, timestamps, permission paths, roster versions, reviewer decisions, and the final verification result.

NIST describes its control catalog as flexible and customizable within an organization-wide risk-management process. Use that as a reason to make this ledger fit the organization's approval and incident process, not as a claim that one fixed template satisfies every environment. NIST

Recommendation: require a reviewer who did not perform the change to compare the final access state against the authoritative roster. The reviewer should confirm both the corrected edge and the absence of the old edge.

• Recording hash and file ID match the correction record.
• Observed and authoritative roster IDs remain distinct in the ledger.
• Every discovered access route has a disposition and timestamp.
• A reviewer has confirmed the final approved principals and roles.

What if the old roster cannot be reconstructed?

Keep the recording restricted and mark the reassociation unresolved. Do not restore access from an incomplete list or from the fact that someone previously received a link.

Build the authoritative roster from the approval evidence that explicitly covers the recording. If that evidence is missing, route the decision to the person or function authorized to approve access, then capture the new decision as a dated roster version.

The absence of a usable historical roster is an evidence gap. It is not approval to reuse the nearest current roster.