Projects
A project holds members, apps (launchers), flows, storage, and project credentials. On AWS and Google Cloud the estimated cost of everything you run is tracked under the project it runs in (see How costs are tracked). Kubernetes environments show no costs. Project settings such as time limits apply to it. Your projects show as cards on the home page.
A project, in the order you meet it
Section titled “A project, in the order you meet it”- Create a project with New Project, or ask a project Owner to add you to theirs.
- Change project settings on the General tab of Project Settings.
- Add and manage members under Members on the same tab.
- Project credentials on the Credentials tab, for flow stages that call AI services.
- Use the project: Storage, Storage Settings, Apps, and Flows.
- Learn who can do what and how costs are tracked.
- When the work is done, archive, restore, or delete the project.
| Role | Can do |
|---|---|
| Owner | Everything an Editor can, plus change settings, members, and credentials. |
| Editor | Add and change apps, flows, and buckets. Pick credentials. |
| Reader | See the project, launch an app, delete an app they started, write files and bucket objects, and run shared flows. |
System admins can do everything an Owner can on every project. For the full list, see Roles and permissions.
eureka project summary and the MCP tool project_summary return the home-card counts (apps and flows running, starting, and failed, and a storage count) in one read. The card on the home page still opens Apps, Flows, and Storage.