Using Active Directory Federation Services for Single Sign On with Snap Schedule 365 ERA

IMPORTANT: All information in the following screenshots contain sample data that should be replaced with information specific to your ADFS configuration. Example server: Windows Server 2012 R2 w/ ADFS 3.0 @ adfs.ad.snapschedule.com How it works: Employees use employee codes and passwords to log in to Snap Schedule 365. However, your company policies may require these users…

Using Active Directory Federation Services for Single Sign On with Snap Schedule 365

IMPORTANT: The information in the following screenshots contains sample data that should be replaced with information specific to your ADFS configuration. Example server: Windows Server 2012 R2 w/ ADFS 3.0 @ adfs.ad.snapschedule.com How it works: Schedulers enter user names and passwords to log in to Snap Schedule 365. However, your company policies may require these users…

March Maintenance Update

The development team at Snap Schedule released a maintenance update to Snap Schedule 365 last night that included fixes to the following issues: Contact Information was missing from Employee property pages when invoked from within a report.  While no data was ever lost in this scenario, the contact information was not being displayed if the…