Skip to main content
The Projects tab is the DryRunPro home screen. It is where you land after sign-in, and it is the visual answer to the question “which Adobe Commerce Cloud projects am I responsible for, and what is the state of each one’s dryrun fleet?”. This page documents the layout, the per-project card model, the project ID convention, the search bar, and the four interactive elements on each card (Delete Project, View Details, Team dropdown, Add Project). Live URL: app.vortexiq.ai/v2/apps/dryrunpro/project

​
What you see when you land here

The Projects tab is a three-column grid of project cards. The screenshot of a populated tenancy shows eleven cards across three columns: Ulster Weavers Ltd, Xupes Limited, Bahrain Duty Free Company WLL (Dublin), Soak and Sleep, Independent Buying Consortium, Eggfree Cake Box Limited Azure, Eggfree Cake Box Ambala, Boutinot Ltd, Blitz Corporation Ltd, Bahrain Duty Free Company W.L.L., and Krispy Kreme UK and Ireland. Above the grid, a single Add project button (top right, dark blue) opens the Add Adobe Commerce Cloud Project wizard. To the left of that button on smaller widths, a search field filters the project list by name or by Project ID. The left rail shows the seven top-tabs with Projects highlighted in the active state.

​
The per-project card model

Every project card has the same structure, top to bottom:
  1. Project name, in bold black, e.g. “Bahrain Duty Free Company WLL (Dublin)”. This is the human-readable name you set in the Add Adobe Commerce Cloud Project wizard.
  2. Project ID, in small grey text under the name, e.g. “Project ID: 47k74xtjq6jya”. This is a thirteen-character lowercase alphanumeric handle that DryRunPro generates at creation time. It is the canonical identifier used in URLs, API calls, and audit logs.
  3. Adobe Commerce Cloud sub-section, with three statistics in a horizontal strip:
    • Environments count (e.g. 4), how many Adobe-side environments DryRunPro can see (typically integration, staging, production, plus any feature branches).
    • Storage (e.g. 51200), reported in megabytes.
    • Users count (e.g. 13), how many users are entitled to the Adobe Commerce Cloud project itself (this is the Adobe-side roster, not the DryRunPro roster).
  4. DryRun Pro sub-section, with three statistics in the same layout:
    • Staging count (e.g. 1), how many dryrun environments DryRunPro is currently maintaining for this project.
    • Packages count (e.g. 2), how many Docker packages have been produced from completed dryruns.
    • Users count (e.g. 2), how many users have been added to this project on the DryRunPro side. This is independent of the Adobe-side count.
  5. Team dropdown. A short label (e.g. “No team”, “Cakebox”, “Blitz”, “BDFC”) with a chevron. Click to open the dropdown and reassign the team. See Teams for the full team model.
  6. Delete Project button (red, bottom-left). Triggers the Delete Project workflow.
  7. View Details link (blue, bottom-right). Opens the Project Overview page for that project.

​
Project ID convention

Project IDs in DryRunPro follow a deterministic pattern: thirteen lowercase alphanumeric characters with no separators, generated at creation time. Examples from a real tenancy:
ProjectProject ID
Ulster Weavers Ltda4mhquy4qw1n
Xupes Limited3yikcfa7kpu5l
Bahrain Duty Free Company WLL (Dublin)47k74xtjq6jya
Soak and Sleep5oti7tlrqaeo
Independent Buying Consortium5z075lqewa
Eggfree Cake Box Limited Azureaaeu0gl4q4n5
Eggfree Cake Box Ambalamowelo3ldewdw
Boutinot Ltdacabbu0e3z4c
Blitz Corporation Ltdaeqpt1g4tj8
Krispy Kreme UK and Irelandqg9oqvw1869
The Project ID is what appears in the URL when you open a project’s detail page: /v2/apps/dryrunpro/projectoverview?project_id=akt4buy2iqm7o. It is also the value you reference in API calls and in support tickets. The Project ID is not the Adobe Commerce Cloud project ID (the one that comes from accounts.magento.cloud/user). Those are two different identifiers. The Adobe Cloud project ID is supplied as input during the Add Project wizard; the DryRunPro Project ID is generated as output. We document the mapping on the Project Overview page. The search field accepts free text and filters the visible cards by:
  • Project name (partial match, case-insensitive)
  • Project ID (partial match)
  • Team name assigned to the card
Search runs client-side on the cards already loaded, so it is instant. There is no server round-trip and no minimum character count.

