Companies that sell into the restaurant industry can use Restaurantology and Salesforce together to automate how they consume industry data with speed, predictability, and precision.

[!TIP]
Salesforce CRM integration is an additional Data-as-a-Service (DaaS) offering from Restaurantology. Learn more about DaaS here.

There are two types of Restaurantology users in Salesforce.

[01] End users: Viewing Restaurantology insights on Account records

End users may include sales (AEs, SDRs/BDRs, managers), marketing, post-sales (CSMs, support), ops, and executive roles. Their primary use is to view Restaurantology insights within Salesforce through:

• Custom fields
• A custom sub-tab
• A side Visualforce widget
• Visual reporting elements
• Related records (e.g., RestaurantologyLogs)

Admins can customize where these insights appear to optimize visibility and reduce friction.

[!IMPORTANT]
Restaurantology’s monthly data pushes do not overwrite Salesforce Account fields (e.g., Location Counts or Service Type) by default. Admins can configure workflows to apply updates as needed.

Chrome extension behavior in Salesforce: When the sidebar is opened, Restaurantology’s Chrome extension can scan Salesforce pages and automatically perform searches. Learn how it works with standard and custom objects.

[02] Admins: Configuring Restaurantology via the App Center

Admins—often in SalesOps, RevOps, BizApps, or data roles—are responsible for setup, mapping, and ongoing maintenance. Through the App Center, they can:

• Map Restaurantology records to existing Accounts using candidate match logic
• Mass-create Accounts where no matches exist
• Review newly created records and resolve accordingly
• Restore previously discarded or hidden records
• Monitor background processes and queued workloads
• Access setup and admin tools during implementation and ongoing updates

In smaller teams, a single user may serve both admin and end-user functions.