Accounts for Several People

Everyone who uses a Nimbus cloud computer must have an account defined.  This consists of a User Name (which must be different from all other User Names) and a Password of your choosing (which prevents everyone else from accessing your account).

Many people will just want a single account for their own use, but for many situations several people will use the Nimbus or there will be several Nimbus units in use.  For example, in a family there may be separate accounts for each parent, and additional accounts for some of the children.  In any business or organization, there will normally be several people involved and each will want their own account.

Related Nimbus accounts may be organized into a tree structure with one master account and several subordinate accounts.  The master account is financially responsible for all of the subordinate accounts and may delegate (or withhold) some authorities to the subordinate accounts.  For example, a master account may allow a subordinate account to create additional accounts, which will be considered as subordinate to that account.

Multiple Account Example

Assume a small manufacturing business with the normal departments of Administration, Sales, and Production.  Sub-departments for Accounting and HR exist within Administration.  Then the following structure of Nimbus accounts might be created:

  Business Owner
Staff 1
Staff 2
Accountant 1
Accountant 2
HR Staff 1
Sales 1
Sales 2
Sales 3
Production Staff 1
Production Staff 2
Production Staff N

Of course, each entry shown above would have a separate User Name and Password defined which would constitute the actual Nimbus cloud computer for that person.


The Business Owner has the master account.  This account must have a credit card registered and is ultimately responsible for Nimbus financial matters.

The master account issues activation keys which may be used by other staff members to setup their own accounts.  They will not need to enter credit card information, and entering the activation key authorizes their account and automatically associates it with the master account.

In addition, the master account may delegate certain authority to any of the subordinate accounts.  For example, the person who creates the Administration account may be delegated the authority to issue additional activation keys, so that they can manage the creation of new accounts for the staff in the Administration department.  Each new account is considered to be subordinate to the account which issued the activation key.

Multiple Billing Levels

The master account must always have a valid credit card registered, and all Nimbus charges will be posted to that card on a monthly basis.

However, when subordinate accounts are created with an activation code, they may also specify a credit card.  In this case, all charges for that account, and all accounts subordinate to that account, will be posted to this credit card instead of the one registered for the master account.

This allows the business to post different charges to different credit cards if desired.

In the example above, if it is desired to keep all charges for Sales and Production segregated for accounting reasons, then separate credit cards could be specified for the Sales account and the Production account.  All charges for the Sales, Sales 1, Sales 2, and Sales 3 Nimbus accounts would be posted to the Sales credit card.  All charges for Production, and all the Production Staff X accounts would be posted to the Production credit card.  Note that all Administration charges would still flow to the master credit card.