For the complete documentation index, see llms.txt. This page is also available as Markdown.

Create a project

Create a project in your organization and choose who can access it.

A project groups related apps inside an organization: a service and its workers, an experiment, or a team's environment. The organization owns the project and pays for its apps. The person who creates it is its creator.

Create the project

  1. Sign in to the portal. Choose the intended organization from the account menu at the bottom of the sidebar.

  2. Open Projects and choose Create Project. You need an Admin or Developer organization role.

  3. Give it a useful name, such as inference-staging, and choose Private or Everyone at your organization. Private is the default.

  4. Create the project, then choose a gallery template or configure your first app.

An organization's Projects URL includes its permanent slug: /dashboard/<org-slug>/projects. The list groups private projects you created, organization-wide projects and other accessible private projects by creator. Filter and sort choices are remembered per organization. Inside a project, apps can be filtered by creator and status.

Work with a team

Private projects are visible to organization admins, their creator and members added through Share. Organization-wide projects are visible to all members within their roles. Apps inherit the project's visibility; a member can also be added to just one app.

Admins and the project's creator manage access and visibility. Developers edit accessible apps with Developer access and delete projects/apps they created. Viewers can inspect, with no terminal or secret values. A resource grant never raises an organization role.

Deleting a project also deletes its apps. A Developer must have created every app inside it; otherwise ask an admin. REST and MCP deletion require all apps to be stopped first.

Removing the creator from the organization does not delete the project or stop its apps. See Members and roles and Sharing and visibility.

Automate project creation

Use POST /projects?org=<slug> with name and optional visibility: "private" or "org", or MCP create_project with an org argument. A credential needs projects:write and the person must be an Admin or Developer. Keys limited to specific projects cannot create another project.

Use MCP update_project to change the name or visibility. The former action name rename_project has been replaced. See Projects API.

Deploy from the App Gallery ยท Create a custom app

Last updated

Was this helpful?