{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":40240,"path":"platform-administration/user-administration/t_CreateAGroup.md","title":"Create a user group","bundle":null,"doc_type":null,"release":"australia","body":"\n# Create a user group\n\nCreate groups and assign roles to them. Users assigned to the group inherit the roles.\n\n## Before you begin\n\nRole required: user\\_admin\n\n## Procedure\n\n1. Navigate to **All** > **User Administration** > **Groups**.\n\n2. Select **New**.\n\n3. On the form, fill in the fields.\n\n Some fields appear after personalizing the form. [Personalize a form](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/t_PersonalizeAForm.md).\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nName\n\n\n\nName of the group.\n\n
\n\nManager\n\n\n\nGroup manager or lead.\n\n
\n\nType\n\n\n\nCategory for this group. For example, a group designated as type **catalog** is a service catalog group and can also be accessed under the **Service Catalog** > **Catalog Policy** > **Fulfillment Groups** module. See [Configure assignment group types](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/user-administration/c_ConfigGroupTypesForAssignGroups.md) for more information.You may need to [Personalize a form](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/t_PersonalizeAForm.md) to add the **Type** field. Activating the Work Management plugin adds the **Type** field automatically.\n\n**Note:** ITIL is added for groups with an empty group type. Also, the default reference qualifier for tasks enables these groups to assign tasks and other task types to the group.\n\n
\n\nGroup email\n\n\n\nGroup email distribution list or the email address of the point of contact, such as the group manager.\n\n
\n\nParent\n\n\n\nOther group of which this group is a member. If a group has a parent, the child group inherits the roles of the parent group. The members of the child group aren’t members of the parent group. For example, if an incident is assigned to the parent group and you select the **Assigned to** lookup icon, only the members in the parent group are available. The members of the child group aren’t available.\n\n
\n\nActive\n\n\n\nCheck box that indicates whether the group is active or inactive. Inactive groups still appear in any reference field that already references the group, but aren’t visible by non-admin users in:- lists of groups\n- the reference lookup list for reference fields\n- the auto-complete list of groups displayed when you type into a reference field\n\n\n
\n\nExclude manager\n\n\n\nCheck box that controls whether the group manager receives email notifications.\n\n
\n\nInclude members\n\n\n\nCheck box that controls whether the group members receive individual emails when someone sends an email to the **Group Email** address. The only exception to this functionality is for approval notifications, whereby all members of a group receive an approval notification, regardless of the **Include members** selection. See [Receive notifications](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/build-workflows/c_ReceiveNotifications.md) for more information.\n\n
\n\nDescription\n\n\n\nHelpful information about the group.\n\n
4. Remove or hide a group.\n\n 1. **Note:** Only users in the hidden group are able to see the hidden group when selecting a group in a reference field.\n\n Create a true/false field labeled `Hidden` on the Group form.\n\n For more information on creating fields, see [Add and customize a field in a table](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/t_CreatingNewFields.md)\n\n The system creates a field called **u\\_hidden** on the **Users \\[sys\\_user\\_group\\]** table and enables use of the **Hidden** check box to designate a hidden group.\n\n 2. Create a new before query business rule on the \\[sys\\_user\\_group\\] \\(Group\\) table with the following script:\n\n ```\n if (!gs.hasRole(\"admin\") && !gs.hasRole(\"groups_admin\") && gs.getSession().isInteractive()) { \n var qc = current.addQuery(\"u_hidden\", \"!=\", \"true\"); //cannot see hidden groups... \n qc.addOrCondition(\"sys_id\", \"javascript:getMyGroups()\"); //...unless in the hidden group \n }\n ```\n\n **Note:** For more information, see [Before Query business rules](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-security/bp-before-query-business-rules.md).\n\n\n## Result\n\nThe user group is created based on the configuration that you've provided.\n\n**Note:**\n\nWhen `glide.ui.schedule_job_for_group_parent_change` is set to true, removing a parent group results in the roles of the parent group being added to the child group asynchronously. If `glide.ui.schedule_job_for_group_parent_change` is set to false, the roles of the parent group are added to the child group synchronously when the parent group is removed.\n\n**Parent Topic:**[Creating groups](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/platform-administration/user-administration/ua-creating-groups.md)\n\n"}}