It would be great if Observers could submit forms or add entities (submitter permission).
We licensed Fibery for a subset of staff, but we also have others who only need to authenticate to the platform, submit forms (or add entities), and view the related views. They would not edit entities or setup views…
Thanks!
Hey! It was discussed here: Form View - Guest Access
But it was using the old “Guest” terminology, but it’s refering to the current “Observer”
We are a school, and we have an app for students or parents to submit information. They can SSO and get Observer role, but giving them a paid license is not possible for us.
Could you (develop/have developed for you) a custom front-end and host it on your website, then use an API call to POST to Fibery?
In this case, the data will appear to have been created by the user from whose account the API token has been taken, which I suspect is not what OP wants.
sure, but if you have first / last name fields and an email, you could map them easily to a people table
I find this is the solution. Any process that can take in information from an infinite number of external people should not have records attributed to the users database.
To be fair, I think the original request is for a limited number of pre-defined users, who should be able to log in to Fibery (i.e. require authentication) to see stuff, but they should also be able to create records.
Overall, the actual technical requirements are addressed with the current permissions model (i.e. Members who have Submitter access for certain dbs, but are Viewers otherwise) but I think that for some use cases, the cost of user licences for all these people is too much.
Basically, the jump from viewer-only to viewer-plus-submitter is a jump from Observer to Member, and for some use cases, this feels too expensive, given that the users may not be particularly active.
Unfortunately, devising a pricing plan which covers all possible use cases (and without making some people feel like they are paying too much for too little functionality) is tough.
Ah I see, I was thinking more about the use case than the fact that @Cddd actually has observer users already on the platform for these tickets.
I agree that the current permissions & pricing model is right here. Since submitters are effectively users that create records.
My approach for a team like this one, where additional user licenses is not preferred, would be to auto-link users given an email field or use an automation to read the email address value on submission and link the observer.
The latter uses more of the automation quota but, it preserves an easy UX for overwriting the user value