Overview
The LB 2.0 New Admin Dashboard is the platform used by restaurant organizations to manage their menus, orders, locations, customers, and marketing in one place. This article explains how users with the correct role can access the dashboard.
Prerequisites & Dependencies
Access to the LB 2.0 Admin Dashboard requires an established admin account with valid credentials and access to either the ordering website or the chain-entry page. This allows the login process to connect to the platform and open the dashboard for the assigned account.
Limitations
Internal team: To log in to the Admin dashboard, we must create an account on the client's website or app, and then ask for management access via the #cx-configurations-team Slack channel.
Alternatively, we can request management access without registering via the ordering website or app. This way, the teammate providing the access will create an account directly in the client's dashboard, granting the access, and share temporary login credentials. It's important to update the password immediately, so it doesn't get compromised.
Some features that were part of the older system may still appear only in the previous Novadine Admin experience, and those items are not available in LB 2.0.
Depending on the assigned role and, primarily, role in the restaurant organization, Admin users can have different levels of access to features.
💡Learn more about the roles Operate: Management (LB 2.0)
Access the LB 2.0 New Admin Dashboard
There are two ways to access the LB 2.0 New Admin Dashboard: via ordering website or via chain entry.
Log in via the ordering website
We can access the Admin Dashboard through the restaurant’s ordering website:
Navigate to the ordering website (e.g. https://pgtest2.netlify.app/)
Log in using your Lunchbox credentials. A team member provides them, or you can request them via SIIT (for internal team). See the Limitations
Once we are logged into the website, we can see the Jump to Admin button in the top right. Select it to access the dashboard
IMPORTANT NOTE: The Jump to Admin button becomes visible only after logging in with an account with an Admin role created. No matter which role user is assigned to, if their account is listed under Operate> Management, they will be able to log into their Admin dashboard.
Log in via chain entry
Chain Entry gives direct access to the Admin Dashboard by selecting the correct tenant and domain. Here's how to do it:
Navigate to https://dashboard.lunchbox.io/chain-entry
Enter a client tenant name, which can be found in the Chain URL sheet.
The tenant name can be grabbed from the Novadine dashboard URL
The tenant name is always before .novadine or .lunchbox, e.g. https://pgtest.novadine.com/mp/nd/sites/xilan-prime/#/ so the tenant name in this case is pgtest
Choose the Lunchbox or Novadine domain, depending on what's in the URL above.
If it includes Novadine, select novadine.com from the dropdown.
If it includes Lunchbox, select lunchbox.io from the drop-down.
Additionally, with international expansion, we can select lunchbox.ca (for Canadian websites), lunchbox.uk (for United Kingdom websites) or lunchbox.dk (for Denmark websites)
Select Continue to proceed to credentials entry
Enter your email and password and select Login to access the chain dashboard
Support & Escalation Path
Internal assistance: If an internal team member has an issue with logging in or accessing the Admin dashboard, even if they have a management account created, they can post in #cx-configurations team Slack channel. If the issue cannot be resolved there, a bug ticket should be submitted for Engineering.
FAQs
Q: The Jump to Admin button is not visible. What should be done?
A: Access is available only when a user tries to log in to the ordering website using their Admin credentials. If the button is still not visible, the Chain Entry method can be used.
Q: What if the password is forgotten?
A: Use the Forgot Password link on the login page.
Q: Why does the dashboard show the wrong data?
A: The wrong tenant or domain may have been selected. Ensure that the correct environment is used support.lunchbox.io.