When new simulation is created, there are few nodes in the node database - master data service node, server nodes, anonymous node also called anonymous account, and one administrator client node also called administrator account. In this state, no clients can connect to the simulation, because they don't have their own account.

Newly installed massiv client knows information just about master data service node and anonymous account (this information are stored in a file massiv.server_nodes.conf) Client connects to the master data service using anonymous account and downloads data necessary for connecting to the simulation (including node database). Node database is managed by master data service and is stored as necessary data object. In this state, client knows all server nodes, but it doesn't have account for connecting to the simulation.

Client sends a request to create account to the master data service, master data service sends a request to some server node to create special object called account object (see chapter special objects), after that master data service saves new client account to the node database, updates data and distributes them to massiv servers. In this state, server knows the client and it can successfuly connect to the simulation.

	Note
	When account creation request is sent from a client, it takes awhile till server nodes update their data with actualized node database. This time can be a few tens of seconds in a case of automatic account management, or more (days) in a case of manual account management, see account manager settings.