Use case:
As a developer using Studio to upgrade a "full" Realm to a "reference" Realm, and then immediately open the Realm I would expect it to contain all the Permission classes/Roles/Users associated with being a Query-based Realm.

Problem:
Depending on your perspective, the problem is in one of two locations:

1) In ROS

As upgrading from Full to Reference just involves calling PATCH /files/:realmpath and the server logic is very limited. See https://github.com/realm/realm-object-server-private/issues/1337

2) In Studio

Right now we open Reference Realms in "Full" mode, which means it bypasses all Query-based logic which would otherwise create permission classes and users.

This is confusing as a developer as this does not match the behavior of Query-based Realms that is otherwise described in our docs. It also makes bootstrapping difficult as you are required to go through some binding code to actually trigger the generation of the initial permission data.

It is unclear if this can be fixed with the current API's available in JS (probably not), but then we need to figure out which API's to add to make this possible.

Also, we need to consider the fact that some might want to open a Reference Realm without triggering Query-based modifications, but it is unclear how important this use case is.

See https://realmio.slack.com/archives/CA3ET33NU/p1542119589018500