The map of every 'group' in FreeITSM Ed's observation: there are multiple concepts called group and it is not clear which is which. This is the catalogue, written from a sweep of the schema rather than from memory. Three reusable groups of people (team, learning group, people group), and a matrix of which consumer accepts which. The headline finding is an asymmetry nobody has reconciled: you cannot give a knowledge folder to a learning group, and you cannot assign a course to a team. Also documented, because they are easy to trip over: - per-record member lists (CAB, task Involved, war room, watchtower) -- the right shape, because each carries per-membership state - process_groups is a coloured BOX on a diagram; morningChecks_Groups is a group of CHECKS. Neither contains people. - 'department' means three unrelated things: the routing table, a free text HR attribute on analysts and users, and the RFP builder's own list
LMS: training for portal users, and people groups Four new pages -- a user guide and a developer guide for each of: People Groups the shared groups on Tickets -> Users Training for Portal Users the four assignment targets, what a portal user sees, deadlines, and reminder emails The developer guides carry the parts that would otherwise be rediscovered: the (learner_type, learner_id) key and why nullable was not enough, the three silent traps in the db_verify migration, the two-identities-in-one- session problem and the as=portal fix, and why knowledge_user_groups must not be renamed. Corrected in passing: LMS.md opened by saying courses are 'assigned to learning groups, taken by analysts', which stopped being true; its assignments section and key-tables list are updated with it. Self-Service Portal gains a Training section. Sidebar updated.