OWFR Credentials Request: Communications Team Guide

1

What This Plugin Does

The Credentials Request plugin adds a green button to any page. When clicked, it opens a branded modal popup with a short contact form. Visitors use this form to request login credentials for password-protected areas of the OWFR website.

There are two versions of the form:

Primary Care Resources (PCR) - for physicians, nurse practitioners, and other primary care providers requesting access to the Primary Care Resources section.
Lived Experience Partner (LEP) - for patients, caregivers, and community advocates requesting access to the Lived Experience Partner resources.

When a visitor submits the form, the request is saved directly to the WordPress database. No email configuration is required. Staff review all incoming requests from the Access Requests menu in the WP Admin sidebar, then manually create credentials and follow up with the requester.

This plugin does not automatically create WordPress user accounts. It captures and stores the request for staff to review and action manually.

2

How It Works

Visitor experience

1
Visitor sees the buttonA green pill-shaped button (e.g. "Request Access") appears on the page wherever the shortcode is placed.
2
Visitor clicks the buttonA modal popup slides over the page with the request form.
3
Visitor fills in the formFirst name, last name, organization, role/title, and email are required. Phone and additional notes are optional.
4
Visitor submitsThe request is saved to the database. The modal shows a green checkmark and "Request Sent!" message.

Staff experience

1
Log into WP AdminGo to Access Requests in the left sidebar. New requests are highlighted with a badge count.
2
Review the requestThe table shows the date, type (PCR or LEP), name, organization, role, email, phone, and any notes. Use the filter tabs to view only New or only LEP/PCR requests.
3
Create credentials manuallyGo to WordPress → Users → Add New, create the account, and email the login details to the requester using the email address shown in the table.
4
Mark as reviewedClick Mark Reviewed on the request row to update its status. Optionally delete entries you no longer need.

3

Shortcode Reference

Add the shortcode to any Divi Code Module, page, or text widget.

Shortcode	Use Case
`[owfr_request_credentials]`	Default PCR button - "Request Primary Care Resources Access"
`[owfr_request_credentials type="lep"]`	LEP button - "Request Lived Experience Partner Access"
`[owfr_request_credentials label="Request Access"]`	Custom button label text
`[owfr_request_credentials type="lep" label="Apply for LEP Access"]`	LEP form with custom label

You can place both shortcodes on the same page - for example, one PCR button and one LEP button. Each gets a unique ID automatically to avoid conflicts.

All shortcode attributes

Attribute	Values	Default	Description
`type`	`pcr` or `lep`	`pcr`	Which form variant to show. Changes the title, subtitle, role label, and email subject.
`label`	Any text	See below	Text shown on the trigger button.
`title`	Any text	See below	Heading inside the modal.
`subtitle`	Any text	See below	Paragraph text below the modal heading.
`role_label`	Any text	See below	Label for the role/title field.
`role_placeholder`	Any text	See below	Placeholder text inside the role field.

Default text for `type="pcr"`

Button label: Request Access
Modal title: Request Primary Care Resources Access
Role label: Role / Title
Role placeholder: e.g. Family Physician, Nurse Practitioner

Default text for `type="lep"`

Button label: Request Access
Modal title: Request Lived Experience Partner Access
Role label: Role in Community
Role placeholder: e.g. Patient, Caregiver, Community Advocate

4

Form Fields

First Name Required

Requester's given name.

Last Name Required

Requester's family name.

Organization Required

The clinic, organization, or group the requester belongs to.

Role / Title Required

Job title or role. Label and placeholder text differ between PCR and LEP variants.

Email Required

Used as the Reply-To address on the notification email sent to staff.

Phone Optional

Phone number for follow-up if needed.

Additional Notes Optional

Free-text field for any extra context the requester wants to include.

5

Viewing Requests in WP Admin

All submissions are stored in the WordPress database and viewable at WP Admin → Access Requests. No email or external service is needed.

The requests table

Each row shows:

Date - when the request was submitted
Type - PCR (green badge) or LEP (purple badge)
Name - first and last name
Organization - clinic or group
Role - job title or community role
Email - clickable mailto link for easy follow-up
Phone - if provided
Notes - any additional context from the requester
Status - New (amber) or Reviewed (green)

Filter tabs

Use the tabs above the table to filter the view:

Tab	Shows
All	Every request regardless of type or status
New	Only requests not yet marked as reviewed
Reviewed	Only requests that have been marked as reviewed
PCR only	Primary Care Resources requests only
LEP only	Lived Experience Partner requests only

Row actions

Action	What it does
Mark Reviewed	Changes the status from New to Reviewed. Appears only on New rows. Use this after you have created the credentials and followed up with the requester.
Delete	Permanently removes the row from the database. A confirmation prompt appears before deletion.

A badge counter next to Access Requests in the sidebar shows how many unreviewed (New) requests are waiting. It disappears once all requests are marked as reviewed.

Only users with the Editor role or higher can view and manage the Access Requests page.

6

Where to Place the Button

The shortcode can go anywhere on the website. Recommended placements:

Primary Care Resources page - next to the login prompt or at the top of the page for users who don't yet have credentials.
Lived Experience Partner page - beside the partner portal login.
Homepage or footer - as a secondary call-to-action for new partners.

Adding to a Divi Code Module

In the Divi Builder, add or edit a Code Module.
Paste the shortcode: [owfr_request_credentials]
Save the module and publish/update the page.

Do not paste the shortcode inside a Text Module - use a Code Module only. Text Modules can add extra HTML tags that break the button layout.

7

Troubleshooting

Problem	Likely Cause	Fix
Button appears but modal doesn't open	JavaScript conflict with another plugin or Divi module	Check the browser console for JS errors. Ensure the shortcode is in a Code Module, not a Text Module.
Modal opens but appears behind other content	Divi stacking context issue (unlikely - the modal is appended to `<body>`)	Contact the development team. The plugin already uses a body-append fix for Divi z-index conflicts.
Form submits but request doesn't appear in Access Requests	Database table not yet created	Deactivate and re-activate the plugin in WP Admin → Plugins. The table is created automatically on re-activation.
"Access Requests" menu not visible in WP Admin	Logged in as a user role below Editor	Only Editor-level users and above can see the Access Requests menu. Log in as an Editor or Administrator.
"Security check failed" error on submit	Page was open for a very long time before submitting (nonce expired)	Ask the user to refresh the page and try again.
Divi editor fails to save after activating	Corrupt plugin file (UTF-8 BOM)	Re-upload the plugin file. Ensure the PHP file is saved as UTF-8 without BOM.

Credentials Request

Table of Contents

What This Plugin Does

How It Works

Visitor experience

Staff experience

Shortcode Reference

All shortcode attributes

Default text for type="pcr"

Default text for type="lep"

Form Fields

Viewing Requests in WP Admin

The requests table

Filter tabs

Row actions

Where to Place the Button

Adding to a Divi Code Module

Troubleshooting

Default text for `type="pcr"`

Default text for `type="lep"`