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
Open the Project selector.
Choose New Project.
Give the Project a descriptive name and icon.
Add initial members if appropriate.
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.
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 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.
Last updated
Was this helpful?