This view that needs a separate login account is not intended to be used very often. Usually, only at the very beginning of becoming publishing application customer, this view need to be accessed briefly so that CDN address can be set. Without it being set all the public pages' footer contain a message that mentions about missing CDN address.
It provides, among other things, the possibility to create new users and the editing of user-specific constraints. Some areas of the managing view contain just information e.g. "how much outbound transfer bandwidth has been used in the current billing cycle".
A user's project can be transferred from one user to another in this interface, but only if the catalogs of that project are not used by any other project. If this condition is not met, the project transfer will not even be started. The transfer requires as parameters the project id and the username of the user to whom the project is to be transferred. From a database point of view, such a transfer is a quick operation, since as a relational database it is not necessary to make changes in many places if the project has no image catalogs at all and if it has it is still quicly done. If a project being transferred to another user has adequatesets associated with it, these associations are removed, as the adequatesets are not intended to be transferable from one user to another, at least for the time being.
Occasionally, on rare occasions, one might choose from the normal user accounts the one that will become the main user, i.e. the one whose public solkutions will be listed when going to the domain's index page. Otherwise, a user listing would be displayed, from which one could select to see the user-specific listing of published solutions.
If necessary (highly unlikely), there's a simple button that can be used to clear the contents of long-lived caches that form in the central memories of the servers in use. Such caches include a partial copy of the database contents with relations, as it is much faster to retrieve information from them than from the database, as the database is located on a slower SSD.