How district and organization administrators invite staff, grant only the access they need, manage pending invitations, and deactivate accounts without losing historical records.
User management controls who belongs to the district workspace and what each person can see or administer. In SocialNote, professional role, administrative privilege, school access, and account status are separate settings. Review all four whenever someone joins, changes responsibilities, transfers schools, or leaves.
District admins and organization admins can open Settings → Users. Only an organization admin can grant organization-admin access.
| Setting | What it controls | How to choose |
|---|---|---|
| Professional role | Identifies the user as a Social Worker, Counselor, Psychologist, or Intern. | Select the person’s actual working role. A professional role is not the same as administrative access. |
| District admin | Grants district-level settings and administrative workflows, including schools, users, referrals, and consent configuration. | Enable only for staff responsible for district administration. |
| Organization admin | Grants organization-wide administrative workflows and the ability to grant organization-admin access. | Reserve for the small number of people who administer the organization across districts. |
| School access | Allows all district schools or limits the user to selected schools. | Use selected schools when the person’s responsibilities do not span the district. |
| Active user | Determines whether the person is treated as active staff in SocialNote workflows and staff lists. | Leave enabled for current staff; disable during offboarding while preserving history. |
Start with standard access and the person’s assigned schools. Add district or organization administration only when the job requires it.
The invitee receives an email link to create a password. The invitation remains in Pending Invitations until it is accepted, cancelled, or expires. Invitation links expire after seven days.
The email becomes the user’s sign-in identity. SocialNote will not create an invitation for an email that already belongs to a user or already has a pending invitation.
Jordan Rivera is a counselor assigned only to Springfield High School. Jordan will document and coordinate student support but will not manage district settings.
| Field | Example entry | Reason |
|---|---|---|
| Name | Jordan Rivera | Use the name staff and students will recognize. |
| jordan.rivera@springfield.edu | Use the person’s verified work address. | |
| Professional role | Counselor | Matches Jordan’s role rather than treating “admin” as a profession. |
| District admin | Off | Jordan does not configure district settings. |
| Organization admin | Off | Jordan does not administer multiple districts or grant organization access. |
| School access | Selected schools | Jordan’s responsibilities are limited to one school. |
| Selected school | Springfield High School | Provides the minimum school scope required for the job. |
After sending the invitation, confirm that Jordan appears in Pending Invitations with the Counselor role, standard privileges, one-school access, the correct inviter, and the expected expiration date.
Select an invitee in the Pending Invitations table to review the invitation’s status, role, privileges, school access, sender, and expiration.
| Action | When to use it | What happens |
|---|---|---|
| Edit Invitation | Correct a name, email, role, privilege, or school assignment before acceptance. | The pending invitation is updated. Changing the email automatically sends a new invitation link. |
| Resend Invitation | The invitee did not receive the message or the link is near expiration. | A new link is sent with a fresh seven-day expiration; the prior link no longer works. |
| Cancel Invitation | The invitation was sent in error or the person should no longer join. | The invitation leaves the pending list and its acceptance link can no longer be used. |
A district admin may resend an organization-admin invitation, but only an organization admin can edit or cancel that invitation.
Use this workflow when a person changes roles, gains or loses administrative responsibilities, or transfers between schools. An administrator cannot deactivate their own account or remove their own admin privileges from this form, which helps prevent accidental self-lockout.
When a staff member leaves or no longer uses SocialNote, deactivate the user. SocialNote’s district user settings do not provide a delete action, and deactivation is the preferred approach because it preserves the person’s historical authorship, service records, assignments, and reporting context.
Those records explain what support was delivered and who documented it. Preserve them, transfer current responsibility, and use inactive status for the former staff member.
Inactive users remain in the district’s Users table. If a person returns, select the user, open Edit User, review their role and school access, turn on Active user, and save.
Do not send a second invitation to the same email. Reactivate the existing record so the person’s identity and historical work remain connected.
District and organization administrators should review the user list on a predictable schedule and whenever staffing changes occur.