As a storage owner,
I want to know which users and applications read/write/append access to documents in my storage,
So that I can prevent accidental overpermissioning in a storage with many resources.

Preconditions:

What conditions must be in place or assumed before this use case can begin?

NA

Trigger:

What (user or system) event or action initiates this use case?

Storage owner uses an access management interface to request a list of any users and applications who have read, write or append access to any resources within a container.

Actors:

Describe the primary actor, and any other relevant actors involved in this use case

Storage owner - owner of a storage
Other users - any entity that has been given direct or role based access to resource

Distinction:

What unique challenges or distinguishing factors (like technical issues, user experience needs, workflow integration, etc.) are associated with this use case?

This is currently a challenge in Solid as servers do not pre-compute this information; instead clients need to traverse the resource heriarchy and read all of the acls in order to determine which applications and users have permissions to access resources within a container.

Scenario:

Describe an ideal or happy-case scenario where this use case would play out as intended.

Alternative case(s):

What alternative flows or variations should the system handle for this use case?

The access management application is able to fetch the data about who has access to a container in a single request.

Error scenario:

What unexpected issues or errors might arise, and how should the system handle them?

Acceptance Criteria:

What conditions or criteria must be met for this use case to be considered successfully handled? What limitations are acceptable?

References:

List any relevant resources or examples that could inform this use case, possibly from other domains or solutions.