Delegate department permissions by group and personnel role Audience: Department administrators, Managing members, Department trainers Find the department permission table Open the department name menu and choose Security and Permissions. The resulting Security and Permissions page contains a table of individual permissions. Read the Permission, Note and Selection columns together before changing a row. Group Only and Roles provide additional scope where offered. This lesson uses a fictional training department so we can compare a saved delegation with its original setting. Practice: Open Security & Permissions and identify the Permission, Note, Selection, Group Only and Roles columns. Read the administrator scope for adding users Find Who can Add Users. Its current selection is Department Admins. The note explains that department administrators and the managing member can add users by default, and that group administrators can be allowed to add users only to the group they administer. Read that scope before delegating this task. A station or community-response team may need local roster administration without receiving every department-wide responsibility. Practice: Read the complete Add Users note and describe the group boundary it states. Delegate one permission and verify the saved value For the practice change, set Who can Add Users to Department and Group Admins. This control saves when its selection changes. Reload the page and confirm that the same selection returns. Who can Remove Users still shows Department Admins. These are separate decisions: giving a group administrator permission to add a member does not change the remove-users selection. No person is created or removed in this exercise. Practice: In a training department, change Add Users, reload, and compare the separate Remove Users selection. Restore the practice setting deliberately Return Who can Add Users to Department Admins when the practice comparison is complete. After another reload, the original selection is visible again. Use this same readback habit when making an intended departmental change: confirm the exact row and returned value. Record who should own the task before delegating it, and review that decision when personnel or group responsibilities change. Practice: Restore the intended Add Users value and verify it after reloading. Choose a permission mode and a specific role Scroll to Who can Create Trainings. The starting selection is Department Admins with No Roles beside it. Choose Department Admins and Select Roles, then open Select roles. This training roster offers named choices including Rescue Technician and Paramedic. Select Rescue Technician for the example and read the resulting Rescue Technician tag beside the permission. This chooses a role for this particular permission; it does not demonstrate changing a member’s role assignment or promoting anyone to department administrator. Practice: Inspect the offered role names and select an appropriate practice role for this permission only. Check the final permission mode after practice After the role-selection exercise, remove the practice selection and return Who can Create Trainings to Department Admins. The final view shows that mode and No Roles again. Compare both pieces, because a permission mode and its selected roles are separate parts of the configuration. Our demonstration restores the training baseline. For a real training coordinator, retain only the delegation your department has actually decided to use. Practice: Verify both the intended training-permission mode and its role selection after practice. Read location visibility and group scope together The location rows separate Who can see the Location of Personnel from Who can see the Location of Units. Both pictured selections are Everyone. The personnel-location note explains the Group Only option for limiting group administrators and roles to a group. Read the row’s selection and scope together rather than treating the checkbox as the entire permission. These controls address who may see locations; this view does not establish that a device is currently reporting its position. Practice: Read the personnel and unit location rows and explain the Group Only note before changing location visibility. Plan the login check and departmental responsibilities Return to the note above the Security and Permissions table. It says changes take effect on the next login to the Resgrid web application. After an intended change, plan a normal login and check with the affected authorized account. Our screenshots verify saved settings, not that second-account test. A security company, search-and-rescue team, community paramedicine or mental health service, wildland contractor, industrial response team, or fire and E M S department can use these controls to match administration to actual responsibilities. Practice: Identify the affected role or group administrator and plan a next-login permission check for your department. Examples for your department Fire / EMS: Review station administrator scope without granting every department responsibility. Community response: Match community paramedicine or mental health team administration to assigned responsibilities. Search and rescue: Review a rescue-training role and group scope before assigning administration. Security: Delegate local roster work to a group supervisor while deciding removal authority separately. Wildland: Review contractor group administration and location visibility separately. Industrial: Separate team roster administration from training and location permissions.