What it does
The Assign page pushes a requirement from your library to an individual, a group, or a program, with an optional due date. Each affected person gets it on their personal checklist with an incomplete status.
Who it's for
Institution administrators, program administrators, and coordinators in the institution or administration portal.
How it works
The page offers three assignment tabs:
Individual — search for one person and assign the requirement to them.
Group — pick one of your groups. The requirement is assigned to every group member.
By Program — the requirement is assigned to everyone in your current program.
For each assignment you choose the Requirement, the target (user, group, or program), and an optional Due Date, then select Assign Requirement. It starts incomplete and appears immediately on the assignee's checklist. Summary cards at the top show total assignments, pending review, approved, and how many requirement definitions are available.
Group and By Program create every member's assignment in one batch, so a cohort gets the same requirement and due date together. Individual assigns to one person at a time.
Before you start
You need permission to assign requirements in the institution or administration portal.
The requirement you want must already exist in the library — this page does not create new requirement definitions.
For the Individual or Group tab, know the person or group you're assigning to. For By Program, select the right program in the header first.
Do this
Open the Assign page (
/requirements/assign) → you should see the summary cards and the Individual, Group, and By Program tabs.Select the tab that matches your audience → the panel below the tab shows the fields for that audience.
Choose a Requirement from the dropdown → you should see its type shown below the field.
Fill in the target field for that tab — a user for Individual, a group for Group, or confirm the program shown for By Program.
Set the Due Date field if you need one, then select Assign Requirement → you should see a confirmation toast and the target's due status update.
You're done when
✓ You saw the "Requirement assigned" confirmation toast.
✓ The assignment shows as incomplete on the assignee's personal checklist.
✓ The Total Assignments count on this page reflects the new assignment.
Boundaries and limits
You can only assign requirements that already exist in your library. The Assign page does not create new requirement definitions.
The due date is optional. Without one, the assignment never shows as overdue.
This page sets a due date only, not an expiration date — expiration is a submission-time detail, entered by the assignee or configured on the requirement definition.
Individual assigns to one person per action; use Group or By Program for many people in one batch.
Assigning to a group or program is a one-time action. It does not create a standing rule that auto-assigns people who join later.
The page lives in the institution and administration portals. Assignees manage their side from the personal portal.
Common questions
Q: What status does a new assignment start in? A: Incomplete. It moves to pending review when the person submits, and then to approved or rejected after review — or to completed directly for requirement types that do not require approval.
Q: Can I assign one requirement to a whole cohort at once? A: Yes. Use the Group or By Program tab — every member gets the same requirement and due date in one batch.
Q: Should I assign requirements individually or use a packet? A: Use direct assignment for a single requirement. When people need a set of requirements together — onboarding, renewals, clearances — build a packet so the whole checklist is generated at once.
Related articles