I think Michael meant submitter access, not sure. But I have the same need. I think I brought it up before.
Situations not possible on space/database permissions:
- Create, view, edit, but not delete.
- Create, view, but not edit or delete (possible with a workaround of providing submitter access to db and view access to space, but not ideal if you dont want to give view access to entire space)
- View and delete, not create or edit.
- Create, view, edit, but not share.
It was chatted about here: Feature Request: Share Space but restrict entity views - #41 by Edan
I still think the granular selector (present in access templates) is much more powerful and even more intuitive than a single select dropdown.