Your workspace is the tenant boundary for everything in Limnn. Every module reads and writes to one shared graph, so a contact, employee, deal or ticket is a single record wherever it appears. Configuring the workspace deliberately on day one prevents rework across every team later.
The shared graph
Modules are views over the same underlying objects and relations rather than separate databases. A Sales contact who becomes a Support requester, or a person who becomes an HR employee, is linked rather than copied. Permissions, field-level access, audit and Cortex all resolve against that one graph, which is why a rule set once is honored everywhere.
First-day setup
- 1Sign up at app.limnn.com and confirm your email. The first person to join becomes the workspace owner and is assigned the Super Admin system role.
- 2Open Settings and go to /settings/general. Set workspace name, time zone, default currency and locale; these flow into quotes, payroll, reports and invoices.
- 3Open /settings/branding to upload your logo and colors, used on invites, portals and PDFs.
- 4Open /settings/module-access and enable only the modules your teams need (Sales, Support, People, Grid, Workspace, Gate and so on). Disabled modules disappear from navigation but keep their data.
- 5Open /settings/localization if you operate in more than one region (date formats, currencies, languages).
- 6Invite your team at /settings/users and assign roles (see Invite your team and Roles & access).
- 7Review /settings/security (session timeout, two-factor, SSO and IP allow-list) and /settings/audit so you know where sign-in policy and the audit trail live before you have real data.
Settings is grouped into Your preferences, Account, Data, Tools (one block per module, such as Sales, Support and Flows) and Developer. Use the search box at the top of Settings to jump to any page by name or keyword.
Routes you will use most
- /settings/general - workspace identity, time zone, currency
- /settings/module-access - turn modules on or off
- /settings/users and /settings/teams - people and team structure
- /settings/roles - role and permission definitions
- /settings/fields and /settings/field-access - custom fields and field-level security
- /settings/integrations - connections to other tools
- /settings/developer - API keys, request logs, webhooks and the MCP server
- /settings/billing, /settings/plan and /settings/credits - seats, plan and Cortex credits
One person, one workspace
Each person belongs to a single workspace. Removing a user deactivates the account rather than deleting it, because ownership, history and audit records reference the user and must remain intact. Reactivate the person later and everything reattaches.