# Composites

> Blocks made of other blocks, installed as one, for SaaS, sales, CRM, finance, support, scheduling, care, filespace and more.

Source: https://bettersupabase.com/docs/blocks/catalog-composites

A composite block installs a set of blocks that belong together and adds helpers that span them. Presets list composites instead of long block arrays, and `add` and `remove` work on a composite by name. How a composite is declared is in [Composite blocks](/docs/extending/composite-blocks).

- [SaaS](/docs/blocks/saas)
- [Sales](/docs/blocks/sales)
- [CRM](/docs/blocks/crm)
- [Commerce](/docs/blocks/commerce)
- [Procurement](/docs/blocks/procurement)
- [Finance](/docs/blocks/finance)
- [Support](/docs/blocks/support)
- [Projects](/docs/blocks/projects)
- [Service](/docs/blocks/service)
- [People](/docs/blocks/people)
- [Recruiting](/docs/blocks/recruiting)
- [Scheduling](/docs/blocks/scheduling)
- [Learning](/docs/blocks/learning)
- [Events](/docs/blocks/events)
- [CMS](/docs/blocks/cms)
- [Care](/docs/blocks/care)
- [Filespace](/docs/blocks/filespace)
- [Collaboration](/docs/blocks/collaboration)
- [Governance](/docs/blocks/governance)

## The names [#the-names]

The Drive-style composite is `filespace`, not `documents`, because `documents` is already the block for collaborative documents. The compliance composite is `governance`, not `compliance`, because `compliance` is already the block for policies and controls. Both keep the parts the plan listed that exist today, which are the drive, versions, share links, search and the bin for `filespace`, and audit, field history and data lifecycle for `governance`.

Each composite lists only the parts it installs. Blocks that are not parts, such as `signatures` or `retention` next to `filespace` and `governance`, stay separate, so add them next to the composite when an app needs them.