Administering MAGIQ Service Requests – Part One: Users, Hierarchy and Access
Following our popular overview of the Service Requests module, this two-part series goes behind the scenes for the people who keep it running.
Part One is for MAGIQ Service Requests administrators. It walks through the setup that decides who sees what, who is assigned what, and how work reaches the right people.
We’ll cover:
• Adding and maintaining users – the roles required in System Administration, and setting up matching AOF (Action Officer) and WHO (Received By) records so officers can create and be assigned requests
• Understanding the metadata hierarchy – how Divisions, Departments, Request Types and Officers link together, how adaptive selection works, and why you should always link from the bottom up
• Action Officer scenarios – what happens when an officer is linked to a Division, a Department, specific Request Types, or nothing at all
• Locking down users – using access controls to restrict contractors and external users to only the requests assigned to them
We’ll also share practical tips, like cloning existing users to save time and keeping codes consistent across records.
Whether you’re new to administering Service Requests or tightening up an existing setup, you’ll leave knowing exactly how your module fits together.
📅 Date: Thursday 29 October 2026
🕐 Time: 11:00am AEDT | 1:00pm NZDT
🔗 Register to attend the webinar here.