info@firstcron.com +44 797 910 0801 +1 917 519 9016 +971 56 130 3636
FirstCron Logo

Common Strategies For Redwood Enablement

founder

By

Vaneet Gupta (8 min read)

Published July 22nd, 2025

Share this blog on

Facebook Instagram Twitter LinkedIn
Common Strategies for Redwood Enablement

Below are some Common Strategies for Redwood Enablement

1. Change Management & User Adoption

  • Most users are accustomed to the classic UI; transitioning to Redwood requires significant change communication.
  • Frontline users (social workers, HR clerks, finance officers) may not adapt easily without clear, visual training material.

2. Security & Role-Based Access Control (RBAC)

  • Redwood pages often expose data or tiles that were not visible in classic UI.
  • Defence and central government require strict alignment with IL3/IL5 or OFFICIAL-SENSITIVE security controls.
  • Roles may need redesigning to support Redwood layout-specific privileges.

3. Configuration Compatibility

  • Custom fields, extensions, and page composers may not carry over cleanly.
  • Many Redwood pages do not support personalization or extensions the way classic pages did.

4. Staggered Feature Availability

  • Not all modules are Redwood-enabled yet.
  • Finance, Procurement, and some HCM submodules have partial support.
  • Councils and MOD units often run hybrid environments that complicate UX consistency.

5. Performance Issues

  • Redwood pages rely more heavily on visual components (cards, dashboards) which can load slower in legacy networks or low-bandwidth council offices.

6. Data Privacy And Auditability

  • With new dashboards and drill-downs, Redwood may expose audit-sensitive information (e.g., payroll exceptions or disciplinary flags).
  • Need to ensure new UI doesn’t break GDPR or MOD/MoJ data governance rules.

Technical Implementation Issues

Below are som technical Implementation Issues

1. FSM Feature Opt-In Confusion

  • Redwood enablement is scattered across multiple FSM opt-ins. Not enabling the correct one(s) can lead to broken navigation or empty tiles.

2. Incomplete Page Parity

  • Some Redwood pages do not have full parity with classic—e.g., payroll run results, bulk timecard entry, person management views.
  • Councils may have to train users on both UIs temporarily.

3. Broken Integrations / BI Reports

  • BI Publisher outputs or OTBI dashboards embedded in classic pages may not render or link properly from Redwood dashboards.
  • Central government agencies often rely heavily on embedded analytics.

4. Mobile And Accessibility Gaps

  • Some Redwood pages are still not optimized for screen readers or low-vision users.
  • Public sector needs to meet WCAG 2.1 AA accessibility standards by law.

5. Missing Localizations (e.g. UK Payroll)

  • Redwood-compatible flows for UK payroll processes like RTI, FPS, or Pension outputs may not be complete.
  • Defence and council HR/payroll teams often face delays in deploying Redwood due to localization gaps.

Contact Us

Location: 78, St John Street, London UK. EC1V 4PW

Phone: +44 797 910 0801

Email: vaneet.gupta@firstcron.com

Top