Skip to main content

Managing Jobs

Jobs are the titles assigned to staff members — for example, Head Coach, Assistant Coach, Physio, or Manager. In SportsPress, "Jobs" is the user-facing label for the `sp_role` taxonomy.

Updated today

Managing Jobs

Jobs are the titles assigned to staff members — for example, Head Coach, Assistant Coach, Physio, or Manager. In SportsPress, "Jobs" is the user-facing label for the sp_role taxonomy.

Important distinction: Jobs are staff title designations only. They have no connection to WordPress user roles, which control login access and permissions.

Accessing the Jobs Screen

Navigate to Staff → Jobs to see the full list of job terms. The screen uses the standard WordPress taxonomy interface with a form on the left and a table on the right.

Creating a Job

  1. In the Add New Job panel on the left, enter a Name (e.g. "Head Coach").

  2. The Slug field auto-populates from the name. Edit it if you need a custom URL-friendly identifier.

  3. Click Add New Job to save.

The new job immediately appears in the table on the right and becomes available in the Jobs selector on all staff edit screens.

Editing a Job

Click the job's name or the Edit link to open the full edit form, where you can change the Name and Slug. Click Update to save.

Deleting a Job

Hover over a job name in the table and click Delete. Deleting a job removes the taxonomy term but does not delete the staff members assigned to it — those staff members simply lose that job assignment.

How Jobs Are Used

  • Staff edit screen — The Jobs multi-select field in the Details meta box assigns one or more jobs to a staff member. The selected jobs appear before the staff member's name in list directories.

  • Staff Directories filter — When creating or editing a Staff Directory, the Job field in the Details sidebar filters the directory to show only staff with that job assignment.

  • Staff list screen — The Job column in the Staff list table displays the assigned jobs for each staff member.

  • REST API — Jobs are accessible via the sp_role taxonomy terms endpoint.

Did this answer your question?