> 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/administration/11.4-project-setups-and-packs.md). # Project Setups and Packs Project Setups are reusable blueprints for projects. They define what a project should look like when it is created and what supporting workflow assets should be available. This is an Administration page for Admins and Owners. Members usually use the projects created from these setups rather than managing the setup blueprints directly. **Location:** Administration -> Project Types The main navigation label is **Project Types**. The page header may describe the same area as **Project Setups** because it manages reusable setup blueprints for projects. ## What A Project Setup Defines A project setup can define: * Project name and description defaults * Lifecycle stages * Structured data fields * Default or recommended task types * Recommended integrations * Required setup steps * File templates or source files * Agent or manager guidance * Team or role expectations ## Source Templates And Workspace Setups Project Setups can come from different sources. **Source templates** are reusable blueprints supplied by the platform or an external pack. **Workspace-owned setups** are customized for your workspace. **Activated setups** are ready to use for creating projects. **Available setups** can be selected or configured when your workspace needs them. The Project Types page separates **Source Templates** from **Workspace Custom and Forked** setups. Source templates can show states such as **Needs activation** or **Available**. Workspace-owned setups can be forked, customized, saved, and versioned. Project setup management is workspace administration. Owners can create workspace-owned project types, edit project type details, create and update versions, attach files, and manage project type document templates. Admin access can vary by workspace policy and feature rollout. ## Packs A pack is a packaged workflow domain. It can include project setups, task types, recommended files, integrations, and setup guidance. Use packs when a workflow needs more than a blank project. The VC pack includes pack-backed deal pipeline or deal-room setup, venture-specific task types, file and methodology templates, agent templates, skills, workspace variables, and recommended integrations. The VC pack keeps origination and opportunity work conceptually separate. Origination work is for standing sourcing, enrichment, scoring, review, and promotion. Deal-room work is for one opportunity from intake or promotion through screening, evaluation, diligence, IC, closing, and portfolio handoff. The exact visible project setup label can vary by pack version and activation state. ## Setup State Some project setups are ready to use immediately. Others require setup before activation. Setup can include: * Reviewing required fields * Connecting recommended integrations * Supplying workspace-specific configuration * Opening or completing a setup task * Confirming readiness before the setup is used in live projects External pack templates can move through states such as: | State | Meaning | | --------------------- | ------------------------------------------------------------------------------- | | **Needs activation** | The source template exists, but the workspace has not enabled it yet. | | **Setup in progress** | A setup task is open for that project type and should be continued or reviewed. | | **Activated** | Workspace configuration is enabled and teams can use the project type. | | **Available** | The project type is ready to use and does not require guided setup. | For external pack project types, **Activate** enables the workspace configuration for that source template. **Start setup** or **Manage setup** opens the guided setup task and takes the user into the task workspace. The setup editor can include areas such as Setup, Details, Overview, Connections, Variables, Team, Files, Schedule, Lifecycle, Data Shape, Context, Tasks, Agents, and Skills. The tabs available depend on the selected setup. Project Type tabs load supporting data as needed. For example, the Team tab loads available workspace members, Tasks loads compatible task definitions and templates, Integrations loads available integrations and connection status, and Agents loads deployed agent options. ## Forking Or Customizing If your workspace needs a different lifecycle, data shape, task set, or integration pattern, create or customize a workspace-owned setup instead of changing a source template directly. Before customizing: 1. Identify what the source setup already provides. 2. Confirm which fields or stages need to change. 3. Check whether task types or integrations depend on those fields. 4. Test a project created from the customized setup. ## When To Use Project Setups Use a project setup when: * Many projects should follow the same structure. * Project creation should ask for consistent fields. * Tasks should be created or suggested consistently. * The project needs a defined lifecycle. * Recommended integrations or files should be clear from the start. Use a simpler project when the work is one-off and does not need a repeatable structure. --- # 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/administration/11.4-project-setups-and-packs.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.