Customization that only changes a logo
Most workforce tools call their theming 'branded' when it is just a color picker.
Business themes
Practical branding for the real admin and employee shell.
Brand the real product shell. Theme Workbench tunes light and dark tokens, typography, surfaces, radii, and density — applied to the live admin and employee surfaces, not a sample.
Evaluation focus
branded workforce app themes
- custom theme workforce platform
- white label employee app
- branded admin dashboard
- design tokens for workforce app
- Factory presets plus capped custom themes
- Brand kit fields with logo, color, and typography
- Readability checks and destructive-change confirmations
Theme Workbench
Theme Workbench · Brand kit
Slate
Forest
Sand
Ember
Light surface
Dark surface
Generated layout — synthetic demo data.
Who it is for
- Operators rolling Yrka out under their own brand
- Multi-brand operators managing themes across locations
- Marketing/ops leads tuning the employee experience
Built for these realities
The pain we hear from operators
Each pain point reflects real conversations with SMB operators evaluating workforce tools today. Yrka is shaped around these realities, not generic feature checklists.
Themes disconnected from the actual surfaces
Preview screens that do not match the real admin shell hide readability problems.
Unlimited custom themes that create chaos
No caps and no readability checks turn theme management into a support burden.
How teams use it
Use cases we ship for today
These are the moments this surface is built around. They map to shipped product behavior and the launch scope for this area.
Apply a brand kit
Factory presets and capped custom themes apply to the actual admin and employee surfaces.
Light + dark mode parity
Live shell preview keeps light/dark tokens, typography, and density visible in context.
Guarded customization
Custom themes are capped, checked for readability, and managed with destructive confirmations.
Why Yrka here
What makes this different
Differentiators map to shipped product behavior. They are the reasons buyers pick this surface after comparing alternatives.
Built into operations
Theme changes apply to the real admin and employee shells, not a disconnected sample.
Capped and checked
Custom themes intentionally have caps and readability checks to keep rollout coherent.
Brand kit fields with tokens
Brand fields plus light/dark tokens make themes portable across locations.
How it flows
A workflow that mirrors how operators actually run the day
Three steps, three responsibilities.
- 01
Pick
Start from a factory preset or open a capped custom theme slot.
- 02
Tune
Adjust brand kit fields, tokens, radius, and density with a live preview of the product shell.
- 03
Apply
Confirm destructive changes, snap to readability checks, and roll the theme out organization-wide.
What's inside
Business themes highlights
Tokens, not classes
Edit light/dark token values — the entire product shell adapts.
Density and radius
Shell geometry tuning to match the operational rhythm your team prefers.
Readability checks
Contrast and legibility validation before a theme can be applied.
Capped custom slots
Custom themes are intentionally limited; factory presets stay available as a trusted baseline.
Destructive confirmations
Major changes require confirmation so themes don't silently break legibility.
Brand kit fields
Logo, color, and typography fields apply wherever brand belongs in the product.
Built into operations
Theme changes apply to the actual admin and employee surfaces. Operators can tune rollout branding without sending tickets to product design.
Guarded customization
Custom themes are intentionally capped, validated for contrast, and managed with destructive confirmations so changes never silently break legibility.
Scope
What's included, what's intentionally out of scope
Yrka maps every feature to its product claim so commercial conversations stay honest.
Included
- Factory presets
- Capped custom themes
- Light and dark token editing
- Admin shell preview
Boundaries
- Unlimited theme slots
- Unreviewed destructive theme changes
- Custom design agency services by default
Related
Where this fits in the platform
Resources
Company knowledge that asks for acknowledgement.
Publish handbook pages, organize collections, require acknowledgements, prepare approved sources, and answer questions over ready records.
ExploreCommunications
Messages, boards, and follow-up that match the workflow.
Direct messages, board announcements, app notifications, and review-required inbox work — each distinct, all connected to the operations they belong to.
ExploreTrust and security
Real controls. Honest scope. Customer in charge.
Supabase auth, organization scoping, row level security, role checks, private file storage, signed URLs, audit events, AI boundaries, and operations runbooks — described as built, not as promised.
ExploreQuestions
Common buyer questions
We surface the questions buyers actually ask — trial, support, export, mobile, payroll, provider, AI, and trust scope — in plain language.
How does the trial work?
Start with a 30-day card-required trial. Cancel anytime from the Stripe customer portal. Workspaces stay available for export or reactivation for 30 days after paid access ends.
Does Yrka process payroll or file taxes?
No. Yrka covers time tracking, scheduling, payroll-prep exports, and provider handoff. Customers stay in charge of payroll processing, tax filing, legal, and HR decisions.
What does mobile look like?
Responsive web and an installable PWA cover employee time entry, scheduling, resources, tasks, messages, and profile review. Employees see scoped offline read context plus queued supported writes with clear sync states.
Can we export our data?
Yes. Payroll-prep exports, schedule and time reports, and employee data exports are part of the core product. Customer data remains exportable for 30 days after paid access ends unless an earlier deletion is requested.
Ready to run the day on Yrka?
Start a 30-day trial in minutes, or book a working session to walk through the rollout with someone who has done this before.