Data Structure

The database structure for the template

All objects and some selected fields in the template are explained below. Please refer to our Bubble Best Practices document for guidance on how the Bubble database should be structured.

All data types and a few select fields are explained below. A good general rule to follow is that you shouldn't delete any fields that are included with the template and instead only add new ones.

Account

This data type represents an account that users can add, view, and modify on the platform. An Account can be added by an Admin, Manager, or Rep. Admins and Managers can view all Accounts on the platform. Reps can only view Accounts which have been assigned to them (e.i., their user account is the Owner field for that Account).

Field name	Type	Description
Owner	User	The owner assigned to this account. This is used for display purposes and list filtering on the portal page. It is also used to determine which accounts can be viewed by a Rep
Saved?	yes / no	Indicates whether or not this account has completed the creation process. Only accounts with Saved? set to yes should be shown throughout the app. This field is set to yes when a user clicks to save changes for this account (but will remain empty if the user never completes the process)
Title	text	The title and primary identifier for the account
Website URL	text	The website URL added for this account

Block entry

This data type is used to store content that goes into each homepage block. Each homepage block (template) will have a maximum number of block entries:

• Testimonials section: Multiple entries

• Featured section: Up to 3 entries

• Process section: Up to 3 entries

• Slideshow section: Between 3 to 5 entries

• Capabilities section: Up to 9 entries

• Video section: 1 entry

• Press section: Between 3 to 5 entries

• About section: 1 entry

• Call-to-action section: 1 entry

• Contact section: 0 entries

Contact

This data type represents a contact that users can add, view, and modify on the platform. A Contact can be added by an Admin, Manager, or Rep. Admins and Managers can view all Contacts on the platform. Reps can only view Contacts which have been assigned to them (e.i., their user account is the Owner field for that Contact).

Field name	Type	Description
Account	Account	The Account associated with this contact. This field is optional. It used for display and reference purposes
Account name	text	This is equivalent to the Title field of this contact's Account. This is used only for the download contacts functionality on the portal page
Email	text	The email for this contact
First last	text	This is equivalent to the First name + Last name for this contact. This is used in situations where you need to refer to both fields but Bubble only allows you to select a single field in the editor
First name	text	The first name for this contact. This, coupled with the Last name field, is the primary identifier for contacts
Last name	text	The last name for this contact. This, coupled with the First name field, is the primary identifier for contacts
Owner	User	The owner assigned to this contact. This is used for display purposes and list filtering on the portal page. It is also used to determine which contacts can be viewed by a Rep
Phone	text	The phone for this contact. The input which populates this field forces formatting for a US phone
Saved?	yes / no	Indicates whether or not this contact has completed the creation process. Only contacts with Saved? set to yes should be shown throughout the app. This field is set to yes when a user clicks to save changes for this contact (but will remain empty if the user never completes the process)
Title	text	The title for the contact

Dummy

This data type allows you to quickly preview your page layout by it as your data source.

Deal

This data type represents a deal that users can add, view, and modify on the platform. A Deal can be added by an Admin, Manager, or Rep. Admins and Managers can view all Deals on the platform. Reps can only view Deals which have been assigned to them (e.i., their user account is the Owner field for that Deal).

Field name	Type	Description
Account	Account	The Account associated with this deal. It used for display and reference purposes
Account name	text	This is equivalent to the Title field for this deal's Account. This is used only for the download deals functionality on the portal page
Close date	date	This field represents the date that this deal was initially assigned a Stage with a Likelihood of 100%. This field is auto-populated and may be empty. It is used for display and reference purposes
Deal value	number	The numeric value (in US dollars) of this deal
Expected value	number	The numeric expected value (in US dollars) of this deal. This is calculated by multiplying the Deal value by this deal's Stage's Likelihood
Lost date	date	This field represents the date that this deal was initially assigned a Stage with a Likelihood of 0%. This field is auto-populated and may be empty. It is used for display and reference purposes
Owner	User	The owner assigned to this deal. This is used for display purposes and list filtering on the portal page. It is also used to determine which deals can be viewed by a Rep
Primary contact	Contact	The Contact associated with this deal. This field is optional. It is used for display and reference purposes
Primary contact name	text	This is equivalent to the First name + Last name fields of this deal's Primary contact. This is used only for the download deals functionality on the portal page
Saved?	yes / no	Indicates whether or not this deal has completed the creation process. Only deals with Saved? set to yes should be shown throughout the app. This field is set to yes when a user clicks to save changes for this deal (but will remain empty if the user never completes the process)
Stage	Stage	The Stage associated with this deal. This field is used when calculating the deal's Expected value and for populating the active deal value chart on the portal page
Stage name	text	This is equivalent to the Name of this deal's Stage. This is used only for the download deals functionality on the portal page
Title	text	The title and primary identifier for this deal