​
Connect with DryRun Pro modal

When the user clicks Add project for the first time, or any time DryRunPro detects that a project card needs its credentials reconfirmed, a Connect with DryRun Pro modal opens. It contains:
  • A short instruction: “Enter the project ID and check access. Please add the deploy bot (e.g. docker@247commerce.co.uk) as super-admin to your Adobe Commerce Cloud (its the same account whose SSH key is in DRP_ssh2id_rsa and whose Cloud CLI token is configured in config).”
  • A Cloud project ID input field (placeholder: “Enter Magento Cloud Project ID”).
  • An Assign to team dropdown (default: “No team”). This is the same team selector as on the project card.
  • A Check access & Save button (dark blue, full-width).
The modal is the same control surface that appears on a card when DryRunPro can no longer reach the Adobe Commerce Cloud project (typically because the deploy bot lost super-admin access on the Adobe side). Re-validate by entering the project ID, picking the team, and clicking Check access & Save.

​
Card states

A project card can be in one of three visual states. Healthy, the default. All three Adobe Commerce Cloud counts populate, the DryRun Pro counts populate, the team dropdown shows the assigned team. View Details and Delete Project both work. N/A, partial visibility. One or more Adobe-side counts show “N/A” (most often Storage). This means DryRunPro could read part of the project but Adobe declined to surface a particular metric. The card still works for spinning up dryruns; the missing metric is purely informational. Connect with DryRun Pro modal, blocked. The card cannot complete its read against Adobe Commerce Cloud and prompts you to re-enter the Cloud project ID. Until you do, the dryrun fleet for that project is paused.

​
Add project

Click Add project (top right) to open the five-step Add Adobe Commerce Cloud Project wizard. The wizard walks you through:
  1. Sign in to accounts.magento.cloud/user, click into the project, and add the deploy-bot user.
  2. Open the project’s setting wheel.
  3. Click Add User to add the deploy bot as a super-admin.
  4. Tick the SUPER USER checkbox, save the user, and confirm the deploy bot’s SSH key + API token are in DryRunPro config.
  5. Copy the project ID from account.magento.com/cloud/project/subscriptions/ and paste it on the next screen.
The card appears in the grid the moment the wizard completes the access check.

​
Sorting and ordering

The Projects tab does not currently expose a manual sort order. Cards are returned in creation order (oldest at the top, newest at the bottom). If you have ten or more projects, use search to jump directly to the one you want. A future release will add column sort controls.

​
Pagination

There is no pagination. All project cards in your tenancy load on the first page. Performance is fine well into the dozens of projects because each card pulls its Adobe Commerce Cloud + DryRun Pro stats from a cached snapshot, not by re-querying Adobe on every page load.

​
Frequently asked questions

Why does my Storage column show “N/A”? Adobe Commerce Cloud does not always surface storage figures via the Cloud CLI. When that happens DryRunPro displays “N/A” rather than guessing. The functional dryrun fleet is unaffected. Why does my “Adobe Commerce Cloud Users” count differ from “DryRun Pro Users”? The Adobe count is the number of users that have access to the Adobe Commerce Cloud project on the Adobe side, surfaced through the Cloud CLI. The DryRunPro count is the number of users you have explicitly added to the project on the DryRunPro side via Project Users. They are independent rosters, kept independent on purpose, so that internal engineers can have DryRunPro access without needing Adobe-side access, and vice versa. Can I rename a project after creation? The display name is editable from the Project Overview detail page. The Project ID is immutable. The Add project button is greyed out for me. You do not have the project_overview_access permission, or you are signed in as a Tester role rather than an Admin or Team Leader. See Roles for the role to permission mapping. A project card shows “Connect with DryRun Pro” instead of stats. What broke? DryRunPro lost its read access to the Adobe Commerce Cloud project. The most common cause is the deploy-bot user (e.g. docker@247commerce.co.uk) being removed from the Adobe project’s super-admin list. Re-add the deploy bot on the Adobe side, then re-enter the Cloud project ID in the Connect modal. How many projects can a single tenancy hold? There is no hard ceiling. Live tenancies are running with eleven projects in the bundled screenshot and are tested up to several dozen. Performance scales linearly because cards render from cached snapshots. Where do I see all dryrun environments across all projects, in one list? On the Dryrun Environments tab, second item in the left rail. The Projects tab is project-centric; the Dryrun Environments tab is environment-centric. Use whichever lens fits the question you are answering.