Granting Realm-Scoped Developer Permissions

Administration of game makers on the game project

When your Beamable account contains multiple games, you may wish to allow different teammates different access levels depending on which game they are working on. This article shows how to set up realm-scoped permissions.

Instructions

This guide assumes there is already an account for the person whose access you are changing. If they need a new account, follow the instructions in https://docs.beamable.com/docs/adding-developers-to-your-beamable-account first, giving them "tester" access to begin with.

  1. Navigate to https://portal.beamable.com/ and enter your customer ID (CID).
  1. Log in using the email and password with which you registered your project.

  2. Go to the Team tab to see your list of admins, developers, and testers. Use the search field or scroll to find the teammate whose permissions you are changing.

  1. Press the "Permissions" button within the teammate's row in the table. This will open a dialog that allows you to edit account permissions.
  1. Use the "Add a realm-scoped role" button to set up realm-scoped permissions. This allows you to specify which realm and which role, such as "admin" or "developer", to apply.

  2. Press the "Save" icon button to the right of the new realm-scoped role to put the permission update into effect. Until you hit Save and the button's action indicator stops spinning, any changes in this dialog will have no effect.

👍

Notes about Realm-Scoped Permissions

  • If somebody's Global role is higher than their Realm-scoped role, the Global role will take precedence.
  • Realm-scoped roles propagate through the Realm hierarchy. Using a Prod->Staging->Dev setup as an example, if my Global role is "tester" and my team lead set me as a "developer" in staging and an "admin" in dev, then:
    • In Example-prod, I only have tester permissions, because of my Global role.
    • In Example-staging, I have developer permissions, because of my Realm-scoped role there.
    • In Example-dev, I have administrative permissions, because of my Realm-scoped role there.
    • Additionally, if any of my colleagues make a new child realm under Example-dev, I will be an admin there as well.
    • Likewise, if someone makes a child realm under Example-staging (that is, a sibling of dev), I will have developer permissions there.

📘

TIP: Finding your CID

To get your customer ID (CID), look for config-defaults.txt in your project. The shell snippet below illustrates how to get it from the command line if you are on MacOS.

% find . -name config-defaults.txt
./Assets/Beamable/Resources/config-defaults.txt
% grep cid ./Assets/Beamable/Resources/config-defaults.txt
    "cid": "1320644969098300",

Did this page help you?