Screen for public users to create rows (app access is Basic logged in user or above)

[saz33m1]

Using the tutorial sample data, I have an employees table (with access set to Basic logged in users). I want a public form (screen) to be able to submit rows.

I tried the solution detailed in #10563, however, I don't want public users to read my employees table, and only be able to create rows.

Right now, I am getting "Session Unauthenticated" error when viewing the the public form (screen) as an unauthenticated user.

Any help is appreciated it.

[saz33m1]

Using the the latest release 3.2.1. When I try to bring up the public form, it displays, but shows an error and won't let me submit (create new row in table set to private access).

[mikesealey]

Hi @saz33m1

The way permissions operate has been worked on recently and updated in last week's Budibase v3 Launch Week. This means that if the information discussed in May 2023 does not apply, it will likely be outdated.

When setting a table's permissions to "Public" the table can be written to from a public screen in your app. If you are still encountering the "Session not authenticated" error message this may be a bug and you should submit an issue here: https://github.com/Budibase/budibase/issues/new/choose

I have just tested this, and a Public table can be written to from a public form. There is an ongoing discussion within the engineering teams regarding public-write-logged-in-read permissions. There are currently no feature requests for this issue, you may wish to submit a feature request using the link above. You could provide more specifics on your intended use-case which may help to shape any future updates in this area.

I will be meeting with the rest of the team throughout the week and we could discuss your feature request further.
Mike

[SimonDoll]

HI @mikesealey thanks a lot for looking into that!

I'm currently facing the exact same issue / missing feature of public-write-logged-in-read which was possible with Budibase < 3.0
If it helps, I could also submit a feature request @saz33m1 / upvote Yours when it exists.

A prototypical use-case is nicely illustrated in one of your templates: visitor-check-in-form template @mikesealey (see #14973).
In my case, we have a lot of "single-time" customers and a restricted timeframe.
Therefore, the customers just enter some details about themselves and submit their cases, but should never have access to other cases and don't need to change their case. Also, we don't want them to go through a register process since they will most likely not return / time is limited.

Sadly, the new permissions currently prevent me from migrating my apps to Budibase>=3.0

I hope that helps and that @mikesealey and the team find a solution 👍