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

# Overview

> How Quivly organizes your customer data

## Overview

Objects are structured containers that hold different types of data in Quivly. When you connect integrations (Salesforce, HubSpot, Stripe, etc.), data is mapped to objects to create a unified customer view.

***

## Object Types

| Type               | Description                                                                         |
| ------------------ | ----------------------------------------------------------------------------------- |
| **Core Objects**   | Pre-built objects (Customers, Contacts, Opportunities, etc.) that cannot be deleted |
| **Custom Objects** | Objects you create to track business-specific data                                  |

***

## Core Objects

Quivly includes these core objects:

* **Customers** - Your customer accounts/companies
* **Contacts** - People within customer organizations
* **Opportunities** - Deals, renewals, expansions from your CRM
* **Subscriptions** - Recurring revenue from billing systems
* **Invoices** - Billing transactions and payments
* **Contracts** - MSAs, order forms, and renewals from your CRM
* **Support Tickets** - Customer support requests
* **Call Recordings** - Meeting transcripts from call recording tools
* **Market Signals** - External company intelligence (funding, hiring, etc.)
* **Product Usage** - Customer activity metrics from your data warehouse or the Push API
* **External Users** - People from your connected systems (CRM owners, support agents) used for ownership references

***

## Object Relationships

All objects relate to Customers:

```
Customer
├── Contacts
├── Opportunities
├── Contracts
├── Subscriptions
├── Invoices
├── Support Tickets
├── Call Recordings
└── Product Usage
```

***

## Managing Objects

Navigate to **Settings** → **Objects** to:

* View all core and custom objects
* See field definitions for each object
* Add custom fields to any object
* Configure integration field mappings