List who a collection is shared with
GET /collections/{id}/acls
Lists every sharing grant stored on a collection: who it names, the level, when it was last granted and by whom, and when it expires.
You need to be signed in. The collection’s owner and holders of
collections.admin or system.admin granted globally can see the
list. Being able to read the collection, having it shared with you,
or the collection being public isn’t enough. Others get 403. The
collection is looked up through each server’s cached copy of its
details, so one that doesn’t exist answers 404, and a deleted one
does too unless the server still holds an out-of-date copy.
Every stored grant is listed, including expired ones and old role
or team grants, which give no access, most recently granted first,
with no paging. Only a user grant that hasn’t expired lets someone
read the collection, and the level makes no difference.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The collection’s id.
Responses
Section titled “ Responses ”The grants stored on the collection.
object
Who the grant is for, as stored: a user’s numeric ref, or a role’s
or team’s UUID.
When the grant was last written. Granting the same principal and level again resets it.
The ref of the account that last wrote the grant, or null if none is recorded.
When the grant stops giving access, or null if it doesn’t expire.
A grant whose time has been reached is still stored and listed, but
gives no access.
Authentication required, missing, or invalid
object
Human-readable error summary
Example
the request could not be completedExample
{ "error": "authentication required: sign in and retry with a valid session or API token"}Authenticated but missing required capabilities
object
Human-readable error summary
Example
the request could not be completedResource not found
object
Human-readable error summary
Example
the request could not be completed