| Integration with Emory VPN |
- Mandatory
Troubleshooting Common Login Issues in Emory PeopleSoft
The Emory PeopleSoft login system is a critical tool for accessing employee and student records, payroll, and administrative services. However, users may encounter technical disruptions such as credential errors, session timeouts, or permission restrictions that impede access. This section provides structured diagnostic steps, account recovery procedures, and technical resolutions to address these challenges efficiently. Emory’s IT support resources, including the service portal and Help Desk, are integral to resolving persistent issues, with standardized workflows to minimize downtime.
Diagnostic Flowchart for Common Login Errors
Users frequently experience three primary login errors in Emory PeopleSoft: Invalid Credentials, Session Timeout, and Permission Denied. Each error requires a distinct troubleshooting approach. Below are structured flowcharts to guide users through resolution steps systematically.Error 1: Invalid Credentials -
Step 1: Verify Credentials
- Ensure the username (typically EmoryNet ID or employee ID) and password are entered correctly.
- Check for caps lock or accidental special characters (e.g., numbers/symbols mistakenly included).
- For multi-factor authentication (MFA), confirm the verification code or method (e.g., Duo Mobile push) is active.
-
Step 2: Reset Password via Emory IT Service Portal
- Navigate to Emory IT Password Reset.
- Select "PeopleSoft Login" as the service type and enter the EmoryNet ID or employee ID.
- Follow prompts to create a new password (minimum 12 characters, including uppercase, lowercase, numbers, and symbols).
- Submit required documentation:
- For employees: Supervisor verification (via email or HR portal).
- For students: Emory ID and academic record confirmation (accessible via Office of the Controller).
- Wait for IT confirmation (typically 1–4 hours for processing).
-
Step 3: Unlock Account (If Locked Due to Failed Attempts)
- Submit a ticket via Emory Help Desk with:
- Full name, EmoryNet ID, and department.
- Description of the issue (e.g., "Account locked after 5 failed login attempts").
- Supervisor or HR contact information for verification.
- Expected resolution time: Same-day unlock for verified accounts.
-
Step 4: Browser/Device-Specific Checks
- Clear cache, cookies, and temporary files (instructions provided in the next section).
- Test login on a different device or browser (e.g., Chrome, Firefox, Edge).
- Disable VPN or proxy settings if used, as they may interfere with authentication.
-
Step 5: Escalate to Help Desk
- If the issue persists, contact the Emory Help Desk with:
- Error screenshots (if applicable).
- Recent changes to credentials or device settings.
- Confirmation of MFA enrollment status.
- Escalation path: Tier 1 → Tier 2 (PeopleSoft administrators) if unresolved within 24 hours.
-
Step 1: Confirm Session Activity
- Session timeouts occur after 30 minutes of inactivity by default. Ensure the session remains active by:
- Clicking the "Stay Logged In" option (if available).
- Navigating between pages or performing actions (e.g., viewing reports) periodically.
-
Step 2: Adjust Browser Settings
- Disable aggressive power-saving modes (e.g., Chrome’s "Discard unused tabs" or Firefox’s "Close tabs to free memory").
- Enable "Do Not Track" or "Private Browsing" may trigger session resets; disable these temporarily.
-
Step 3: Server-Side Timeout Configuration
- If timeouts persist, submit a request to Emory IT to extend the session timeout for your role (requires supervisor approval for administrative access).
- Use the Access Request Portal to specify:
"Request to adjust PeopleSoft session timeout from 30 minutes to [X] minutes for [role/department]. Justification: [brief explanation]."
-
Step 4: Network Stability Check
- Unstable Wi-Fi or VPN connections may cause premature timeouts. Test with:
- Ethernet connection (wired network).
- Mobile hotspot (as a secondary test).
-
Step 1: Verify User Role and Access
- Permission errors indicate insufficient privileges for the requested module (e.g., payroll, HR, or financials).
- Consult the Access Request Portal to confirm assigned roles.
-
Step 2: Request Additional Permissions
- Submit a role modification request via the portal with:
"Request access to [specific module, e.g., 'Employee Self-Service Payroll'] for [EmoryNet ID]. Current roles: [list existing roles]. Justification: [business need]."
- Approval workflow: Typically requires supervisor + HR/Finance department sign-off.
- Processing time: 1–5 business days depending on complexity.
-
Step 3: Departmental Workarounds
- For time-sensitive tasks, delegate to a colleague with higher permissions or use a shared account (if permitted by IT policy).
- Document the limitation in the IT Ticketing System for future reference.
-
Step 4: Audit Access Logs
- If permissions were recently revoked, check the Emory IT Audit Portal for changes.
- Contact the PeopleSoft Administrator in your department for role-specific guidance.
Resetting Passwords and Unlocking Accounts
Password resets and account unlocks in Emory PeopleSoft are managed through the Emory IT Service Portal, with verification requirements varying by user type (employee, student, or contractor). Below are the standardized procedures, including documentation checks and escalation paths for delays.Password Reset Procedure Role-Based Navigation and Dashboard Customization in Emory PeopleSoft
Emory’s PeopleSoft system employs a role-based access control (RBAC) model to ensure users interact with modules and functionalities aligned with their job responsibilities. Role assignments determine menu visibility, dashboard layouts, and permission levels, optimizing efficiency while maintaining data security. Customization of the homepage and navigation further enhances productivity by prioritizing frequently accessed tools. Below, the structure of role-specific access, dashboard customization steps, and permission adjustments are detailed.
Role-Specific Access and Default Module Visibility
Roles in Emory PeopleSoft are predefined to reflect professional functions, such as "Faculty," "HR Administrator," or "Student Worker." Each role grants access to a distinct set of modules while restricting others to prevent unauthorized actions. The following table outlines the default modules available and restricted features for common roles:
| Role Type |
Default Modules Available |
Hidden/Restricted Features |
|---|
| Faculty |
- Course Management (Banner Integration)
- Student Records (View-Only)
- Time Reporting (for TA/RA hours)
- Payroll Review (salary adjustments)
- Benefits Enrollment (self-service)
|
- HR Case Management
- Recruitment Portals
- Financial Aid Disbursement
- Department Budget Adjustments
|
| HR Administrator |
- Employee Onboarding
- Time and Labor Management
- Payroll Processing
- Benefits Administration
- Performance Reviews
|
- Student Financial Aid
- Faculty Promotion Workflows
- Vendor Payments
- Research Funding Allocation
|
| Student Worker |
- Time Reporting (hours logged)
- Payroll Statements (view)
- Tax Form Submission (W-4)
- Benefits Enrollment (if eligible)
|
- HR Case Management
- Faculty Evaluation Tools
- Department Budgeting
- System Configuration
|
> "The Faculty dashboard in PeopleSoft displays a centralized view of Course Roster Management, Student Grade Submission, and Time Reporting for Teaching Assistantships as primary tiles. Secondary tiles include Payroll Adjustment Requests and Benefits Enrollment Deadlines, with quick-access links to Banner Self-Service for enrollment verification. Hidden modules, such as HR Document Processing, remain inaccessible unless explicitly granted through a permission request."
Customizing the PeopleSoft Homepage for Efficiency
Users can reorganize their PeopleSoft homepage to emphasize frequently used modules, reducing navigation steps. The following steps outline the customization process:1. Accessing the Customization Menu
Navigate to the PeopleSoft login portal and select the "My Homepage" tab. In the top-right corner, locate the gear icon (⚙️)—this triggers the layout editor. 2. Reordering Modules
Drag and drop tiles to reposition them. For example, a Time Reporting module can be moved to the top row for immediate visibility. Use the "Pin to Favorites" option to lock frequently accessed modules in place. 3. Adding/Removing Modules
Click "Add Content" to browse available modules (e.g., "Payroll Review" or "Benefits Enrollment") and select those relevant to your role. To remove unused modules, hover over a tile and select the "Remove" option. 4. Saving Changes
After adjustments, click "Save Layout" in the top-right corner. The updated homepage will apply upon the next login. Visual Guidance:
> "The gear icon appears as a small, gray cogwheel symbol. The Add Content button resembles a + sign within a box. When dragging tiles, a blue outline indicates the drop zone for rearrangement."
Requesting Additional Permissions or Role Adjustments
Access to restricted modules or role modifications requires submission through Emory’s IT Governance Workflow. The process ensures compliance with security policies while accommodating legitimate needs. Follow these steps:1. Identify Required Access
Determine the specific module or permission needed (e.g., "Department Budget Approval" for a faculty member). Verify whether the request aligns with job responsibilities to avoid delays. 2. Submit a ServiceNow Ticket
Log in to Emory’s ServiceNow portal (accessible via service.emory.edu) and create a new request under the "PeopleSoft Access" category. Provide:
- Full Name and Emory NetID
- Current Role and Department
- Requested Module/Permission
- Justification (e.g., "Requires access to Vendor Payment Approval for departmental procurement oversight")
3. IT Review and Approval
The PeopleSoft Access Team reviews requests within 3–5 business days, considering:
- Role-based necessity
- Compliance with university policies
- Potential security risks
Approved changes are implemented in the next system update cycle.4. Follow-Up
If the request is denied, the ticket will include a reason and alternative solutions (e.g., delegating tasks to an existing admin). Resubmit with additional context if needed. Example Justification for a Permission Request:
> "As the Department Chair of Biology, I require access to the Faculty Promotion Workflow module to review and approve tenure cases for my faculty members. This aligns with my administrative duties as outlined in the Emory Faculty Handbook, Section 4.2."
Security Protocols and Compliance in Emory PeopleSoft
Emory University implements rigorous security measures to safeguard sensitive employee, student, and financial data within the PeopleSoft system. These protocols align with federal regulations such as FERPA (Family Educational Rights and Privacy Act) and HIPAA (Health Insurance Portability and Accountability Act), ensuring compliance for protected health information (PHI) and personally identifiable information (PII). Below, the framework for data protection, phishing recognition, secure login practices, and single sign-on (SSO) integration is detailed to mitigate risks and maintain operational integrity. Emory’s PeopleSoft environment employs multi-layered encryption for data in transit and at rest, including AES-256 for database storage and TLS 1.2+ for secure communication channels. Audit logs track all access attempts, modifications, and administrative actions, with logs retained for seven years to support compliance audits. Role-based access controls (RBAC) restrict permissions to the principle of least privilege, while multi-factor authentication (MFA) is enforced for all login sessions. For HIPAA-covered records, additional safeguards such as data masking and access reviews are applied quarterly to ensure adherence to privacy standards.
Data Protection Measures and Compliance Standards
Emory’s PeopleSoft system adheres to NIST SP 800-53 and ISO 27001 for information security management, with specific emphasis on protecting FERPA-regulated educational records and HIPAA-governed health data. The following measures are implemented:- Encryption Standards:
- AES-256 encryption for stored data (e.g., payroll, student transcripts, medical records).
- TLS 1.3 for all external communications, with certificate validation enforced via Emory’s internal PKI (Public Key Infrastructure).
- Database-level encryption for sensitive fields (e.g., Social Security numbers, bank account details).
- Audit and Monitoring:
- SIEM (Security Information and Event Management) integration with Splunk to correlate login anomalies, failed attempts, and unusual data exports.
- Automated alerts for suspicious activities, such as multiple failed logins or access during non-business hours.
- Retention policy for audit logs: 7 years for financial/HR data, 10 years for health records (HIPAA).
- Compliance Frameworks:
- FERPA Compliance: Restricts access to student records to authorized personnel (e.g., advisors, financial aid officers) with documented "need to know."
- HIPAA Compliance: Applies to health-related data (e.g., employee medical leaves, student disability accommodations), requiring separate access tiers and business associate agreements (BAAs) for third-party vendors.
- GDPR Alignment: Extends to international users, ensuring data minimization and explicit consent for data processing.
Key Regulation Highlights:
- FERPA: Prohibits disclosure of student records without consent, except to school officials with legitimate educational interests.
- HIPAA: Mandates safeguards for PHI, including breach notification within 60 days of discovery.
- Emory Policy: All users must complete annual security training, including phishing simulations and compliance refresher courses.
Recognizing and Reporting Phishing Attempts Targeting PeopleSoft
Phishing attacks often mimic Emory’s PeopleSoft login pages or send urgent emails to exploit credential theft. Below are visual cues and red flags to identify malicious attempts, along with a step-by-step reporting process.Common Phishing Tactics and Examples:
- Fake Login Pages:
- URL Mismatches: Legitimate PeopleSoft login URLs begin with `https://ps.emory.edu` or `https://ps.emory.edu/psp/`. Phishing links may use:
- Subdomains like `emory-peopleoft-login[.]com` (note the typo).
- IP addresses (e.g., `http://192.168.1.100/pslogin`).
- Lookalike domains (e.g., `em0ry-ps[.]edu`).
- HTTPS Without Padlock: Some phishing sites use HTTPS but lack the green padlock icon or display a certificate warning in browsers.
- Form Fields: Fake pages may request unnecessary details (e.g., mother’s maiden name, pet’s name) beyond standard PeopleSoft credentials.
- Urgent or Threatening Language:
- Emails claiming:
- "Your PeopleSoft account will be locked in 24 hours unless you verify now!"
- "Unauthorized activity detected—click here to secure your account."
- "Your direct deposit was suspended; update your info immediately."
- Spoofed Sender Addresses: Emails may appear to come from `noreply@emory.edu` but reveal the true address on hover (e.g., `sender@em0ry-ps-support[.]com`).
Step-by-Step Reporting Process:
1. Do Not Click Links or Download Attachments: Hover over links to check the destination URL without clicking.
2. Forward Suspicious Emails: Send phishing attempts to phishing@emory.edu (Emory’s dedicated reporting inbox).
3. Report via IT Service Portal: Log a ticket at Emory IT Support with:
- Email headers (displayed in Outlook: View > Message > Full Header).
- Screenshot of the fake page (if accessed).
- Description of the threat (e.g., "Urgent account lockout claim").
4. Reset Credentials if Compromised: Use Emory’s password reset tool (https://password.emory.edu) to change PeopleSoft credentials if credentials were entered on a fake page.
Example of a Malicious Email:
Subject: URGENT: PeopleSoft Access Verification Required
Body:
*"Dear Employee,
Due to recent security updates, we require you to verify your PeopleSoft credentials to prevent account suspension. Click the link below to proceed:
[https://em0ry-ps-login[.]com/verify](https://em0ry-ps-login[.]com/verify)
Failure to act within 48 hours will result in temporary access revocation.
—Emory HR Team"*
Visual Cues:
- "Em0ry" typo in the URL.
- No Emory branding or logo.
- Generic salutation ("Dear Employee" instead of name).
Checklist for Secure Login Practices
Adhering to secure login habits reduces the risk of unauthorized access and data breaches. Below is a prioritized checklist for Emory PeopleSoft users, categorized by risk mitigation strategies.Credential and Device Security:
Emory recommends using a password manager (e.g., 1Password, LastPass) to generate and store complex, unique passwords for PeopleSoft. Avoid reusing passwords across systems, as credential stuffing attacks exploit compromised passwords from other breaches. - Use 12+ character passwords with a mix of uppercase, lowercase, numbers, and symbols.
- Enable Emory’s MFA (Duo Security) for all login sessions, requiring a push notification, SMS code, or hardware token after entering credentials.
- Never share credentials via email, text, or collaborative tools (e.g., Slack, Teams).
Network and Environmental Safeguards:
Public Wi-Fi networks lack encryption and are prime targets for man-in-the-middle attacks. Use Emory’s VPN (Virtual Private Network) when accessing PeopleSoft remotely to encrypt traffic. - Avoid public Wi-Fi for sensitive transactions (e.g., payroll updates, grade submissions).
- Disable Bluetooth/Wi-Fi on devices when not in use to prevent unauthorized connections.
- Use Emory’s VPN (https://vpn.emory.edu) for remote access to PeopleSoft.
Device Maintenance and Updates:
Outdated software introduces vulnerabilities that attackers exploit. Regularly update operating systems, browsers, and security tools to patch known flaws. - Update devices monthly: Enable automatic updates for Windows/macOS and mobile devices.
- Install antivirus/anti-malware: Use Emory-approved tools (e.g., CrowdStrike, Bitdefender) and keep definitions current.
- Enable firewall protections: Configure firewalls to block incoming connections and log suspicious activity.
Session and Access Management:
PeopleSoft sessions should be secured with timeout policies and device recognition to prevent session hijacking. - Log out after inactivity: PeopleSoft automatically times out after 30 minutes of inactivity; manually log out when finished.
- Recognize unusual devices: If logging in from a new location/device, verify the session via Emory’s IT Security Alerts.
- Use private/incognito browsing to avoid cached credentials
Advanced Features and Automation in Emory PeopleSoft
Emory PeopleSoft integrates self-service tools and automation capabilities to streamline administrative workflows, reduce manual intervention, and enhance data accuracy. Employees and authorized personnel can leverage these features to manage benefits, financial updates, and reporting without relying on IT support. Below are structured guidelines for utilizing self-service functionalities, automating repetitive tasks, and generating actionable reports, along with a comparative analysis of advanced features available at Emory.
PeopleSoft’s self-service modules enable users to perform critical HR and payroll-related tasks independently. Key functionalities include Benefits Enrollment and Direct Deposit Updates, each with specific deadlines and confirmation steps to ensure compliance and accuracy.Benefits Enrollment Process
- Deadlines: Enrollment periods typically align with Emory’s annual open enrollment (dates published via university email and the PeopleSoft portal). Late enrollments may incur penalties or require justification.
- Confirmation Steps:
- Submit changes by the deadline.
- Receive an automated email confirmation upon submission.
- Verify selections in the "My Benefits" dashboard within 48 hours.
- Print or save a summary for records.
- Key Considerations:
- Dependents must be added during the primary enrollment window unless qualifying for a special event.
- Changes to health plans take effect on the first day of the following month.
Direct Deposit Updates
- Deadlines: Updates must be submitted at least 7 business days before payroll processing to avoid delays.
- Confirmation Steps:
- Navigate to "Payroll and Compensation" > "Direct Deposit".
- Enter new account details (routing number, account number, bank name).
- Submit and await a confirmation email with a reference number.
- Verify the update in the "Payroll Advice" section post-processing.
Automation Scripts for Repetitive Tasks
Emory supports automation via approved APIs and integration tools, such as PeopleSoft Integration Broker (PIB) and PowerShell scripts for bulk data exports. Below is a PowerShell snippet for exporting employee compensation data to CSV, adhering to Emory’s security protocols.Prerequisites:
- Access to Emory’s PeopleSoft API Gateway (credentials provided via IT Security).
- PowerShell 7.x installed on a university-approved device.
- Required modules: `ImportExcel`, `RestSharp` (install via `Install-Module`).
Script Example: Bulk Compensation Data Export
```powershell
Define API endpoint and authentication headers
$apiUrl = "https://ps.emory.edu/api/hr/compensation/export"
$headers = @{
"Authorization" = "Bearer $env:PEOPLESOFT_API_TOKEN"
"Content-Type" = "application/json"
}# Query parameters (filter by department, fiscal year, etc.)
$queryParams = @{
department = "MED"
fiscalYear = "2024"
format = "CSV"
} # Invoke API and save response
$response = Invoke-RestMethod -Uri $apiUrl -Method Get -Headers $headers -Query $queryParams
$response | ConvertTo-Csv -Path "C:\Exports\Compensation_$(Get-Date -Format 'yyyyMMdd').csv" -NoTypeInformation # Log completion
Write-Output "Export completed at $(Get-Date). File saved to C:\Exports\."
``` Security Notes:
- Store API tokens in environment variables (`$env:PEOPLESOFT_API_TOKEN`) rather than hardcoding.
- Restrict script execution to Emory’s Virtual Private Network (VPN) or approved on-campus networks.
- Validate data integrity by cross-referencing with the "Employee Compensation Summary" report in PeopleSoft.
Generating and Interpreting PeopleSoft Reports
PeopleSoft’s reporting tools allow users to generate customizable reports (e.g., "Employee Compensation Summary") with filters for granular analysis. Reports can be exported in CSV (for analysis) or PDF (for documentation) and shared with designated roles.Steps to Generate a Report:
1. Access Reports:
- Navigate to "Reports" > "Compensation" > "Employee Compensation Summary".
2. Apply Filters:
- Department: Select "All" or specific units (e.g., "Nursing").
- Fiscal Year: Choose the relevant period (e.g., "2023-2024").
- Compensation Type: Include base salary, bonuses, or adjustments.
3. Export Formats:
- CSV: Enables data manipulation in Excel (e.g., pivot tables).
- PDF: Preserves formatting for audits or presentations.
4. Sharing Permissions:
- Use the "Share" button to distribute reports via email or the "Documents" tab.
- Restrict access to roles with "View-Only" or "Edit" permissions.
Interpreting Key Metrics:
- Base Salary: Reflects annualized compensation before adjustments.
- Year-to-Date (YTD) Earnings: Cumulative earnings from January 1 to the report date.
- Variance: Highlights discrepancies between budgeted and actual compensation (e.g., negative variance indicates over-budget spending).
Example Report Filter Configuration:
Department: "MED" | Fiscal Year: "2024" | Compensation Type: "Base + Bonuses"
Export Format: CSV | Recipients: "Department Heads" (Role-Based Access)
Comparison of Advanced Features in Emory PeopleSoft
The following table outlines Emory’s availability of advanced features, their use cases, and inherent limitations to inform strategic adoption.
| Feature |
Emory’s Availability |
Use Case |
Limitations |
|---|
| Mobile Notifications |
Available via PeopleSoft Mobile App (iOS/Android) |
- Real-time alerts for benefits enrollment deadlines.
- Payroll deposit confirmations.
- Approvals for time-off requests.
|
- Notifications require push permission enablement in app settings.
- Limited customization for alert frequency (e.g., daily digest vs. immediate).
- No SMS fallback for users without mobile access.
|
| Offline Mode |
Partial support via PeopleSoft Mobile App (cached data) |
- Viewing saved compensation statements without internet.
- Submitting time-off requests offline (syncs upon reconnection).
|
- Offline functionality limited to pre-downloaded data.
- No real-time updates or submissions without connectivity.
- Requires manual sync to resolve conflicts.
|
| API-Driven Workflows |
Supported via PeopleSoft Integration Broker (PIB) |
- Automated data feeds to ERP systems (e.g., SAP).
- Bulk exports for HR analytics (e.g., turnover rates).
- Custom integrations with third-party tools (e.g., Tableau).
|
- API access requires IT approval and role-based permissions.
- Rate limits apply (e.g., 100 requests/hour).
- Data transformation may require additional scripting (e.g., Python).
|
| Role-Based Dashboards |
Fully customizable for managers, HR, and employees |
- Managers: Team compensation analytics.
- HR: Enrollment compliance tracking.
- Employees: Personal benefits overview.
|
- Dashboard customization requires training (offered via Emory HR Tech Workshops).
- Shared dashboards may inherit permission conflicts.
- Real-time data updates depend on system refresh cycles (typically hourly).
|
Achieving complete access to Emory PeopleSoft is not merely about entering credentials; it is about understanding the interplay between security, functionality, and user-specific roles. By adhering to the technical prerequisites, troubleshooting common issues proactively, and customizing your workspace to align with your responsibilities, you can transform potential obstacles into opportunities for efficiency. Whether you are resolving a locked account, requesting additional permissions, or automating repetitive tasks, this guide equips you with the knowledge to navigate the system confidently. Emory’s investment in robust security measures underscores the importance of compliance and vigilance, ensuring that every login contributes to a secure and streamlined operational experience across the university.
|
Leave a Comment
Comments are moderated before appearing. The data you submit is processed according to the Privacy Policy of ir.msu.ac.zw.