and I quote, "Customer tenants to permit master tenants to access their user accounts: Earlier, master tenants could log into a customer tenant without any permissions from the customer tenant. Rollbase 3.1 onward, the administrator of a customer tenant must manually permit master tenant users to access its environment for a specified duration."

You have posted to a forum that requires a moderator to approve posts before they are publicly available.

>> A user with a single Progress ID can now belong to multiple teams, and

This is applicable to Rollbase Mobile. i.e., a single Progress Pacific ID that is used in one Private Cloud instance for working with mobile features can be
used in

-Other private instances (installations in other system)

-Same Progress Pacific ID can be used for both OE-Mobile and Rollbase Mobile usage

-Single Progress Pacific ID can be used across different customers.

>> users can be logged into the same app from multiple browsers/devices.

This is also applicable for Rollbase Mobile. i.e., multiple users can simultaneously access the Rollbase backend through Rollbase mobile app from dissimilar
places (say Emulator, different devices and hosted environments).

Earlier, master tenants could log into a customer tenant without any permissions from the customer tenant. Rollbase 3.1 onward, the administrator
of a customer tenant must manually permit master tenant users to access its environment for a specified duration.

For more information about permitting administrative users to access a customer tenant accounts, see
Enabling an administrative user to log into a customer tenant.

Enabling an administrative user to log into a customer tenant

The administrator of a customer tenant can allow master tenant users to access it's environment for a specified duration. Typically, if a customer tenant requires that
the master users troubleshoot a problem in its account, the customer tenant gives access to the master users for them to rectify the problem. After getting the access, the master user can access the customer details page and log into the customer tenant. For
more information about how master users log into a customer tenant, see Working with Customer Records.

To enable a master tenant to log into a customer tenant:

1.
From the customer tenant environment, as an administrative user, select
Setup Home from the list of applications:

2.
Under the
Administration Setup options, select
Support Access.

The
Support Access page appears.

3. 1.
Click
Edit to modify the support access settings
in your tenant.

4. 2.
Select
Enable to allow master users to access
and log into all the users in your customer tenant.

5. 3.
Specify, in the
Give Access for field, the duration for
which you want to grant the access.

and I quote, "Customer tenants to permit master tenants to access their user accounts: Earlier, master tenants could log into a customer tenant without any permissions from the customer tenant.
Rollbase 3.1 onward, the administrator of a customer tenant must manually permit master tenant users to access its environment for a specified duration."

To view and work with
Customer record details, Rollbase administrators of the master tenant can do the following:

1. Navigate to the
System Console:

2. Select the
Customers tab.

3. In the Customers List area, click the
Customer Name.

4. Do any of the following operations:

View Logs:
View log files associated with this customer, which can be useful for troubleshooting and debugging. Requires view permission

Login:
Log into a customer tenant as a Super-Admin (invisible user with full access). This option requires log in permission. The button only appears after the administrative user of the customer tenant enables access for the master tenant users. For more information
about enabling support access, see Enabling
an administrative user to log into a customer tenant.

Edit:
Modify the customer record. Requires edit permission.

Delete:
Delete the customer record and all customer's data. Requires delete permission.

From the
More Actions drop-down menu, the following are available:

Login
As: Log into a customer tenant as a particular user. This option requires log in permission. The button only appears after the administrative user of the customer tenant enables
access for the master tenant users. For more information about enabling support access, see
Enabling
an administrative user to log into a customer tenant.

Data Maintenance:
Use this procedure to restore the integrity of relationships for this customer. This is only for fixing problems and will not be used under normal conditions. Requires edit permission.

System
Backup: Monitor and create backup files created in this customer. Requires view permission.

Restore
from backup: (from Backup page) Use the
Restore option to delete all current customer data and replace it with data imported from the
selected backup file (no users can be logged in during backup). Requires edit permission.

Database
Move: Moves customer data to another (selected) database. Requires edit permission. Additionally, after performing
Database Move, you must navigate to the customer's details page, under
Runtime Information area, select
Load to load the customer tenant from the production server cache.

You unload and load the customer tenant for the new settings to take effect. Only after loading the customer tenant from the production server cache can the users log into the customer
tenant.