Sets – An area to store particular Ingredients, Recipes and Menus.
Group – Used to group various or multiple Sets and Suppliers together.
UserGroup – The permission a user has within a particular Group.
Groups dictate what information a User can see and may also reflect business hierarchy, including:
- Any and / or applicable Suppliers for a Brand or Organization, must be attributed at Group level
- The Ingredient, Recipe and Menu Sets visible to the Group
- Groups can be used to give Supplier access to the system and limit them to only their own ingredients
- Groups are used to export data applicable to that group (e.g. Exports to Inventory, or API feeds to EPoS and other 3rd party companies such as Ten Kites)
At Group level, the following can be entered:
- Default currency
- Default language
- Target GP %
Please Note: Other fields are present, but the above are either mandatory, or more commonly used.
A Group structure may be simple for a single brand / small to medium business, where sites share most or all of the same ingredients and recipes, see Fig.1
Fig.1 - Group Structure
An Organization which has different Suppliers, Ingredients, Recipes etc. for different brands or regions may opt for a more complex structure, see Fig.2
Fig.2 - Complex Group Structure
A Set can be defined as a collection of data. In the case of RME, Ingredient, Recipe and Menu data.
Different Set types can be made available:
The same record can exist in multiple live sets, but may not exist in both a Live and Archive set at the same time.
It is not necessary to replicate / mirror the Sets to the Groups, unless each Group should see different Ingredients, Recipes and Menus.
Commonly, a ‘Core’ Set would be created which all sites / brands would have access to. Further sets can be created which can be specific and exclusive to that particular Group.
The same set can be used in multiple or all groups as required.
Dependent on which Group you have accessed as a user, this will dictate which Ingredient, Recipe or Menu information is available to the user, unless all sets are assigned to that Group.
Simple Group Vs Set Structure
The tables below show an example of a more complex Group vs Set structure, where products and recipes may differ within an organization.
Where Sets in Groups will determine what information a User has access to, the Usergroups will dictate what permissions they have when it comes to interacting with that data.
Multiple (e.g. Hierarchy of permissions) Usergroups can be assigned to a group.
However, there is a 1:1 relationship between Groups and a particular Usergroup. A usergroup cannot be linked to multiple Groups.
There are two Usergroup types available, Standard and Recipe Menu Viewer.
Three different Permission Usergroups have been created and sit within the Live Group. A separate Archive Admin Usergroup has been created to access the Archive Group and associated sets.
Groups can represent different brands and permission can be different depending on each Usergroup within.
One User should be set up per person. If different access / permissions are required, then multiple Usergroups should be assigned to that user.
A typical example of Users attached to one or many Usergroups.
Overall Example Flow