Delete a saved view

Delete a saved view and every share on it.

This also revokes access. A view can be shared with people who are not vault members, and that share is the only thing letting them read the vault through it, so deleting the view cuts off everyone who reached the vault that way. Pending shares to people who had not accepted yet go too. This cannot be undone: recreating the view does not restore the shares.

The view has to belong to the vault in the path. A view ID from another vault returns 404, even when the caller can reach both vaults.

The documents, columns, and extracted data in the vault are untouched. Only the saved layout and its shares go away.

Requires the editor or owner role in the vault, the organization-level permission to manage vaults, and the organization-level Manage Views permission. A caller who holds the vault role but not both permissions gets 403.

Requires a user-scoped API key (u:gcai_...). A vault is shared with named people, so an organization-scoped key has no identity to resolve vault access with.