Concepts
Apps
First-party apps you install per project — Environments and Tasks.
Features inside a project are delivered as apps. Each project installs the apps it needs from Apps (/studio/p/<slug>/apps). The list of apps lives in code (appRegistry in @loftlancer/actions/apps); a project_app row records which project has which app installed. There are no third-party apps.
Available apps
| App | ID | What it adds | Project page |
|---|---|---|---|
| Environments | env | Environments and encrypted variables with .env import and export | /studio/p/<slug>/env |
| Tasks | tasks | Numbered tasks with status, priority, assignee, due date, labels and comments | /studio/p/<slug>/tasks |
Both apps are free.
Install and uninstall
- Installing an app shows the permissions it uses and the data it creates.
- Each app owns a set of actions (for example
variable.revealbelongs toenv,tasks.task.createtotasks). When an app is not installed on a project, its actions are denied withapp_not_installed, in the UI and the API alike. - Uninstalling keeps the app's data for 30 days. Reinstalling within that window restores it; after that the data is scheduled for purge.
Installing and uninstalling are the project.app.install / project.app.uninstall actions.
Permissions
App actions follow the normal roles and permissions rules. Tasks actions, for example, need project access for managers (project assignment) and members (a team on the project plus a grant).