The following configuration is required for widgets:
Name | Description |
---|---|
Dayforce Wallet |
Employees need role feature access to the Eligible for Dayforce Wallet and Eligible for On-Demand Pay features under Application Container > People > Employee Profile > Employment > Employment Settings > Dayforce Wallet in the Features tab of System Admin > Roles. |
Employee Balance |
Widget access is based on employees having balances assigned to them. If employees have no balances, Dayforce doesn’t display the widget. No role feature access is required for employees to view their own balances so, if the balances widget is added to a hub, Dayforce displays the widget for any role that employees have. Note: Accessing the link to the form to book time off from the widget requires feature role access to Work > Time Away List. |
Employee Earnings | Employees require role feature access to Earnings in the Features tab of System Admin > Roles. |
Favorites | Employees require role feature access for the features that the widget displays. |
Featured Links |
Employees require role feature access for the Dayforce features that the widget displays. Files and external links: No role feature or access authorization is required for files and external links, so if an employee has access to a hub, they have access to all files and links that are added to that hub. Forms and guided processes: Configuration in Workflow Administration > Role Privileges determines which forms and guided processes are visible to employees. Note: Experience Hub excludes any items where the form name or workflow is blank. |
My Team |
Employees require role feature access to People in Application Container in the Features tab of System Admin > Roles, and need at least one direct report. Note: If a manager has two roles, for example, an employee role and a manager role, if their employee role also has access to the People feature, they will see My Team in their employee role. Some of the widget functionality might not work under their employee role (depending on configuration), but Dayforce displays the widget itself and its contents. |
Onboarding - Employee Summary |
Employees must be in their active onboarding period. They require role feature access to Getting Started in the Features tab of System Admin > Roles. |
Onboarding - Manager Summary |
Employees require role feature access to Onboarding > Onboarding Employees in the Features tab of System Admin > Roles. |
Pending Actions |
No role feature access is required for the Pending Actions widget. If a user role is assigned to a hub that has the widget, end users will see it. The widget doesn’t show in Hub to employees who have a terminated status. |
Quick Links |
Employees require role feature access for the Dayforce features that the widget displays. Files and external links: No role feature or access authorization is required for files and external links, so if an employee has access to a hub, they have access to all files and links that are added to that hub. Forms and guided processes: Configuration in Workflow Administration > Role Privileges determines which forms and guided processes are visible to employees. Note: Experience Hub excludes any items where the form name or workflow is blank. |
Rich Text Editor | No role feature access is required for the Rich Text Editor widget. |
Time Clock |
Employees require role feature access to Work > Time Clock in the Features tab of System Admin > Roles. Additionally, depending on how an employee’s time entry policy is configured, some clock entry options might be unavailable in the widget. For example, if an employee’s time entry policy doesn’t support meal breaks, the Start Meal and End Meal clock entry options won’t appear in the widget. See “Time Entry Policies” in the Dayforce Implementation Guide. |