> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/administer-and-govern/control/settings/projects.md). # Projects Projects in Lleverage are working environments for a related operational area. They keep the Agent, Workflows, Skills, Tables, Knowledge, Connections, files, monitoring and access configuration around that work together. ### Key features * Group related operational capabilities and context in one Project * Project-specific Activity and operational views * Built-in and custom role-based access * Item-level sharing for Apps, Workflows, Tables and Knowledge Bases * Customisable Project identity and navigation * Easy switching between Projects you are authorised to access ### Create a Project 1. Open the Project selector. 2. Choose **New Project**. 3. Give the Project a descriptive name and icon. 4. Add initial members if appropriate. 5. Create the Project. Use names that describe the operational responsibility or use case rather than a temporary implementation detail. ### Manage Project access Open **Control → Members** inside the Project to manage people and access. You can assign the built-in **Admin, Builder, Operator or Guest** roles, or a Project-specific custom role. Custom roles can narrow access by Project area and selected items. Individual Apps, Workflows, Tables and Knowledge Bases can also be shared without giving broader Project access. Use **Preview as this member** when you need to check what someone will actually see before handoff. For the current access model, see [Roles and Permissions](/administer-and-govern/control/members/roles-and-permissions.md). ### Switch between Projects Use the Project selector to move between Projects you can access. The interface then resolves that Project's context, capabilities and permissions. ### Organise work inside a Project Keep related Workflows, Skills, data and operational context together when they serve the same responsibility. Split Projects when the work needs a genuinely different context or access boundary, not merely because one Project contains many objects. ### View Project activity Use Activity and Project dashboards to inspect runs, Agent sessions, feedback and operational metrics available for that Project and your role. ### Customise Project navigation Each Project's sidebar and landing page can be tailored in its settings under **Navigation**. Pins and navigation configuration affect how people find pages; they do not replace access permissions. See [Finding your way around a Project](/run-operations/overview/navigation.md) for the current navigation model. ### Good Project hygiene * Keep the Project purpose clear. * Use the narrowest access that matches each person's responsibility. * Review membership and custom roles when ownership changes. * Keep authoritative operating context close to the work that uses it. * Use Activity and feedback to verify that the Project is doing the intended work in production. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.lleverage.ai/administer-and-govern/control/settings/projects.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.