Granular access controls
Allow more granular controls to limit which members can access which views.
Make Form resizeable in list view
The form showing record attributes in the list view is currently a fixed size.
Basedash database hosting would allow users to create SQL databases from Basedash. No need to use a 3rd party like AWS, Supabase, Digital Ocean, etc. for your database. Ideally there would be a free plan (e.g. 500 Mb of data) and then have a paid plan for more storage.
Ability to create new record on joined table through dropdown
If you're looking at a view, for example in the Basedash demo "[Demo] Users with verified email", and you are adding a new record, if you are selecting from a column that is represented by a foreign key, in this case "Company", it opens a select style box where you can choose a record from the joined table. It would be handy if a new record could be created in maybe a little modal window or something so users don't have to go to the company table/view and create it first. Particularly useful for users not familiar with SQL and foreign key constraints.
Allow custom attributes to be created in Basedash. These attributes would not impact the connected Database, but would allow users to make quick booleans, lists, notes, or any attribute without having to go to the database to do it.
Show more information on foreign key dropdown items
In order to properly distinguish between similar foreign key values, it would be useful to be able to add more information to the display value on foreign key dropdown items. For example, let's take the following examples: There is an orders table, which also contains a foreign key to a positions table and that position's table has a foreign key to a locations table. When editing or adding a order, the user needs to specify the position for the order, and in order to accurately select the position they need to use both the name and location for the position, since position names are not unique across locations. In this case it would be useful for the position foreign key dropdowns to display the following information: Position's primary attribute value Position location's primary attribute Currently we only display the position's primary attribute (as well as it's primary key), but that is not enough information to easily identify correct values from the foreign key dropdown. Yes you could look up the position by it's primary key, but that requires you to navigate to the position table and filter by the primary key to find the additional information you need.