Sharing Quickbase apps publicly with Everyone on the Internet (EOTI) group allows you to create extended workflows that include people who do not have Quickbase accounts. These may be customers, clients, or others within your organization.
This article explains acceptable use of the EOTI group. It also gives examples of unacceptable and prohibited usage of the EOTI group. Any process that uses the EOTI group, including those built using intermediary middleware, such as custom code written by a Quickbase Solution Provider (QSP), must adhere to the standards outlined in this article.
In this article
Acceptable use of the EOTI group
Use the EOTI group to share apps publicly for extended workflows that do not involve highly confidential, sensitive, or personal data.
Any workflow that includes sharing your app publicly must comply with all regulatory and legal requirements and governing controls. This is especially true for workflows that involve personally identifiable information (PII). Examples of regulatory and legal requirements and governing controls include but are not limited to, HIPAA and GDPR.
Examples of unacceptable use
Unacceptable use of the EOTI group is any situation that includes:
-
Violating Quickbase’s Acceptable Use Policy
-
Exposing sensitive, confidential, or personal information
-
Using the EOTI group to circumvent licensing costs
More details about unacceptable uses of sharing apps publicly are outlined in the following table.
|
Emulating user credentials |
This involves users locating personal information without signing in. This includes having search fields or reports that allow users to enter identifying information to access data. For example, an ask the user report where users type a last name or phone number to look up their contact record and make edits. In cases where you have used a secure public link, that link may only grant limited access to certain parts of the app. It may not be used to replace user credentials. |
|
Using Quickbase as a High Traffic Content Delivery Network (CDN) |
For uses such as high-traffic requests for images embedded in websites, emails, and other services. Unacceptable use for these public resources is defined as more than 4 requests per second for all the combined resources in a given app. |
|
Credential spoofing |
Building a JavaScript page in Quickbase that provides authentication inputs, other than going directly to Quickbase for true authentication. For example, having a page query a list of data to determine what records someone accessing the page can see, when the information is not free to disclose to the public. |
Quickbase's right to cancel or suspend apps and accounts
We reserve the right to cancel or suspend apps and accounts if we find that you are using the EOTI group to circumvent licensing costs, or in any of the other unacceptable ways outlined in this article.