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

# How your app is configured

> Fields, pages, dropdown choices, and rules are configured per company — what that means for what you see on screen.

AI Insurance is not a one-size-fits-all product. The platform provides the
machinery — records, lists, workflows, forms, financials — and each company's
app is **configured** on top of it for that company's specific insurance
program. Two companies can run on the same platform and see very different
screens.

## What's configured per company

| Configured            | What it controls                                                                                                                                                                                                                                          |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Fields**            | Which fields exist on each record type (submission, quote, policy, event, exposure, person, organization), their names, and their types — text, number, currency, date, yes/no, dropdown, address, links to other records, and structured nested objects. |
| **Pages & cards**     | How those fields are laid out — which cards appear on each detail page and wizard step, what they're called, and the order fields appear in.                                                                                                              |
| **Option sets**       | The choices behind every dropdown — coverage types, statuses, classifications, and any other pick-list your program uses.                                                                                                                                 |
| **Rules**             | Behavior on top of the fields: when a field is shown or hidden, when it's required, values calculated automatically from other fields, and values set automatically by the platform.                                                                      |
| **Rating**            | How premiums are computed from your rating information during quoting.                                                                                                                                                                                    |
| **Forms & templates** | The document templates your quotes, policies, and events generate — see [Form templates](/app/admin/form-templates) and [Auto-added forms](/app/admin/auto-added-forms).                                                                                  |
| **Financials**        | Invoice types, line items, approvals, and export settings — see [Invoice types and line items](/financials/invoice-types).                                                                                                                                |

A small core is fixed by the platform — every exposure has a name and a type,
every quote belongs to a submission — but everything beyond that core is
yours. The [Entities documentation](/entities/overview) describes what's
platform-level; your configuration fills in the rest.

## What that means for what you see

* **Your screens won't exactly match these docs.** Screenshots in this
  documentation come from example configurations. The layout patterns — the
  sidebar, the tabbed record workspace, list pages — are the same everywhere,
  but the specific fields, cards, and dropdown choices on them are your
  company's own.
* **Field names are your names.** Where these docs say "a dropdown field" or
  use a generic example, your app shows the fields configured for your program.
* **Behavior can differ too.** A field that's required in your app may not
  exist in another company's; a section that appears when you pick a certain
  coverage type is a configured rule, not a platform constant.
* **Lists follow the fields.** The columns available under
  [Edit Columns](/app/getting-started/navigating#choosing-columns) and the
  fields you can filter by are exactly the fields configured on that record
  type.

Wherever behavior depends on setup, these docs say so — usually as "depending
on how your company is configured."

<Note>
  Configuration is also **per company** in the literal sense: if you work
  across multiple companies and
  [switch between them](/app/getting-started/signing-in#working-across-companies),
  each one has its own fields, pages, and rules. The same record type can look
  quite different after a switch.
</Note>

## What you manage yourself

Configuration in the sense above — fields, pages, option sets, rules, rating —
is managed for you (see below). But day-to-day administration is in your
hands, in the **Administration** area (select your company's name at the
bottom of the sidebar):

* [Users & roles](/app/admin/users-roles) — invite users and assign roles.
* [Company settings & inboxes](/app/admin/company-settings) — profile, logo,
  and email settings.
* [Form templates](/app/admin/form-templates) — upload and edit document
  templates.
* [API keys](/app/admin/api-keys) — create keys for the
  [API](/api-reference/overview).
* [Rating run logs](/app/admin/rating-logs) — inspect rating calculations.

## Changing your configuration

To add a field, change a page layout, adjust dropdown choices, or update a
rule, **contact your AI Insurance team** — configuration changes are made for
you as part of onboarding and ongoing support. When you ask, it helps to
describe:

1. **Where** — the record type and page (for example, "the quote wizard's
   coverages step").
2. **What** — the field, choice, or rule you want added or changed.
3. **When it should apply** — always, or only under certain conditions.

<Tip>
  Technical teams can also read and manage configuration programmatically. The
  [Configuration API](/api-reference/configuration/overview) exports your full
  configuration as structured JSON and applies edited configuration back — it
  requires an [API key](/app/admin/api-keys) with the configuration-manager
  role.
</Tip>