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

# Clients Overview

> Organization and client hierarchy management

## Client Hierarchy Structure

From the Claude.MD context, we know Ipster is designed to support multi-level client structures for future reseller access. This section will document how organizations are structured and managed.

## TODO: Organization Data Model

<Note>
  **Team Input Needed**: We need to document the actual client/organization structure in our database
</Note>

**Questions for the team:**

1. What's the exact hierarchy? (Ipster → Client → Subcompany → Location?)
2. What fields does each level have? (name, billing\_info, settings, etc.)
3. How do we handle billing relationships between levels?
4. What permissions flow down the hierarchy?

Example structure we need to document:

```javascript theme={null}
// TODO: Replace with actual schema
{
  id: "string",
  name: "string",
  type: "client" | "subcompany" | "location", // TODO: Confirm types
  parent_id: "string | null",
  // TODO: Add all actual fields
}
```

## TODO: Client Types and Permissions

**Questions for the team:**

1. What are the different client types? (Billing client, reseller, end customer?)
2. What can each client type access?
3. How do we handle data isolation between clients?
4. Do clients have different feature flags or limits?

## TODO: Multi-Tenant Architecture

**Questions for the team:**

1. How do we ensure data isolation between clients?
2. How are agents assigned to clients/organizations?
3. Can clients share agents or are they always isolated?
4. How do we handle client-specific branding/customization?

## TODO: Available Endpoints

Once we confirm what endpoints exist, we'll document:

* `GET /v1/clients` - List client organizations
* `POST /v1/clients` - Create new client
* `GET /v1/clients/{id}` - Get client details
* `PUT /v1/clients/{id}` - Update client
* `GET /v1/clients/{id}/subcompanies` - List subcompanies (if applicable)
* `POST /v1/clients/{id}/subcompanies` - Create subcompany (if applicable)

## TODO: Client Onboarding Flow

**Questions for the team:**

1. What's the process for onboarding a new client?
2. What default settings/agents do new clients get?
3. How do we handle initial billing setup?
4. What's the approval process for new clients?

## TODO: Future Reseller Support

**Questions for the team:**

1. What's the long-term vision for partner/reseller access?
2. What additional API permissions will resellers need?
3. How will white-labeling work?
4. What reporting/analytics will resellers have access to?