Remove explicit content access assignments for one or more users or groups from a specific TeamSite item, including TeamSite home when itemId is root. Use this operation when an integration needs to revoke direct access that was previously granted on a file, folder, or TeamSite root.
When removal succeeds, the specified members are removed from the target item's explicit access list. Depending on service rules, removal may also affect inherited or upstream access relationships that originate from the same assignment chain.
Domain Terms
TeamSite root: the top-level home location of a TeamSite, addressed by itemId: root.
Upstream folders: parent folders between the target item and TeamSite root that participate in inherited access behavior.
TeamsiteOwner and ProfileManager: administrative roles with elevated TeamSite permissions that may not be removable in some scenarios.
Removal Rules
Full-control members cannot be removed from any content with this operation.
TeamSite administrative members (TeamsiteOwner or ProfileManager) cannot be removed from TeamSite root.
The caller must have CanManage permission on the target content or relevant upstream path.
Removing access on TeamSite root requires CanManage permission on TeamSite root itself.
The caller cannot remove their own access.
The caller cannot remove the last remaining group that grants their own access.
Recent Requests
Log in to see full request history
Time
Status
User Agent
Retrieving recent requests…
Loading…
Responses
204
Successfully removed the requested explicit content access entries.
403
Forbidden. The caller lacks permission to manage content access for the requested item. In some legacy environments, expired or missing authentication may also surface as 403; clients should handle both 401 and 403 for auth-related failures.
404
Not Found. The TeamSite or target item could not be found for the provided identifiers.
500
Internal Server Error. The service failed while removing content access from the requested item.