> ## Documentation Index
> Fetch the complete documentation index at: https://docs.custral.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Hubs

> Organize your workspace into role-based hubs so each team lands on the data and tools they need.

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:

| Building block  | Example                                                         |
| --------------- | --------------------------------------------------------------- |
| **Objects**     | Deals, Contacts, Accounts, Tickets, Feedback.                   |
| **Saved views** | A board of open deals by stage; an inbox filtered to your team. |
| **Dashboards**  | Pipeline velocity, response times, renewal forecasts.           |
| **Automations** | Routing rules, notifications, and sequences scoped to the team. |

## Setting up your hubs

<Steps>
  <Step title="Decide your teams">
    List the functions that work in Custral: Sales, Support, Success, and so on. Each becomes a hub.
  </Step>

  <Step title="Model the shared data">
    Create the [objects](/data/objects/overview) every team needs (Contacts, Accounts) once, and add team-specific objects (Deals, Tickets) alongside them.
  </Step>

  <Step title="Build role-specific views">
    For each hub, save the [views](/surfaces/views/overview) and dashboards that team relies on, filtered to what they own.
  </Step>

  <Step title="Add automations">
    Layer in [workflows](/automation/workflows/overview) and [sequences](/automation/sequences/overview) so routine work happens without anyone touching it.
  </Step>
</Steps>

<Tip>
  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.
</Tip>

## Related

<CardGroup cols={2}>
  <Card title="Use cases by team" icon="compass" href="/start/use/overview">
    See how Sales, Support, Success, Marketing, and Product set up Custral.
  </Card>

  <Card title="Objects & records" icon="cube" href="/data/objects/overview">
    Model the data your hubs are built on.
  </Card>

  <Card title="Views & dashboards" icon="table" href="/surfaces/views/overview">
    Build the saved views each hub opens to.
  </Card>

  <Card title="Automations" icon="bolt" href="/automation/overview">
    Route, notify, and follow up automatically.
  </Card>
</CardGroup>


## Related topics

- [HubSpot](/integrations/hubspot.md)
- [GitHub](/integrations/github.md)
- [Change Log](/product/updates.md)
- [Object Mapping](/data/properties/complex/object-mapping.md)
- [Integrations](/integrations/overview.md)