The company record, its feature toggles, base currency, logos, and tags — the company-wide configuration every module reads from.
Everything in Carbon is scoped to a company, and two records hold its configuration: the company row (identity, address, currency, logos) and a paired companySettings row holding the company-wide feature flags and defaults. Settings live under Settings in the app, grouped into Company, Modules, and System. Every route is employee-only; Billing additionally needs company ownership on a Cloud environment, and Companies and Backups are internal-only.
The tenant's identity — one record every document and posting reads from.
FieldType
Company name.
The registered address. addressLine1, city, postalCode, and countryCode are required.
The currency every posted amount is expressed in. See base currency.
Contact details.
Tax registration identifiers printed on documents.
The five logo slots, edited under Settings → Logos: light/dark pairs for UI backgrounds, compact icon variants, and a watermark printed behind documents.
Set when this company is a subsidiary of another.
Marks a consolidation-only company that nets intercompany pairs out of consolidated reports.
Groups related companies for the company switcher.
Which modules this company turned on during onboarding.
The industry chosen at onboarding.
Whether change history is recorded. See audit log.
Company membership is per-user: one login can hold several companies and switch through the company picker, and each company carries its own settings, currency, and numbering. Nothing crosses the boundary. A company with a parentCompanyId is a subsidiary; consolidation and elimination are covered in intercompany accounting.
companySettings is a single row per company, edited across the Settings → Modules pages. These are the real column names:
FieldType
Master switch for the ledger. When off, operations complete without posting journal entries.
Turns on shop-floor time cards.
Enables the support/impersonation console.
Everyone needs an authenticator app to open this company. Edited from Settings → System → Security; locked on in controlled (ITAR) deployments. See two-factor authentication.
Whether material units default to metric.
Whether new materials get an auto-generated readable id.
The release-control policy for item revisions.
What a Kanban card prints: label, qrcode, or url.
Default label sizes.
Whether receiving recalculates supplier lead times.
When purchase prices refresh: Purchase Invoice Post or Purchase Order Finalize.
Whether preventive maintenance is generated ahead of time, and by how many days (1–90).
The default inspection sampling standard.
Requires a second person to sign off inspections.
The quality issue target used in reporting.
Whether a separate tax-depreciation schedule is tracked for fixed assets, and its rate.
Whether customer/supplier readable ids are surfaced in the UI.
Every shelf-life knob in one blob. See shelf life.
Whether customers get a digital quote, and whether it includes purchase orders.
Per-category default markups applied to quote lines.
The same row also carries the notification groups (who to notify for digital quotes, RFQ-ready, supplier quotes, job completions, dispatches, gauge-calibration expiry), the AP/AR email addresses, and default CC lists — see notifications for how they fan out.
HEADS UP
Accounting is a company-wide toggle, not per-document
accountingEnabled gates the entire ledger: off means jobs, shipments, and invoices complete but nothing posts, with no per-transaction exceptions. Turning it on mid-stream doesn't backfill past activity.
Every company has one baseCurrencyCode: the currency all posted amounts are stored and reported in, with foreign-currency transactions converted at their exchange rate before posting. It's chosen at onboarding and is the denomination of your whole history, so it isn't something you flip casually. A subsidiary can carry a different base currency from its parent; consolidation is where they meet.
Carbon ships eight color themes (Modern, Brutal, Cherry, Apricot, Lemon, Mint, Blueberry, Lavender). Theme is per-person, stored in a browser cookie rather than on the company record, so two people in one company can run different themes; document templates have their own separate theme setting. Tags are free-form labels scoped to a company and a table, so the same label can mean different things on items versus jobs, and vocabularies never leak across companies.
