<!-- https://nuforce360.com/help/business-manager/contact-groups -->
# Contact Groups

How to create, nest, edit, and delete the contact groups you use to organize contacts in NuForce.

# Contact Groups

This screen lets you create and manage the groups you use to organize your contacts, so you can sort customers or accounts into named groups and pick one when you set up a contact.

## What you can do here

- See every contact group for your business in a list, showing its name and, if it sits inside another group, the parent group under "Under".
- Add a new group with the New Group button, giving it a Name and, optionally, a Description.
- Nest a group under an existing top-level group by setting "For" to that parent when creating or editing it. Leave it unset to keep the group at the top level.
- Edit an existing group's name, parent group, or description using the Edit action on its row.
- Delete a group you no longer need using the Delete action. You are asked to confirm before it is removed.
- Group names must be unique among your contact groups. If you reuse a name already in use, you are asked to pick a different one.

Once a group exists, you assign a contact to it from the contact's own record, where the group shows up as the Folder field.

## Steps

1. Click New Group at the top of the list.
2. Enter a Name for the group.
3. Optional: set "For" if this group should sit under an existing top-level group.
4. Optional: add a Description.
5. Click Save.

To change a group later, click Edit on its row, update the fields, and click Save. To remove one, click Delete and confirm.

## Related

- /help/business-manager/contacts
- /help/business-manager/organization/labels
- /help/business-manager/organization/categories

<!-- REVIEW NOTES (drafting agent could not verify):
  1. The screen may block deleting certain protected/system groups (the underlying model has a 'locked' flag that prevents deletion), but it's unclear whether any default groups of this specific type are ever locked in practice, so this was left out of the article rather than asserted.
  2. The three '## Related' help paths are inferred from sibling app routes (contacts, organization/labels, organization/categories) and were not verified against an actual help-center content structure, since none was found in the repo.
  3. Nesting appears limited to one level (a group can only be placed under a top-level group, not under another sub-group), based on how the parent-selection dropdown is populated; this wasn't tested in a running instance.
-->