Feature backlog

This data type represents each feature that an Owner has added into the Backlog section of the Owner's Portal.

Homepage block template

The data type is used for the homepage maker. App owners can add any number of homepage blocks / homepage sections straight from the owner's portal by starting from a homepage block template.

Homepage block

App Owners can add an unlimited number of homepage blocks. They can control the content and settings from the Owner's Portal.

Note

This data type represents a note - or comment - that can be added to a Deal, Contact, or Account. All Notes should have either the Deal, Contact, or Account field populated (and will always be linked to/associated with exactly one of those objects). A Note may contain text or a file attachment (and will always have one or the other).

Field name	Type	Description
Account	Account	The Account this note was created for. This may be empty
Attachment	file	The file attachment for this note
Contact	Contact	The Contact this note was created for. This may be empty
Deal	Deal	The Deal this note was created for. This may be empty
Text	text	The text content for this note

Palette color

This data type is color palette list is referenced in the Air Color Picker plugin / element. Feel free to add more color entries for quick access when using the Air Color Picker element.

Push token

This represents a unique token to be used with OneSignal for push notification integrations for wrapped mobile apps.

Role

The role and permissions level assigned to a user account. Each User should have exactly one Role. A User's Role determines which Deals, Contacts, and Accounts they can view and interact with on the portal page. The three types of Roles are Admin, Manager, and Rep.

Field name	Type	Description
Can select owner?	yes / no	Indicates whether the user can select an Owner (besides themselves) for a Deal, Contact, or Account. If this is set to no, then the user will auto-assign the Owner fields to their account
Can view all?	yes / no	Indicates whether the user can view all Deals, Contacts, or Accounts or only those which have been assigned to them
Type	text	The label for this role. This value should be either Admin, Manager, or Rep

Stage

This data type represents a Stage that a Deal can be in. Stages are used to populate the active deal value chart on the portal page and the Likelihood field is used when calculating a Deal's Expected value. Stages are created and managed from the owner's portal.

Field name	Type	Description
Likelihood	number	The numeric value which represents the likelihood of closing a Deal in this stage. When selecting and displaying Likelihoods throughout the app, the percentage formatter is used
Name	text	The name and primary identifier for this stage
Order	number	The order that this stage will appear in lists

User

The user data type represents each person who has an account in your application.

Field name	Type	Description
Date agreed to terms and privacy docs	date	Date agreed to terms and privacy docs during sign up
Inactive	yes / no	User is marked as inactive = yes when App owner deletes the user from the Owner's Portal
Last login	date	Captures the last date that the user loaded any page in the app
Owner?	yes / no	If Owner is yes then they will have access to the Owner's Portal
Signup method	text	E.g., E-mail, LinkedIn, Facebook, Twitter, or etc.

Website

This data type includes fields for all app-wide settings. Most of the data fields are controlled by the App Owner from the Owner's portal. There should only be a single object of this data type.

Field name	Type	Description
Ask for cookies?	yes / no	App Owner can control whether or not to ask users to accept cookies (if yes, a cookies banner will show on the homepage)
Email	text	Contact / support email that all emails in the application come from. Whenever a new email action is created in the application, it should refer to this field instead of being hardcoded
Email HTML	text	Used in the SendGrid API call for "send emails" that generates a nicely-formatted HTML email
List of blocks	List of homepage blocks	Homepage blocks / sections
Name	text	Name of your app / website. This is the field that should be referenced anywhere where the name is used (instead of hardcoded).
Primary color	text	App and email template primary color
Usersnap off?	yes / no	This turns off the Usersnap tool, which AirDev uses with its clients to submit feedback and bug reports.