Administering Limnn is mostly about shaping the workspace to how your business works. Cortex Builder speeds that up by turning a plain-language description into real configuration objects, while the rest of /settings holds the levers you maintain over time.
Cortex Builder
Cortex Builder at /settings/cortex-builder generates real graph objects, not mockups: fields, pick lists, pipelines, layouts and automations that appear in the relevant settings pages once accepted.
- 1Open /settings/cortex-builder.
- 2Describe what you need, for example: a customer onboarding pipeline with four stages, a required kickoff date field and a task on entering Live.
- 3Press Execute. Cortex proposes the objects it will create.
- 4Review each proposed object; deselect anything you do not want.
- 5Apply. The objects are created and listed with links to their settings pages for fine tuning.
Try large builds in /settings/sandbox first. Builder is on demand only and consumes Cortex credits.
Administration map
- People - /settings/users, /settings/teams, /settings/roles, /settings/module-access.
- Data model - /settings/fields, /settings/pick-lists, /settings/layouts, /settings/pipelines, /settings/custom-engines.
- Process - /settings/approvals, /flows and /settings/automations (Simple rules), /settings/cadences, /settings/sales-routing.
- Data - /settings/import, /settings/data-management, /settings/retention.
- Security - /settings/security, /settings/field-access, /settings/audit.
- Developer - /settings/developer (API keys, logs, webhooks, MCP).
- Money - /settings/plan, /settings/billing, /settings/credits.
Approval chains
At /settings/approvals configure multi-step approval chains for items such as expenses, leave and requisitions. Chains route to a named approver or the requester's manager and record each decision.
Recurring admin checklist
- 1Monthly: review /settings/users for leavers and unused seats.
- 2Monthly: review API keys (Settings > Developer) and integrations for stale or expiring entries.
- 3Quarterly: review roles and field access against current job functions.
- 4Quarterly: review credit budgets and ledger trends.
- 5After any org change: update teams so manager scope stays correct.
Changes to settings are recorded at /settings/audit. If something changed unexpectedly, start there.