(Edge case) Handling of collaborative projects with complicated ACL

[anngvu]

Describe
(Reporting here for future design improvements.)

Currently, in order to see and select a folder for annotation, the user first must be able to see to a project by having edit access on the project.

In this tricky case, there is a collaborative project involving two labs, one Owner and the other Contributor. The Contributor lab is granted local edit permissions for specific folders within the project, but they don’t actually have edit access on the entire project (Owner lab would prefer Collaborator lab not to have edit access to other data by default, and local settings on every folder are hard to manage).

When Collaborator lab goes to DCA, they can't see the specific folder that they are collaborating on and want to annotate because they don't even see the project. To resolve this, we did just add them with edit permissions on the project, but this might not be what's really wanted/acceptable in other cases.

I think this is related to an existing suggestion somewhere along the lines of "can we add the curator link a folder directly, and if the person has access they can just do the annotation?"

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Priority (select one)

• Minor ⬇️
• Major 📢
• Critical 🆘

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (if applicable, please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[MiekoHash]

@AmyHeiser for visibility.

[AmyHeiser]

Thanks @anngvu. For the example you provided, would the user have edit access to the individual folder? you also mentioned that would be hard to manage so want to confirm that this is a desired state with access granted at folder level.