Versions Compared

Old Version 23

changes.mady.by.user Yildirim, Semih

Saved on

compared with

New Version Current

changes.mady.by.user Pierzynski, Augusto

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

These guidelines are intended to help markets easily onboard with the User Management capabilities. For any questions/feedback you may have, please reach out to Semih Yildirim.

Navigation

User Management Capabilities

Tip

User Management enables FZs to create users, manage their roles and exact set of permissions directly from the Digital Operations Portal.​

...

Users with the Edit Product Availability permissions can:

  • Make different menu items available or unavailable, for different restaurants/restaurant, service modes (and later channels)

  • Use either the Editor or the CSV Upload capabilities for making availability changes

Market Onboarding

  • Please share information about the first admin user in the market with the development team (via reaching out to syildirim@rbi.com). This user will have access to all the restaurants in the region for a given brand (e.g. BK). The following information needs to be shared:

    • Okta ID

    • E-mail

    • Name

  • Upon receipt, the development team will add this user to the database and the admin user will be able to add other users, assign restaurants/restaurant groups to other users and define roles with a specific set of permissions. By default, any admin user will have all of the following permissions enabled:

...

Info

Notes:

  • The name of the role Admin and/or the exact set of permissions for that specific role can easily be edited in the Portal based on the needs of each market. For example, it could be called ‘Master FZ’ instead.

  • Each OKTA user can access the market version of the Digital Operations Portal for the country they are assigned to, managed on OKTA via FranCountry value. For example, if the user on OKTA has FranCountry = DE, then that user can only login to Digital Operations Portal for Germany. (This is a limitation the development team will soon remove.)

Authentication with Okta

To have access and be able to authenticate to the DOP App, the user needs to have the title assigned to their Okta account. These are the current list of DOP titles.

...

:

...

These tiles should be automatically available for FZs. In case it is not, a generic IT request can be raised mentioning the Digital Operations Portal - [Brand] tile to be added. For example:

  • Could you please provide me with access to staging and production instances of the Digital Operations Portal - BK Staging & Digital Operations Portal - BK Production?

If a given user is responsible for the operations in multiple countries, after authentication the user can switch the current market (region) by clicking on the country flag in the header bar:

...

Note

If you are encountering an authorization error upon login, make sure to check the country flag on top right is pointing out to the right country.

User Change History Audit Trail

The Digital Operations Portal offers a capability to provide the audit trail for pricing and availability changes done by a given user. This capability aims to support franchisees for compliance and audit-related reporting requirements, and help troubleshoot potential issues. An overview of the capability could be seen below:

...

Info

The data retention period for the history of changes is 181 days.

Account Password Resetting (via OKTA/FRUM)

Access to the DOP is currently controlled via OKTA (access management tool). Please note that the franchisees have to approach their regional manager that have a full admin account to create OKTA IDs for them. Any OKTA account must be managed by franchisees via FRUM (Franchise Restaurant User Management). You can find more informations about how to manage users here.

If your password expires, you might run into the following issue:

...

  1. Look up the user in FRUM

  2. Reset the password

...