1In one sentence#

The Settings module is LumosCRM's workspace control panel — where administrators tailor the CRM to their agency: company details, the editable dropdown lists that appear throughout every module, the team's user accounts, the tax-rate catalogue behind invoicing, and document categories — with a link through to Access Control (roles & permissions).

It's how a generic CRM becomes your CRM, without touching code.

2Who it's for#

Role	What they get
Workspace administrators	One place to configure company info, lists, taxes, and categories.
Team leads	Manage user accounts for the people who operate the CRM.
Anyone	The benefit indirectly — the tailored dropdowns and labels they see every day come from here.

3The core idea: configure, don't customise#

A lot of what makes a CRM feel "right" for a business is the vocabulary and lists it uses — client tiers, request categories, vendor types, payment terms. LumosCRM exposes these as editable option-sets, so an administrator can rename, add, reorder, or retire the choices that appear across the product — no developer needed.

   Settings
   ├── General      → company information · localization
   ├── People       → client option-sets · user accounts   (Roles → Access Control)
   └── Workspace     → option-sets for Requests · Vendors · Documents · Events · Finance
                       + tax-rate catalogue · document categories

4Capabilities at a glance#

Area	What an admin can do
Company information	Set the agency's core company details.
Localization	Configure localization preferences.
Editable option-sets	Add / edit / reorder / retire the dropdown choices used across every module.
User accounts	Create and edit the CRM operator accounts (the people who log in).
Tax-rate catalogue	Maintain the tax rates that feed invoice line-item tax.
Document categories	Maintain the categories used to organise the Document Vault.
Roles & permissions	Jump to Access Control (the RBAC module) to manage who can do what.

5The areas#

General#

Company information — the agency's identity details.
Localization — regional/format preferences.

People#

Clients — the client-related option-sets (e.g. tiers, statuses, preference categories).
Users — the user accounts for staff who operate the CRM: create new operators and edit existing ones. (Roles are assigned via Access Control.)

Workspace modules#

Dedicated option-set editors for Requests, Vendors, Documents, Events, and Finance — this is where the statuses, categories, priorities, channels, types, and terms that each module offers in its dropdowns are managed. Finance additionally hosts the tax-rate catalogue that the Invoice module draws on for per-line tax.

Document categories#

The categories behind the Document Vault's category field are maintained here (create / edit / remove).

6Editable option-sets — the configuration backbone#

Most module dropdowns are database-backed option-sets rather than hard-coded lists. An administrator can:

Add a new choice (e.g. a new vendor type or request category),
Edit a label,
Reorder how choices appear,
Retire a choice that's no longer used.

Changes flow straight through to the create/edit forms and filters across the relevant module. (A few lists that are tied to business logic — for example KYC and compliance statuses, or document classification levels — are deliberately fixed and not editable, to protect the rules that depend on them.)

7Security & access control#

Granular permissions: settings.general.view / settings.general.update for company info and localization; settings.options.view / create / update / delete for option-sets and tax rates; users.record.* for user accounts; document categories use the Document module's documents.record.* permissions.
Safe landing: the Settings home is reachable by anyone with any settings surface, so the nav entry never dead-ends in a permission error.
Roles live in Access Control: the "Roles" entry links to the RBAC module's Access Control screen.

8Use cases & scenarios#

Use case A — Tailoring the vocabulary#

A new agency wants its client tiers named "Bronze / Silver / Gold / Black" instead of the defaults. An admin opens Settings → People → Clients, edits the tier option-set, and the new labels appear everywhere clients are created or filtered.

Use case B — Adding a tax rate#

Finance needs a new 5.5% reduced VAT rate. An admin adds it to the Finance tax-rate catalogue; it's immediately selectable on invoice lines.

Use case C — Onboarding a new operator#

A new concierge joins. An admin creates their user account in Settings → People → Users, then assigns their role in Access Control.

9Permissions reference (simplified)#

Area	View	Create	Update	Delete
General (company / localization)	`settings.general.view`	—	`settings.general.update`	—
Option-sets & tax rates	`settings.options.view`	`settings.options.create`	`settings.options.update`	`settings.options.delete`
User accounts	`users.record.view`	`users.record.create`	`users.record.update`	—
Document categories	`documents.record.view`	`documents.record.create`	`documents.record.update`	`documents.record.delete`

10Glossary#

Term	Meaning
Option-set	An editable dropdown list (tiers, categories, statuses…) used across a module.
Tax-rate catalogue	The managed list of tax rates feeding invoice tax.
User account	A login for a staff member who operates the CRM.
Document category	A label organising files in the Document Vault.
Access Control	The RBAC screen where roles and permissions are managed.

This document describes the Settings module as currently built. Company information and localization can be configured; option-sets, user accounts, tax rates, and document categories have full management. Business-logic-bound lists (e.g. compliance statuses, classification levels) are intentionally fixed. Roles and permissions are managed in the RBAC / Access Control module.