Prepare project environments

To initially set up your Magento Commerce (Cloud) project, you need the Project Owner to create the project, add a super user, and generate Magento Commerce authentication keys. The account owner has sole authority over the project and account to manage your store, project and Git access, and more.

As the Project Owner, you must complete the following, required by development and technical resources:

  • Access to the Magento Commerce (Cloud) project through added user accounts
  • Generate Magento authentication keys
  • Create the project
  • Add a project admin account

After you have completed those tasks, the project admin can manage development and deployments for you.

Generate Magento authentication keys

Important: This step is required for the Project Owner.

Any developers or users that want to access the project require Magento authentication keys. The Project Owner needs to generate Magento authentication keys (includes 1 public and 1 private) through a Magento Marketplace account for themselves and any other user. Only the Project Owner can create these keys. When you first create your project, you will be prompted to add them.

You must create one set of keys for each technical person you expect will work on Magento Commerce. Each user must add these keys to their auth.json file, which is located in the project root directory. We recommend against providing the keys over e-mail because it isn’t secure. Please find a secure method, working with your IT staff, for distributing the keys.

To create authentication keys through the Magento Marketplace:

  1. Log in to the Magento Marketplace. If you don’t have an account, click Register.
  2. Click your account name in the top-right of the page and select My Profile.
  3. Click Access Keys in the Marketplace tab.

    Click Access Keys

  4. Click Create A New Access Key. Enter a specific name for the keys, for example CloudProductOwner or the name of the developer receiving the keys.
  5. The keys generate a Public and Private key you can click to copy. Save this information or keep the page open when creating your project.

Create the project

The project contains all of your code branches, environments from development to Production, and allows you to manage access and configurations. After the Project Owner has signed up for a plan and logged in from the email, they can begin creating and managing the project.

The Project Owner creates the project, selecting the option for a blank site, which is a fully functional Magento template of a store and code. When created, we generate a master branch of Git code from and add it to a development environment. This environment is master production for Starter and master Integration for Pro.

If you are concerned with creating the Project, you can create a Technical Admin and have them create the project.

  1. Access your account. You can open the email you received from Magento Cloud,, and click the Access your project now link. Or you can log in to your Magento Commerce account.
  2. Click the Projects tab. You should see an untitled new project.
  3. Click the name of your [Untitled Project] project and enter a name. Click Next.

    Enter a name for your project

  4. Click Create a blank site from a template and click Continue. We recommend always starting with the blank site from a template as your initial project option. You will deploy this code across all environments including Staging and Production as part of your First-time development setup. If you have an existing Magento deployment, you can later import code, extensions, themes, and data after fully deploying this base Magento code.

    When you initially set up a project from a template, we retrieve the code from the magento-cloud-configuration repository, build and deploy it as your Master branch.

    Create a site using the sample Magento project

  5. When prompted, enter your Magento Commerce authentication keys in the provided fields. You created these keys earlier in the Magento Marketplace. Enter the keys and click Finish.

    Enter your authentication keys

  6. Wait a few minutes while the project deploys. A status of pending displays until completed, similar to the following:

    Your sample Magento project

  7. After the project deploys, Success displays next to the name of your project.

You should create user accounts to this project for each developer, administrator, and consultant that needs access to the code.

Create project admins and user accounts

As discussed in more detail in Manage users, Magento Commerce (Cloud) has a number of user roles and permissions available project-wide or per environment.

Typically, the only user the Project Owner must create is the Technical Admin. This user should have the Super User role. Your Technical Admin can create user accounts for developers, set environment permissions, and manage all branches and environments.

Before you start, create a list of e-mail address for the users you want to add. New accounts receive an invitation to register with Magento Commerce (Cloud) and receive access based on the role. You can add and manage users at any time.

To create user accounts:

  1. Log in to your Magento Commerce (Cloud) account.
  2. Click the Projects tab as the following figure shows.

    Click the projects tab to access your Cloud project

  3. Click the name of your project. If you have not named your project, click Continue Later to bypass and create a user.
  4. Click the configure project button next to project name in the top navigation bar as the following figure shows.

    Configure the project

  5. In the right pane, click Add Users.

    Start creating users

  6. Click Add User.

    The page displays as follows.

    Create the account

  7. Enter the user’s e-mail address.
  8. Select the access for the account:

    • For a project administrator account, select the Super User check box. This provides Admin rights for all settings and environments, including creating the project. If not selected, the account has only view options for all environments on a project and requires branch specific permissions.
    • Select permissions per specific environment (or branch) in the Integration environment: No access, Admin (change settings, execute action, merge code), Contributor (push code), or Reader (view only). As you add active environments, you can modify permissions per user.
  9. Click Add User.

The users you add receive an e-mail inviting them to join the Magento Commerce (Cloud) project. The user must follow the prompts to register an account and verify their e-mail address. They receive access based on the set project and environment permissions.

Blackfire and New Relic

Your project includes Blackfire and New Relic services. Your project console displays your credentials for these services. Only the account owner has initial access to the credentials and services. You should provide these credentials to technical and developer resources as needed. Profiler provides tools for reviewing and optimizing Magento and your store in your environments. The profiler checks every method and call, determining what occurs with performance metrics per step.

New Relic APM provides application metrics and performance information for Staging and Production environments. This service is not the module or extension and does not provide infrastructure (hardware) monitoring. Do not install the New Relic module with this service in Magento Commerce (Cloud).

Blackfire credentials

To get your Blackfire Profiler credentials:

  1. As the Magento Commerce (Cloud) account owner, log in to your Magento Commerce project.
  2. In the upper right corner, click <your name> > Account Settings as the following figure shows.

    Go to account settings

  3. On your account page, click View Details for your project as the following figure shows.

    View your project details

  4. On your project details page, expand Blackfire.

    Your Blackfire credentials display similar to the following.

    Your Blackfire credentials

New Relic credentials

Your New Relic APM credentials are displayed on the same page as Blackfire. You may receive the initial New Relic invitiation through an e-mail. You can create New Relic users and provide that information to your technical resources responsible for administering New Relic.