> ## Documentation Index
> Fetch the complete documentation index at: https://help.lobyco.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Access to Lobyco Admin Portal

> Connect your Azure AD, grant admin consent, and assign the admin roles that unlock each portal section.

A guide to setting up access to Lobyco Admin Portal

It's important for Lobyco that our clients' employees can easily access the Lobyco Portal. Therefore, we aim to enable them to use their corporate Azure accounts to log in and access the features they are authorized to read or contribute to.

To achieve this, we utilize an Azure Multi-tenant AD setup, which allows managing roles and groups for our Portal Application within your existing Azure AD.

## Configuration values provided by Lobyco

Client needs to share their Azure Tenant ID so that Lobyco can whitelist it and provide following admin portal configuration for pre-production and production environments:

| Environment name | Link                                                                                          | Azure AD app              |
| ---------------- | --------------------------------------------------------------------------------------------- | ------------------------- |
| Pre-production   | [https://admin.\{client\_name}.pre.lobyco.net/](https://admin.\{client_name}.pre.lobyco.net/) | \{client\_name}-admin-pre |
| Production       | [https://admin.\{client\_name}.lobyco.net/](https://admin.\{client_name}.lobyco.net/)         | \{client\_name}-admin-pro |

<Info>
  **Note**: links and app names are only for example and may be different according to the requirement. Contact Lobyco to receive configuration values.
</Info>

## Admin roles

Each tab in the left panel requires the corresponding role — Game Admin, Store Reader, and so on. Which roles are available depends on your client scope.

<Warning>
  Two roles are deprecated and kept only for backwards compatibility: `stampCards.admin` (use `challenge.admin`) and `member.admin.read` (use `member.reader`). Do not assign them to new users.
</Warning>

### Promotion Platform

| Role                      | Grants                                                                                                  |
| ------------------------- | ------------------------------------------------------------------------------------------------------- |
| `promotion.admin`         | Read and write access to the Promotion admin section                                                    |
| `game.admin`              | Read and write access to the Game & Gameplay admin sections                                             |
| `challenge.admin`         | Read and write access to the Challenge admin section                                                    |
| `stampCards.admin`        | **Deprecated** — read and write access to the Stamp cards admin section. Use `challenge.admin` instead. |
| `bonus.calculation.admin` | Read and write access to the bonus admin section                                                        |
| `feed.admin`              | Read and write access to the Feed admin section                                                         |
| `push.admin`              | Read and write access to the Push admin section                                                         |
| `banner.admin`            | Read and write access to the Banner admin section                                                       |

### Member Management

| Role                | Grants                                                                                          |
| ------------------- | ----------------------------------------------------------------------------------------------- |
| `member.admin`      | Read and write access to the membership admin section                                           |
| `member.reader`     | Read-only access to the membership admin section                                                |
| `member.admin.read` | **Deprecated** — read-only access to the membership admin section. Use `member.reader` instead. |
| `consent.admin`     | Read and write access to the consents admin section                                             |
| `consent.reader`    | Read-only access to the consents admin section                                                  |

### Scan\&Pay

| Role                | Grants                                               |
| ------------------- | ---------------------------------------------------- |
| `scanandpay.admin`  | Read and write access to the Scan\&Pay admin section |
| `scanandpay.reader` | Read access to the Scan\&Pay admin section           |
| `scanandpay.write`  | Write access to the Scan\&Pay admin section          |

### Segmentation

| Role             | Grants                                                  |
| ---------------- | ------------------------------------------------------- |
| `audience.admin` | Read and write access to the Segmentation admin section |

### Store Admin

| Role           | Grants                                            |
| -------------- | ------------------------------------------------- |
| `store.admin`  | Read and write access to the Stores admin section |
| `store.reader` | Read-only access to the Stores admin section      |

### System Configuration

| Role                  | Grants                                          |
| --------------------- | ----------------------------------------------- |
| `dataimport.admin`    | Access to the Data Import admin section         |
| `eventlog.user`       | Read-only access to Lobyco logs section         |
| `global.config.admin` | Access to modify Product settings in Admin Tool |

### Other

| Role                 | Grants                                   |
| -------------------- | ---------------------------------------- |
| `bonus.import.admin` | Access to Bonus bulk adjustments section |

## Access setup in the client tenant

Following steps should be performed in the client's tenant by [Global Administrator](https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/directory-assign-admin-roles#cloud-application-administrator), an [Application Administrator](https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/directory-assign-admin-roles#cloud-application-administrator), or a [Cloud Application Administrator](https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/directory-assign-admin-roles#cloud-application-administrator):

<Steps>
  <Step>
    ### Open and log in to Lobyco Admin Portal

    Open Lobyco Admin Portal of the target environment in the browser and log in using your organization credentials.
  </Step>

  <Step>
    ### Accept requested permissions

    <img src="https://mintcdn.com/lobyco-4c9fb3ad/wpdZgjvGMgh4Gbhy/images/3822a461e08126830e1abf7964a6bc0274095bfc.png?fit=max&auto=format&n=wpdZgjvGMgh4Gbhy&q=85&s=a35a3c9b983d3e29747958c99ab638c2" alt="Screenshot from Lobyco Admin Portal - Setting up access" width="1205" height="650" data-path="images/3822a461e08126830e1abf7964a6bc0274095bfc.png" />
  </Step>

  <Step>
    ### Verify the empty portal

    When permissions are accepted, then an empty Lobyco Admin Portal should be displayed.

    <img src="https://mintcdn.com/lobyco-4c9fb3ad/wpdZgjvGMgh4Gbhy/images/2661f19bba739893abcffddff18fc2dc385e9150.png?fit=max&auto=format&n=wpdZgjvGMgh4Gbhy&q=85&s=f589967aa28c02272e378f0dd7682c76" alt="Screenshot from Lobyco Admin Portal - Setting up access" width="3584" height="1568" data-path="images/2661f19bba739893abcffddff18fc2dc385e9150.png" />
  </Step>

  <Step>
    ### Locate the enterprise application

    Go to the Azure portal. Go to Azure Active Directory and then select Enterprise applications. Search for the Lobyco app for the target environment and for the target client in enterprise applications:

    <img src="https://mintcdn.com/lobyco-4c9fb3ad/wpdZgjvGMgh4Gbhy/images/e9f565b091f05ac55e6fc962a6a813baa054562e.png?fit=max&auto=format&n=wpdZgjvGMgh4Gbhy&q=85&s=5aab024b746de15a36b83d079f1418ab" alt="Screenshot from MS AAD Enterprise Applications" width="1214" height="590" data-path="images/e9f565b091f05ac55e6fc962a6a813baa054562e.png" />
  </Step>

  <Step>
    ### Grant permissions consent

    Open the app and go to Permissions. Grant consent on behalf of all users in this directory, so that end users will not be required to consent when using Lobyco Admin Portal application.
  </Step>

  <Step>
    ### Assign users and groups to roles

    Go to Users and Groups.

    Press Add user/group button. Select users/security groups and assign roles. A single user or security group can have multiple roles assigned — for example, a user assigned `game.admin` gets access to the game admin section.

    <Info>
      **NOTE**: If the client has Azure AD Premium, the admin can assign a security group to a role, and user members of the group will inherit the app role. This is a convenient way to manage roles, because the group owner doesn't need to be an admin or app owner.
    </Info>
  </Step>

  <Step>
    ### Verify access

    Open Lobyco Admin Portal in another tab. The applications and services you have roles for should be available in the left panel:

    <img src="https://mintcdn.com/lobyco-4c9fb3ad/wpdZgjvGMgh4Gbhy/images/40d1a13d73381b732a0b5df5669c660c5261ca1c.png?fit=max&auto=format&n=wpdZgjvGMgh4Gbhy&q=85&s=1fce657bb86f9671810645bd41512b4b" alt="Screenshot from Lobyco Admin Portal" width="3584" height="1086" data-path="images/40d1a13d73381b732a0b5df5669c660c5261ca1c.png" />
  </Step>
</Steps>
