Skip to main content
A hub is a focused home base for a team or function (Sales, Support, Success, Marketing, Operations) built from the same underlying objects, views, and dashboards that power the rest of your workspace. Instead of every teammate sifting through every object, each hub surfaces only the records, pipelines, inboxes, and reports that role works with day to day.

​
Why organize into hubs

  • Less noise: a sales rep opens to their deals and inbox, not the support queue.
  • One set of records: hubs are different views over the same data, so a contact a marketer captures is the same contact a rep closes.
  • Faster onboarding: a new hire on a team starts in a workspace already shaped around their job.

​
What a hub is made of

A well-built hub usually combines:

​
Setting up your hubs

1

Decide your teams

List the functions that work in Custral: Sales, Support, Success, and so on. Each becomes a hub.
2

Model the shared data

Create the objects every team needs (Contacts, Accounts) once, and add team-specific objects (Deals, Tickets) alongside them.
3

Build role-specific views

For each hub, save the views and dashboards that team relies on, filtered to what they own.
4

Add automations

Layer in workflows and sequences so routine work happens without anyone touching it.
Start with one hub for your busiest team, get it right, then clone the pattern for the others. The use-case guides below are good templates.

Use cases by team

See how Sales, Support, Success, Marketing, and Product set up Custral.

Objects & records

Model the data your hubs are built on.

Views & dashboards

Build the saved views each hub opens to.

Automations

Route, notify, and follow up automatically.