The Class data hierarchy consists of different levels:
Community Level Data
This refers to all data held by Class which is pushed to all businesses on Class. It includes all listed security investments which are created and updated by Class daily with information including prices, income and asset allocation. Another example is Auto Transactions Rules which are created for interest or bank fees for certain banks where the description is always the same, saving you the time from needing to create these transaction rules at the fund level.
Business Level Data
Within the Community lies each Business. A Business refers to any single accounting firm/financial planner/administrator. Each business will be set up with an Access Controller who can create manage and remove user login credentials to access Class. An example of business-level data is modifying the asset allocation of listed security (which is normally community-level data). By modifying community-level security it becomes business-level and the change will apply to all entities that use that security code.
Brand Level Data
Within each Business lies one or more Brands. A Brand is used for grouping funds and the majority of businesses on Class will just have one brand but those that have more than one can use brands to apply different default contacts and settings.
Fund Level Data
This refers to data held at an individual Fund level. Most of the end data entered into Class will be at a Fund level e.g. member and transaction date, this applies uniquely to the entity.
The Relevance of the Hierarchy
The hierarchy in Class is important for things like settings, default contacts and parcel match allocation.
The lower levels (e.g. Fund) always take precedence over all other levels on Class as per below. This means that if you make a contact a default at the business level but change it at the fund level then the fund level contact will overwrite the business level for that fund only.
Learn about the different Business Level Menus.