A workspace is a shared space for one team or one project. Everything you do in Aleria, every chat, file, source, and saved agent, lives inside a workspace. When you invite someone in, they get access to everything in it.
Inviting someone to a workspace gives them access to everything inside it — chats, files, sources, and saved agents. Keep separate projects in separate workspaces when people should not share that context.
What a workspace actually is
Think of a workspace the way you think of a shared drive. It has a name, members, files, and content that grows over time. The difference is that a workspace also has memory. The chats inside it, the sources connected to it, and the knowledge your teammates build up all become context that Aleria can draw on when it helps you.
Most organizations run one workspace per department, such as Legal, Finance, or HR, or per project, such as an acquisition or a quarterly audit. You can belong to several workspaces at once and switch between them freely.
Workspaces are isolated from each other. Files in one workspace are not visible to people in another workspace, even if they are on the same team. If Legal and Finance need to share something, put it in a shared workspace or duplicate it.
Organization vs workspace
It helps to know the difference between two levels:
- An organization is your company's account. It holds the plan, billing, and seats, and it can contain many workspaces.
- A workspace is one team's or one project's space inside that organization.
You usually work day to day inside a workspace. Plan and billing settings live at the organization level. See Plans and feature availability.
Create a workspace
- Go to the workspace switcher in the top-left corner.
- Choose New workspace.
- Give it a name and pick an icon.
- Create it.
You can change the name and icon later. A new workspace starts empty (no files, no sources, no memory), so your next step is usually to bring in files or connect data sources.
Invite people
- Open Members in the workspace settings.
- Add teammates by email.
- Choose a role.
- Send the invite.
Teammates appear in the workspace the moment they accept.
Workspace roles
There are three roles:
| Role | What they can do |
|---|---|
| Owner | Full control of the workspace, including settings and removing members. Usually one or two people per workspace. |
| Admin | Manage the workspace day to day, including inviting members and managing shared resources. Cannot transfer ownership. |
| Member | Do the everyday work: chat, create agents and workflows, and use shared sources. Cannot change workspace-level settings. |
Beyond the role, specific actions can be allowed or restricted per member, such as who can invite new people or create workflows. Your Owner or Admin controls those permissions in workspace settings.
Sources
Drag files into the sources tab to make them available to everyone in it. Aleria reads them once and remembers the contents. You can attach a file to a specific chat for a focused conversation, or leave it in the workspace library to be picked up automatically when relevant.
Supported file types include:
- Documents: PDF (including scanned PDFs), Word, TXT, Markdown, RTF
- Spreadsheets: Excel, CSV, TSV, Google Sheets exports
- Slides: PowerPoint, Keynote exports
- Images: PNG, JPG, HEIC, SVG
- Audio and video: MP3, WAV, MP4, MOV (transcribed on upload)
- Archives: ZIP (extracted automatically)
- Code and logs: any text-based source file
Sources
A source is a live place your team's data lives or gets stored. Most workspaces end up with a mix of three kinds:
Databases you create in Aleria
Open Sources, create a new database, give it a name, and you have a ready-to-use database in seconds. You can push data into it straight from chat, for example by saying "import this CSV" or "add a row for the Acme deal." You can then query it from any chat, agent, workflow, or board. There is no external setup and no database ticket to file.
Existing systems you connect
Bring in data you already have, such as company databases, warehouses, SaaS tools, cloud storage, or event streams. Connecting a system is usually a one-time admin step. After that, everyone in the workspace can ask questions that span every connected source. See Connectors and Big Data Fusion.
Generated artifacts saved back
Anything Aleria produces, such as a cleaned table, a merged dataset, a report, or a workflow output, can be saved back as a source. That is how a one-off analysis becomes a reusable dataset that the next chat, agent, or workflow can pick up.
Sources are shared by default. Once a source is added, every member can use it. When a source updates, every board, agent, and workflow that reads from it sees the update automatically.
Shared memory
As your team uses Aleria, the workspace builds up shared memory. This includes conventions, such as "we always refer to Q1 as the fiscal February to April window," people, such as "Priya leads procurement," and past decisions, such as "we rejected the Acme proposal in February because of exposure limits."
New teammates inherit this context the moment they join. You can inspect and edit the memory directly in workspace settings, so nothing is hidden.
Switch between workspaces
Use the workspace switcher in the top-left, or press Cmd + K (Windows and Linux: Ctrl + K) and type the workspace name. Your chat history is scoped to each workspace, so switching away does not mix conversations.
When to create a new workspace
Create one per team, per project, or per confidentiality boundary. Do not create one per person, because that defeats the purpose. A good test is: would this group of people want to see each other's work? If yes, use the same workspace. If no, use different workspaces.