<!-- https://nuforce360.com/help/service-manager/assignments -->
# Assignments

Overview of the Service Manager Assignments screen, where you see which staff members or teams are assigned to your services.

# Assignments

The Assignments screen, under Service Manager, gives you one list of every service assignment in your account: who (a staff member or a team) is currently covering which service, in one place instead of opening each service on its own.

## What you can do here

- Scan the full list of assignments in one screen, without opening each service individually.
- Tell at a glance whether an assignment is a single person or a whole team. Team assignments carry a "Team" badge showing how many people are on that team; individual assignments show a person icon instead.
- Page through the list when you have more assignments than fit on one screen.

Each row is labeled with the name of the assigned person or team. If an assignment somehow has nobody attached, the row shows as "Unassigned" rather than a blank line.

## Related

- [Services](/help/service-manager/services)
- [Teams](/help/hr/allocations)

<!-- REVIEW NOTES (drafting agent could not verify):
  1. Could not confirm from the code whether this screen currently lets you add, edit, or remove an assignment. The row component (AssignmentCard) has edit and delete icon slots and a mobile 'add' button, but they only appear if the backend explicitly declares row actions/tools for this model, and the service.assignment model's $browser config (in ForceServiceAssignment.php) only declares displayed fields, not actions or tools. So in the current codebase this may function as a read-only overview list rather than a place to manage assignments directly.
  2. Could not confirm a search box, filters, or sortable columns appear on this specific screen. Those features in the shared list component are opt-in per model, and the service.assignment model does not declare them.
  3. The 'Service' name, 'Role', and 'Status' shown in the AssignmentCard component's code do not appear to be included in the data this screen actually receives from the backend for this model, so they likely do not display in practice even though the component supports them.
  4. Assumed the actual place to create or change an assignment for a specific service is a separate per-service assignments flow (found action names like services.assignments / services.unassign in the codebase), not this list screen, but did not locate or verify that screen's UI.
-->