Quick Base in-product messaging


Quick Base leverages in-product messaging channels to reach our administrators and end users. We strive to keep messaging to a minimum to ensure that users are focused on getting work done.

All messages are as targeted as possible. For example, if we are making a security improvement that may impact customers, only the accounts impacted and administrators who can act would see the message.

Regardless of the type of message and audience, Quick Base has a rigorous process to ensure messages are timed appropriately and not overwhelming in quantity to users.


There are four categories of audience we may target. Note that being in one group does not exclude a user from being in another.

  1. Account Administrator: A user logged into Quick Base with support or full administrative permissions to the account and/or realm that a specific app lives within
  2. App Administrator: This may refer to an app administrator in an application, or a person that has ever had administrative rights in any application
  3. App Developer (I.e. “Builder”): A user with create permissions to create / edit / update applications, who may or may not also be an account or app administrator
  4. User: A consumer of a Quick Base application built by a builder

Types of messaging

In-product messages generally fall into two categories:

Providing information

Information surrounding new features or capabilities that are directly related to the task being done by the user, or critical alerts. Examples include:

  • Security alerts or browser updates needed
  • Retirement of features
  • New feature walkthroughs — only present in place with the feature
  • Announcement of availability of a feature that is included with the user’s subscription – usually in a place that is contextually relevant
  • Resources available to help customers get more value from the product and could include things like upcoming events or webinars, tools, or relevant content

Asking for information

Quick Base takes feedback very seriously, as it ensures that our product is serving the needs of our users. The most valuable type of feedback is feedback that we can gather at the time that a user performs an action relevant to what we are trying to learn. For example, feedback on adding widgets to dashboards is most valuable when a builder is adding one, as opposed to an email survey days or weeks later. This feedback is always optional, and Quick Base will never prevent or impede a user’s ability to get work done in the product.

For more information on Quick Base’s messaging policies, please contact your account team.