> 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.5-agent-assisted-workflows.md). # Agent-Assisted Workflows Alludium uses agents, skills, integrations, and automations behind many workflows. As a Member, you usually do not need to build or configure those pieces before using them. Think of them as the operating system behind the tasks and projects you see. ## Agents An agent is a focused AI worker configured for a specific job. In everyday use, you may meet agents as: * A task assistant that helps draft, research, review, or summarize work. * A project manager assistant that understands a project or deal room. * A file assistant that helps inspect and reason over uploaded documents. * A configured workspace assistant that follows your team's workflow rules. Members should treat agent output as draft work for review. Agents can gather context and prepare outputs, but humans still decide what is correct, approved, and ready to use. ## Skills A skill is a reusable playbook that tells an agent how to approach a kind of work. You might not see the skill directly. Instead, you see the effect: a task or project workflow produces a structured screening memo, market map, meeting brief, red-flag scan, or other repeatable output using the method your team configured. If an output follows a consistent format, uses a specific review framework, or asks for a particular set of inputs, a skill may be part of the workflow behind it. ## Integrations An integration connects Alludium to another system, such as a CRM, email, calendar, document store, search provider, or communication tool. Members may be asked to connect a personal account when a workflow needs access on their behalf. For example, a task may need your calendar, email, or CRM account rather than a shared workspace credential. You do not need to manage the integration catalog to use a workflow. If a connection is missing, the workflow should tell you what needs attention. ## Automations An automation runs configured work on a schedule or recurring cadence. As a Member, you usually see automation results rather than the automation setup itself: * A task appears in the Inbox. * A file or report is generated. * A project receives an update. * A notification tells you something needs review. Automations should still preserve human review where the workflow requires a decision. ## Project Setups And Packs A project setup defines the shape of a project. It can determine fields, lifecycle stages, default tasks, file expectations, and workflow guidance. A pack is a bundle of setup assets for a domain. The VC pack, for example, can provide deal-room and origination-pipeline structures, task workflows, methodology guidance, recommended files, and integration expectations. Members use the projects created from these setups. Admins and Owners manage the setups themselves in Administration. ## What To Do When Something Is Missing If you expected to see a task, project type, file option, connection prompt, or workflow and it is not available, ask an Admin or Owner. The missing piece may need to be enabled, configured, connected, or assigned to your workspace. --- # 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.5-agent-assisted-workflows.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.