What action can be performed from the Cloud Project Portal (Onboarding Ul) of an Adobe Commerce Cloud project?

The Cloud Project Portal, also known as the Onboarding UI, is the initial interface provided to the project owner (Business Admin). A primary function of this portal is to initiate project setup and manage team access. The project owner uses this interface to invite team members, such as developers or system integrators, and assign them the "Technical Admin" role. This action grants the technical team the necessary permissions to access project environments, code, and perform development and deployment tasks.

A. Set your developer SSH public key. This is a personal action performed by each individual user within their own account settings in the Cloud Console, not a project-level action in the Onboarding UI.
B. Update Project and environment variables This is a technical configuration task performed within specific environments (e.g., Integration, Staging) via the Cloud Console UI or CLI, not in the initial Project Portal.

1. Adobe Experience League Documentation - Onboard with Adobe Commerce on cloud infrastructure: In the section "Step 2: Access the Project Portal," the documentation outlines the initial steps for the project owner. It states, "After you log in, you can create a project and add technical users from your team and from your implementation partner to the project." This directly supports the action of adding a Technical Admin.

Source: Adobe Experience League, "Onboard with Adobe Commerce on cloud infrastructure", Section: "Step 2: Access the Project Portal".

2. Adobe Experience League Documentation - Manage user access: This guide details the process of adding users. It specifies, "The Project Owner, or Business User, receives the initial Adobe Commerce on cloud infrastructure Welcome email... The Project Owner can add Technical users to the project..." The instructions show this is done from the Project Portal by navigating to Manage Users.

Source: Adobe Experience League, "Manage user access", Section: "Add users and teams".

3. Adobe Experience League Documentation - Set up SSH keys: This document clarifies that setting up SSH keys is a prerequisite for developers to access the Git repository and environments. The process involves the user generating a key pair and adding the public key to their account via the My Account > API Keys and SSH Keys tab in the Cloud Console, confirming this is not an Onboarding UI task.

Source: Adobe Experience League, "Set up your local workspace", Section: "Set up SSH keys".

4. Adobe Experience League Documentation - Manage variables: This resource explains that environment variables are managed at the environment level. It states, "You can add and update variables using the Project Web UI or the magento-cloud CLI." The screenshots and instructions point to the environment configuration section of the Cloud Console, not the initial Onboarding Portal.

Source: Adobe Experience League, "Cloud variables", Section: "Manage variables".