Thought I would give this a proper feature request after talking about it in different places.
When you give someone “Creator” access to a space, you allow them to edit data, as well as configure views. These are VERY different powers, both put in the same place. I would love it if my team could make and adjust views in the space as they need. But I do NOT want them to adjust the databases. Right now this is not possible.
I’m aware this WILL be possible with the new access, but it would mean to make everyone creator in all spaces, then remove the all DB access to editor in all spaces. Its not ideal.
EDIT:
I realize actually this isn’t true. If I make someone a creator in a space and restrict access to some db’s, cant they still make new dbs in the space? This is not the desired behaviour…
Suggestion: remove the concept of a global “Space Access”. In the space access settings you see: “Views” and “Databases”, then you can configure who can edit, configure, create, delete views. And also configure who can edit, configure, create, delete databases.
I think it makes sense because the only time you would want to give different to space vs databases, is then you want to give/revoke access to views in said space. So why not make it simpler and more intuitive to do so?
EDIT:
One solution I came up with was to make a “Playground” space, with no databases, and creator access to everyone. Here my team can make views, but not edit databases. Then embed these views in their dashboards. This was the only logical workaround I found for now.