> For the complete documentation index, see [llms.txt](https://alludium.gitbook.io/alludium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alludium.gitbook.io/alludium-docs/readme/1.4-core-concepts.md). # Core Concepts Alludium is a workspace for turning repeatable knowledge work into governed AI workflows. The platform has two layers: * **Everyday work** - the surfaces most Members use to get work done. * **Administration** - the reusable systems Admins and Owners manage behind the scenes. ## Everyday Work Concepts | Concept | What It Is | | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | | **Workspace** | The shared environment where your team works. | | **Inbox** | The main work queue for tasks. It is the default landing surface after sign-in. | | **Task** | A unit of work with state, context, conversation, inputs, outputs, and completion requirements. | | **Project** | A durable workspace for an initiative, such as a deal room, pipeline, campaign, customer engagement, or research workflow. | | **Files** | Uploaded or generated documents used as durable context for tasks, projects, and agent-assisted work. | | **Settings** | The place to manage account preferences, workspace people views, notifications, appearance, privacy, and role-dependent workspace controls. | Most Members spend most of their time in these concepts. ## Administration Concepts | Concept | What It Is | | ------------------ | --------------------------------------------------------------------------------------------------------------------- | | **Project Setup** | A reusable blueprint for creating projects with the right fields, lifecycle, tasks, files, agents, and integrations. | | **Pack** | A packaged set of project setup assets, task types, files, integrations, and guidance for a specific workflow domain. | | **Task Type** | A reusable definition for a kind of task, including fields, schema, execution defaults, and expected outputs. | | **Agent Builder** | The configuration environment for creating, testing, and deploying agents. | | **Templates** | Pre-built starting points for agent creation. | | **Skills** | Reusable instructions or playbooks that can be attached to agents. | | **Integrations** | The unified surface for external systems, available tools, and authenticated connections. | | **Connections** | Scoped credentials that let Alludium use an external system on behalf of a user or workspace. | | **Tools** | Specific actions exposed by an integration, such as searching docs, creating records, or retrieving CRM data. | | **Automations** | Scheduled or recurring work configured to run without manual prompting. | | **Execution Logs** | The run history for automation and execution activity. | These concepts are usually configured by Admins or Owners. Members benefit from them through the task, project, and file experiences they enable. For a simpler user-facing explanation of these concepts, see **Agent-Assisted Workflows**. ## How Components Work Together Most work starts from the Inbox or a project. **Inbox and tasks organize active work.**\ Tasks give work a durable state. A task can have required inputs, structured outputs, linked files, child tasks, and its own conversation. **Projects organize ongoing initiatives.**\ Projects group related tasks, files, data, activity, integrations, and team context. A project setup determines the shape of a project: its lifecycle, fields, default tasks, and recommended integrations. **Files provide persistent knowledge.**\ Files can be uploaded to the workspace, linked into projects or tasks, and used as context for agent-assisted work. **Agents support the workflow.**\ Members may interact with agents through tasks, projects, files, or configured workspace assistants. Admins and Owners manage direct agent configuration through Agent Builder, templates, skills, integrations, and automation settings. **Integrations connect Alludium to external systems.**\ Integrations contain available tools and connection options. A connection authorizes access. A tool is the specific action an agent or workflow can use. **Automations schedule repeatable work.**\ Automations can run work on a schedule and produce execution logs so results and failures can be reviewed. ## Why The Separation Matters Alludium separates everyday work from configuration so each workflow has clear context and permissions. That separation helps prevent: * Confusing one workflow's tools with another's * Mixing unrelated project context * Using files outside the intended workflow * Losing task state in one-off conversations * Running automated work without a visible audit trail --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://alludium.gitbook.io/alludium-docs/readme/1.4-core-concepts.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.