feat(files): add safe connector space removal
This commit is contained in:
@@ -724,6 +724,18 @@ All routes below are under `/api/v1/files`.
|
||||
| Incremental connector settings | `GET /connectors/settings/delta` |
|
||||
| Form evidence | `POST /form-evidence/upload` with a short-lived `X-Form-Evidence-Token` issued by Forms Runtime |
|
||||
|
||||
The Files workspace exposes **Remove space** only for read-only connector
|
||||
spaces and only to actors with file-organization authority over the owning user
|
||||
or group space. Confirmation explains the exact boundary: removal soft-deletes
|
||||
the local connector-space definition and makes that virtual view disappear. It
|
||||
does not mutate or delete remote provider content, previously imported managed
|
||||
files, their metadata or shares, the connector profile, credentials, or remote
|
||||
object references. Those retained objects therefore do not block removal and
|
||||
the connector location can be linked again later. User and group managed spaces
|
||||
are intrinsic ownership scopes rather than removable records, so they never
|
||||
offer this action. A missing, already removed, cross-tenant, or inaccessible
|
||||
connector space fails through the backend lookup and owner-access checks.
|
||||
|
||||
Consumers should use cursor/watermark contracts instead of assuming an
|
||||
unbounded complete list. The default full-list page size is 500 and public page
|
||||
sizes are capped at 1,000.
|
||||
|
||||
Reference in New Issue
Block a user