Overview
Personal URLs (PURLs) allow staff members to get credit for applications that are created on the member flow. If an applicant uses the regular application link and the application is auto approved, Glide's teller ID would appear in the core for any created by/employee fields.
With Personal URLs, staff get their own link/QR code that corresponds with their teller ID and branch. When applicants use this link/QR code on their personal devices, the staff member helping them will get credit automatically as the staff members teller id/branch will be posted to the core.
Using Personal URLs
Locating the Personal URL link
Navigate to the Settings page and locate your name in the Members and roles table. Your Personal URL will appear in the "Personal URL" column.
Viewing the QR Code
To copy or download the QR code, click on the kebab menu for your row in the "Members and roles" table. Then, click "Open QR code." You'll now be able to copy or download the QR code.
How Personal URLs Work
How does the Personal URL link know what branch to send to the core?
The branch that a staff member has selected in the top left of the Glide dashboard at the time of application start will be branch sent to the core.
What happens if an applicant uses a link from an employee that has been removed from the Glide dashboard?
If a staff member is removed from the dashboard, the default branch and Glide's Teller ID will be used similar to the behavior of a regular member application without the PURL link.
What happens if an application uses a Personal URL link, then goes into a pending queue, and a different staff member approves the application?
While applications using Personal URL links will be automatically assigned to the respective staff member, a different staff member is still able to approve the application. In this case, Glide will send the information for staff member that approves the application to the core.
Core Mapping
When an application using a Personal URL is approves, Glide will send the corresponding branch and Teller ID to the core.
Jack Henry Symitar
Teller ID will be put into the "Created by" fields at all levels
Branch will be put into the "Created at Branch" and "Branch" fields at all levels
Fiserv XP2
Teller ID will be put into Operator ID custom field on all levels
Branch will be put into the branch field on all levels
Corelation Keystone
Teller ID (User serial number) will be sent to the "Opened by User" field on the membership and share level
Branch will be sent on the share level