Appearance
Data isolation
Every organization that uses Liddr gets its own fully isolated workspace. Your knowledge, your connector credentials, and your configuration live in a dedicated data store that belongs only to your organization — they are never mixed with another organization's data.
This page explains where the isolation boundary sits, what falls inside it, and what happens to your data when a workspace is decommissioned.
A separate workspace per organization
The isolation boundary in Liddr is the organization. Each organization's workspace is backed by its own dedicated data store, separate from every other organization's. There is no shared pool that all customers' data sits inside and gets filtered out of on each request — your data simply lives somewhere that no other organization can reach.
The practical assurance this gives you:
- One organization's content can never appear in another organization's results. Separation is structural, not a rule that an application has to remember to apply on every query.
- Your connector credentials, settings, and usage all stay within your own workspace.
- There is no cross-organization "tenants" view that any single query could accidentally read across.
A single, clear boundary
Within your workspace, Liddr lets administrators layer organization-wide settings over sensible defaults. Those controls operate entirely inside your own workspace — they are conveniences for your organization, not the boundary between organizations. The boundary between organizations is the separate workspace itself.
What is isolated
Everything that is meaningfully yours lives inside your workspace and only your workspace:
| What | Isolated to your organization |
|---|---|
| Your knowledge graph and the content it's built from | Yes |
| Connector credentials and integration settings | Yes |
| Members, sessions, and access | Yes |
| Configuration and usage history | Yes |
Liddr runs on shared, managed infrastructure — the same way any cloud service does — but your data is never shared. The platform that operates the service is common; the contents of your workspace are not.
Decommissioning a workspace
When a workspace is closed — at the end of a trial, or when an organization leaves Liddr — its data is permanently removed. The dedicated data store backing that workspace is destroyed along with everything in it: knowledge, credentials, settings, and history. Because each organization's data is physically separate, removing one workspace has no effect on any other.
Clean exit
Decommissioning is final and complete. There is no shared remnant left behind in some common store, because your data was never in one to begin with.