I'm testing out the new Prisma admin, and I have a question (and possibly a feature request) related to one the questions in your announcement:
What are your database workflows, and how can Admin help simplify them further?
Many members of my team are usually working quite closely with the raw data, but without working on the technical stuff like defining models, relationships and whatnot.
However, they're usually not working directly on our databases (due to different reasons I won't go into here), instead we're managing amendments, overrides and so in our applications.
With the new admin, it's really starting to look like we can get rid of some of this extra complexity and instead just have the team working directly with the data through the admin interface. The admin seams to be able to provide good direct access to the data, while at the same time providing a nice and clean UI where people are not afraid to make changes to it.
However, in some circumstances it would be beneficial to limit e.g. write access to certain tables/collections, and let some collections only be handled only through prisma and our application.
I'm imagining user access could be implemented through e.g. database users and their privileges (or other ways), and then allowing people to sign into the admin based on these user rights.
Is this something that you have considered or would consider?
I'm well aware that this may be out of the scope of the admin, and that this is typically implemented in standalone applications or custom admin UI's. But in our workflows, the admin could potentially save us from a lot of mundane work related to changing/overriding data. Combined with the value of a pluggable and custom UI, we could just let everyone work through the same UI, instead of having to reimplement many of these things ourselves!
I'm testing out the new Prisma admin, and I have a question (and possibly a feature request) related to one the questions in your announcement:
Many members of my team are usually working quite closely with the raw data, but without working on the technical stuff like defining models, relationships and whatnot. However, they're usually not working directly on our databases (due to different reasons I won't go into here), instead we're managing amendments, overrides and so in our applications.
With the new admin, it's really starting to look like we can get rid of some of this extra complexity and instead just have the team working directly with the data through the admin interface. The admin seams to be able to provide good direct access to the data, while at the same time providing a nice and clean UI where people are not afraid to make changes to it.
However, in some circumstances it would be beneficial to limit e.g. write access to certain tables/collections, and let some collections only be handled only through prisma and our application.
I'm imagining user access could be implemented through e.g. database users and their privileges (or other ways), and then allowing people to sign into the admin based on these user rights.
Is this something that you have considered or would consider? I'm well aware that this may be out of the scope of the admin, and that this is typically implemented in standalone applications or custom admin UI's. But in our workflows, the admin could potentially save us from a lot of mundane work related to changing/overriding data. Combined with the value of a pluggable and custom UI, we could just let everyone work through the same UI, instead of having to reimplement many of these things ourselves!