1. Open native settings
Modules/TaskManagement/Lookups/HRF_TASK_MANAGEMENT_SETTINGS.aspx checks exact ADMINISTRATOR membership. It reads/writes existing TaskManagement / General values and binds employee, manager and HR report configuration. Record current values before an authorised change and verify ordinary access afterward.
Module availability also depends on licence and TasksEnabled. The personal route is Modules/TaskManagement/Pages/HRF_TASK_DASHBOARD.aspx. Manager and HR planning use HRF_TASK_MANAGER_DASHBOARD.aspx and HRF_TASK_HR_DASHBOARD.aspx under the same folder, with native scope retained.
2. Set actual workspace and planning controls
| Control or prerequisite | Use and boundary |
|---|---|
| TasksEnabled | Module option. Native page saves TRUE or FALSE. |
| EnableModernWorkspace | Refreshed personal workspace option; saves 1 or 0. |
| EnableModernPlanning EnableManagerPlanning | Manager planning adds a gate to modern planning. |
| EnableCapacityInsights EnableCertifiedAvailability | Capacity depends on planning; certified availability adds its gate. |
| EnableTaskKnowledge EnableTaskBlockers EnableProjectConfiguration EnableTaskInvoiceTracking | Existing optional capabilities with additional rights/prerequisites. |
| PlanningWipAdvisoryLimit | Advisory work-in-progress signal, not an enforced maximum. |
| TaskBlockerReasonCodes TaskInvoiceAccessGroupIds | Blocker choices and invoice access groups. Verify the intended audience. |
Settings expose capabilities; they do not grant every project or employee right. Do not enable features just to reproduce a screenshot.
3. Respect project and notification boundaries
Modules/TaskManagement/Pages/HRF_TASK_PROJECT_CONFIGURATION.aspx requires one exact enabled EnableProjectConfiguration setting row and a valid user-bound session ticket. Available projects are active, non-template, non-personal, manageable by the user and owned or administered by that user.
| Control or prerequisite | Use and boundary |
|---|---|
| Project configuration | Use the native route and profile choices. A URL or module option does not grant management rights. |
| Notifications | ENABLE_TASK_MANAGEMENT_NOTIFICATIONS and individual NOTIFICATION_TASK_* options govern configured events. Task changes can have outbound effects. |
| Rating and recurrence | Existing controls include AllowTaskClosingWithoutRating, RateRecurringTasks, QualitativeRatingItemCount, QualitativeRatingPrecision and RatingTypeDefaultValue. |
| Time and board | DefaultStartTime, DefaultEndTime and MaxNumberOfTasksOnBoardStatus are existing controls. Validate intended behaviour. |
A settings save does not prove dispatch, recurrence, rating or financial processing. Those require focused authorised operational tests.
4. Verify configuration and documents
- Check module/feature gates as ordinary employee, intended manager and HR.
- Verify matching scope and denied project access before broad planning use.
- Open a permitted task/document through native navigation, then verify expected denial.
- Test saves, recurrence, notifications and finance separately with explicit authorisation.
- Inspect actual report/export files for correct task scope.
- Retain prior values for authorised native rollback after a regression.
Newer local evidence supersedes the older blanket Task 52 hold: six successful reads over two personas, native PDF delivery and cross-task/unknown-document denial were recorded on 20 October. Target concurrency and native business writes remain unproven. No application, settings, SQL or database mutations occurred for these companions.