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

# Company settings

> The company record, its feature toggles, base currency, logos, and tags — the company-wide configuration every module reads from.

Alforse scopes data and configuration to a **company**. The `company` record stores identity, address, currency, and logos. Its paired `companySettings` record stores feature flags and defaults. The app groups settings under **Company**, **Modules**, and **System**. Settings routes require employee access. **Billing** also requires company ownership; **Companies** is internal-only, and **Backups** needs the Business plan.

## The company record

Edited under **Settings → Company**:

Alforse screenshot**Settings → Company: the company form with name, registered address, tax identifiers, and base currency**

The tenant's identity — one record every document and posting reads from.

FieldType

<details>
  <summary>**name**required</summary>

  Company name.
</details>

<details>
  <summary>**addressLine1 / addressLine2 / city / stateProvince / postalCode / countryCode**required</summary>

  The registered address. `addressLine1`, `city`, `postalCode`, and `countryCode` are required.
</details>

<details>
  <summary>**baseCurrencyCode**required`text`</summary>

  The currency every posted amount is expressed in. See [base currency](#base-currency).
</details>

<details>
  <summary>**phone / fax / email / website**</summary>

  Contact details.
</details>

<details>
  <summary>**taxId / vatNumber / eori**</summary>

  Tax registration identifiers printed on documents.
</details>

<details>
  <summary>**logoLight / logoDark / logoLightIcon / logoDarkIcon / logoWatermark**`text`</summary>

  The five logo slots, edited under **Settings → Logos**: light/dark pairs for UI backgrounds, compact icon variants, and a watermark printed behind documents.
</details>

<details>
  <summary>**parentCompanyId**`text`</summary>

  Set when this company is a subsidiary of another.
</details>

<details>
  <summary>**isEliminationEntity**`boolean`</summary>

  Marks a consolidation-only company that nets intercompany pairs out of consolidated reports.
</details>

<details>
  <summary>**companyGroupId**`text`</summary>

  Groups related companies for the company switcher.
</details>

<details>
  <summary>**selectedModules**`text[]`</summary>

  Which modules this company turned on during onboarding.
</details>

<details>
  <summary>**industryId / customIndustryDescription**`text`</summary>

  The industry chosen at onboarding.
</details>

<details>
  <summary>**auditLogEnabled**`boolean`</summary>

  Whether change history is recorded. See [audit log](/docs/reference/audit-log.md).
</details>

A user can belong to multiple companies and switch between them with the company picker. Each company has independent settings, currency, and numbering. A company with a `parentCompanyId` is a subsidiary; see [intercompany accounting](/docs/reference/intercompany.md) for consolidation and elimination.

## Feature toggles and defaults

`companySettings` is a single row per company, edited across the **Settings → Modules** pages. These are the real column names:

FieldType

<details>
  <summary>**accountingEnabled**`boolean`</summary>

  The General Ledger switch under **Settings → Accounting** (shown with an Alpha badge): when on, transactions create journal entries and update the general ledger. The switch is editable by Alforse internal staff only. See [accounting](/docs/reference/accounting.md).
</details>

<details>
  <summary>**timeCardEnabled**`boolean`</summary>

  Turns on shop-floor time cards.
</details>

<details>
  <summary>**consoleEnabled**`boolean`</summary>

  Enables MES console (shared-station) mode, where operators pin in with a 4-digit PIN. Business plan; toggled from **Settings → People** by someone with permission to update settings. See [console mode](/docs/reference/mes.md#console-shared-station-mode).
</details>

<details>
  <summary>**requireMfa**`boolean`</summary>

  Everyone needs an authenticator app to open this company. Edited from **Settings → System → Security**; shown as on and locked in a controlled environment. See [two-factor authentication](/docs/reference/two-factor.md).
</details>

<details>
  <summary>**useMetric**`boolean`</summary>

  Whether material units default to metric.
</details>

<details>
  <summary>**materialGeneratedIds**`boolean`</summary>

  Whether new materials get an auto-generated readable id.
</details>

<details>
  <summary>**plmReleaseControl**`text`</summary>

  The release-control policy for item revisions.
</details>

<details>
  <summary>**kanbanOutput**`enum`</summary>

  What a Kanban card prints: `label`, `qrcode`, or `url`.
</details>

<details>
  <summary>**productLabelSize / shelfLabelSize**`text`</summary>

  Default label sizes.
</details>

<details>
  <summary>**mrpRunTime**`time`</summary>

  The time of day scheduled MRP runs, on the company's time zone. Empty keeps the default, every 3 hours. Edited from **Settings → Planning**. See [planning](/docs/reference/planning.md#when-it-runs).
</details>

<details>
  <summary>**defaultPlanningHorizonDays**`number`</summary>

  How many days ahead the planning grids show actions and suggested orders, unless an item sets its own. Empty or 0 shows everything. Edited from **Settings → Planning**. See [planning horizon](/docs/reference/planning.md#planning-horizon).
</details>

<details>
  <summary>**rescheduleToleranceDays**`number`</summary>

  How many days an open order may land from the date it is needed before MRP suggests an Expedite or Defer. Default 7. Edited from **Settings → Planning**. See [reschedule tolerance](/docs/reference/planning.md#reschedule-tolerance).
</details>

<details>
  <summary>**defaultResponsibleEmployee**`text`</summary>

  The person a planning action is assigned to when no item, item group or location names one. Edited from **Settings → Planning**. See [planning ownership](/docs/reference/planning.md#planning-ownership).
</details>

<details>
  <summary>**forecastConsumptionBackwardPeriods / forecastConsumptionForwardPeriods**`number`</summary>

  How many weeks before and after its own week a real order reaches to consume forecast (defaults 4 and 1). Edited from **Settings → Planning**. See [forecast consumption](/docs/reference/forecast.md).
</details>

<details>
  <summary>**updateLeadTimesOnReceipt**`boolean`</summary>

  Whether receiving recalculates supplier lead times.
</details>

<details>
  <summary>**purchasePriceUpdateTiming**`enum`</summary>

  When purchase prices refresh: `Purchase Invoice Post` or `Purchase Order Finalize`.
</details>

<details>
  <summary>**samplingStandard**`enum`</summary>

  The default inspection sampling standard.
</details>

<details>
  <summary>**enforceInspectionFourEyes**`boolean`</summary>

  Requires a second person to sign off inspections.
</details>

<details>
  <summary>**qualityIssueTarget**`number`</summary>

  The quality issue target used in reporting.
</details>

<details>
  <summary>**assetTaxDepreciationEnabled / assetTaxRate**`boolean / number`</summary>

  Whether a separate tax-depreciation schedule is tracked for fixed assets, and its rate.
</details>

<details>
  <summary>**showCustomerReadableId / showSupplierReadableId**`boolean`</summary>

  Whether customer/supplier readable ids are surfaced in the UI.
</details>

<details>
  <summary>**inventoryShelfLife**`jsonb`</summary>

  Every shelf-life knob in one blob. See [shelf life](/docs/reference/shelf-life.md).
</details>

<details>
  <summary>**digitalQuoteEnabled / digitalQuoteIncludesPurchaseOrders**`boolean`</summary>

  Whether customers get a digital quote, and whether it includes purchase orders.
</details>

<details>
  <summary>**quoteLineCategoryMarkups**`jsonb`</summary>

  Per-category default markups applied to quote lines.
</details>

The row also stores **notification groups**, AP and AR email addresses, and default CC lists. See [notifications](/docs/reference/notifications.md) for delivery behavior.

## Base currency

Each company has one `baseCurrencyCode`. Alforse converts foreign-currency transactions at their exchange rate and stores posted amounts in the base currency. The value is chosen during onboarding and denominates the company's posting history. A subsidiary can use a different base currency from its parent; consolidation handles the conversion.

## Theme and tags

Alforse includes four color themes: alforse light (the default), Modern, Brutal, and Blueberry. Theme selection is **per user** and stored in a browser cookie. Document templates have a separate theme setting. **Tags** are free-form labels scoped by company and table, so item and job tags have independent vocabularies.

## Related system configuration

**Numbering sequences**

The per-company generators behind every readable document number.

[Open](/docs/reference/sequences.md)

**API keys**

Scoped secrets that let external systems call the Alforse API.

[Open](/docs/building/api-keys.md)

**Approvals**

Approval rules that gate documents above a threshold.

[Open](/docs/reference/approvals.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.