# Manage Users

Manage Users allows administrators to create, edit, and manage user accounts for your organization. Each user account includes personal information, unit and program area assignments, viewable and editable permissions, role flags, and other configuration options.

**Permission required:** User manager.

## Getting Started

To access the Users panel, click the **cog icon** in the top navigation bar, select **Organization Settings**, then choose **People & Access → Users**. The list view displays all users in your organization with options to search, filter, and add new users.

![Screenshot: The Manage Users list page showing a table of users with columns for name, email, unit, program area, active status, and role flags](/files/uU55q3mZoJrEXhHr1OjO)

## List View

The user list displays columns for name, email, unit, program area, active status, and role flags. You can search by first name, last name, or email address, and sort by name, email, unit, program area, or active status.

### Filters

Use the filter sidebar to narrow results:

* **Is Active** — Show active or inactive users
* **Unit** — Filter by Extension Unit
* **Program Area** — Filter by program area
* **User Groups** — Filter by role assignment
* **Is Supervisor** — Filter by supervisor status
* **Is Beta User** — Filter by beta user status

## Add a User

Click **Add User** to create a new user account.

{% stepper %}
{% step %}
**Enter Account Information**

* **Username** — Enter a unique username. *(This field is only shown for certain organizations. Otherwise, the email address is used as the username.)*
* **Email** — Enter the user's email address. This must be unique within your organization.
* **First Name** — Required.
* **Last Name** — Required.

{% hint style="info" %}
**TIP:** If the email address matches an existing event-only user in the system, PEARS will automatically convert that account to a full user account.
{% endhint %}
{% endstep %}

{% step %}
**Assign Unit and Program Area**

* **Unit** — Select the user's Extension Unit.
* **Program Area** — Select the user's primary program area. *(Only shown if your organization uses program areas.)*
  {% endstep %}

{% step %}
**Configure Viewable Permissions**

These fields control what data the user can see beyond their own records:

* **Viewable Units** — The user can view records from the selected units.
* **Viewable Program Areas** — The user can view records from the selected program areas. *(Only shown if your organization uses program areas.)*
* **Viewable Users** — The user can view all records where the selected users are creator or collaborator.
  {% endstep %}

{% step %}
**Configure Editable Users**

* **Editable Users** — Select which users this person is allowed to edit. This is typically used for supervisors or administrators who need to manage other users' accounts.
  {% endstep %}

{% step %}
**Set Supervisor and Position**

* **Supervisor** — Select this user's supervisor. The supervisor relationship is used in performance reviews and other workflows.
* **Position** — Select the user's position in the organization.
* **Department** — Enter or select the user's department.
  {% endstep %}

{% step %}
**Assign Role Flags**

Role flags determine which modules and features the user can access:

* **SNAP-Ed User** — Grants access to SNAP-Ed modules including Program Activities, PSE Site Activities, Social Marketing Campaigns, Indirect Activities, Partnerships, Coalitions, Success Stories, Surveys, Reports, and Exports.
* **Extension User** — Grants access to Extension modules including Action Plans, Quarterly Efforts, Direct Contacts, Community Relationships, Professional Development, Performance Reviews, and all SNAP-Ed modules.
* **Event Creator** — Grants access to Community Events and the ability to create new events. *(Only shown if the Events module is enabled.)*

{% hint style="warning" %}
**NOTE:** If your organization uses both SNAP-Ed and Extension, each user must be assigned at least one of these roles.
{% endhint %}
{% endstep %}

{% step %}
**Set Additional Options**

* **Time Zone** — Select the user's timezone. Defaults to your organization's timezone.
* **Active** — Whether the user account is active. Deactivating a user removes all role assignments.
* **Notes** — Optional internal notes about the user.
  {% endstep %}

{% step %}
**Save**

Click **Save** to create the user account.

{% hint style="warning" %}
**NOTE:** If the user has a supervisor and position assigned, and your organization has an active performance review plan, PEARS may automatically create performance review objects for the user. A confirmation dialog will appear before saving.
{% endhint %}
{% endstep %}
{% endstepper %}

## Program Area Members (Extension Only)

For organizations using Extension, an additional **Program Area Members** section appears below the user form. This section assigns users to program area roles for specific reporting periods.

Each program area member entry includes:

* **Program Area** — The program area assignment
* **Role** — The user's role (e.g., Leader, Member, Consultant, Follower)
* **Reporting Period** — The reporting period for this assignment

Only current and future reporting periods are shown. A user can only have one role per program area per reporting period.

## Edit a User

From the list view, click a user's name to open the edit form. The edit page also displays:

* **Last Login** — When the user last logged in
* **Recent Actions** — The user's most recent activity in PEARS
* **Current Roles** — The user's assigned role flags

All fields can be updated. Changes to the supervisor or position may trigger performance review updates.

## Mark a User Account Inactive

To deactivate a user account, open the user's edit page and uncheck the **Active** checkbox, then click **Save**.

When an account is marked as inactive:

* The staff member can no longer log in to PEARS.
* All data created by the user remains intact.
* Other users can continue to view, edit, and analyze the inactive user's data.

To reactivate an account, re-check the **Active** checkbox and reassign any necessary roles.

{% hint style="warning" %}
**NOTE:** Deactivating a user account removes all of their role assignments and group memberships. You must reactivate the user and reassign their roles to restore access.
{% endhint %}

## Export User Account Data

User Managers and Organization Administrators can export user account data to an Excel file.

1. From the Manage Users list view, use the filters and search to include all necessary users.
2. Click the **Export** button.
3. An Excel file downloads containing:
   * **Codebook** — Export metadata including who exported, timestamp, filters applied, and field descriptions.
   * **User Data** — User ID, username, email, unit, department, program area, position, permissions, and record counts.
   * **Program Area Team Members** (Extension only) — Staff distribution and roles across program areas.
   * **Quarterly Effort Report Checkup** (Extension only) — Completion status for quarterly effort records.

{% hint style="warning" %}
**NOTE:** The user account export is only available for Organization Administrators and User Managers.
{% endhint %}

## Manage Program Area Teams (Extension Only)

For organizations using Extension, the **Program Area Team Members** section on each user's edit page assigns users to program area roles for specific reporting periods.

Each assignment includes three interdependent fields:

* **Program Area** — The program area assignment.
* **Role** — The user's role: Member, Leader, Consultant, or Follower.
* **Reporting Period** — The reporting period for this assignment.

All three fields must be completed together or left entirely blank. Use the **plus icon** to assign multiple roles and the **minus icon** to remove assignments. Program Area Team Leaders for the current year appear in the PEARS Directory.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://support.pears.io/administration/administration/manage-users.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.