Everyone on the Internet (EOTI) example use cases

Submitting records

Anonymous users submitting records to Quickbase.

Sample scenarios include surveys, appointment requests, or feedback forms. Typically, these submissions are add-only or deposited, meaning once the record is saved, the user does not see or interact with the record again.

Reading and editing existing records

Anonymous users reviewing limited sets of data and editing records.

One common scenario is availability of items such as appointments. Users see a report listing available time slots and edit an appointment record with their information.

Creating and editing records

Anonymous users adding and editing records.

You may have a scenario where users need to create records that can also be edited by other anonymous users.

You may also have a situation where you want users to be able to add parent records along with child records. For example, adding a maintenance request for a specific machine. In this case, users need some limited access to the parent record. (See the section above about using custom permissions.)

Assuming you are okay with the risks of some machine data being exposed, the Machines parent table would have a custom permission that only allowed access to certain records and fields that were necessary for the EOTI role to add maintenance requests.

File attachment access

Providing access to file attachments at a more granular level than what Quickbase offers, that is, using Quickbase without custom code or API access from a separate environment.

An example of this might be a document that doesn’t contain personal or sensitive information but is not appropriate for public consumption, but you need to provide a URL to the file in emails to customers for download. Rather than allowing the entire file attachment field to be accessible, consider conditionally allowing records in a certain status. This allows a file to be accessible for a limited period of time.

Both custom permissions and limited field access should be used. See the section above on using custom permissions.