Select Interactive

Solution

Employee portals and intranets with a different door for every role.

Compensation and benefits, practice content, policies, people data: the information every employee needs, scoped to exactly what each of them should see. We build employee portals and intranets as real web applications with role-based access designed in from the first data model. Senior in-house. You own the code.

Talk through your rolesSee the work

Who This Is For

Who we build employee portals for

  1. HR, compensation, and benefits teams

    01

    Annual compensation statements, benefits data, and sensitive people information that managers, executives, and employees each need to see differently.

  2. Multi-practice and multi-entity firms

    02

    Accounting, legal, and advisory firms where each practice has its own content, forms, and announcements, and nobody should see the wrong ones. JTaylor runs on this.

  3. Holding companies and family offices

    03

    Several operating entities, one leadership team, and data that has to roll up for the C-suite while staying scoped for everyone else.

  4. IT and operations leaders

    04

    Teams that have outgrown a SharePoint site or a shared drive and need a system they can govern, audit, and extend.

Not for

A company wiki, a document-sharing folder, or a native mobile app. We build browser-based portals with mobile-friendly workflows, not native iOS or Android apps.

What We Build

What an employee portal has to get right

One dataset, several role-specific doors

Role is architecture, not a settings screen

The role a person holds decides the interface they get and the data it can reach. That decision lives in the data model and the API, not in a hidden menu.

  • Rees-Jones Holdings: employees see their own information, managers a team view, directors a business view, executives a leadership dashboard, HR administration, the C-suite an executive view, and IT system operations.
  • JTaylor: every employee gets practice-specific content and nothing they should not see.
Spreadsheet grid becoming a database

Sensitive data, governed

Compensation and benefits data deserves a real database with history, not a workbook with protected tabs.

  • Rees-Jones Holdings: multiple spreadsheet workflows condensed into one real-time database, with limited presentation of sensitive data per role.
  • Full change history and attributed edits, so a number and the reason it changed travel together.
One dataset, several role-specific doors

Dashboards people actually open

Live charts on the questions each role asks, rather than a monthly export someone has to format.

  • Rees-Jones Holdings: live dashboards and charts on annual compensation and benefit data, used by 150+ employee logins.
Charts and generated documents

Content and forms for each practice

Announcements, policies, resources, and internal forms scoped by practice, department, or entity, managed by the people who own them.

  • JTaylor: a firm-wide intranet in daily use by every employee for a decade, with practice-gated content.
Spreadsheet grid becoming a database

Identity, SSO, and the enterprise path

Portals sit next to the identity provider and the systems of record. We design for that from the start.

  • Role-based authentication on Firebase or your identity provider, with an activity log of user actions.
  • SSO, HR and payroll integrations, and audit requirements are covered under enterprise web development.

How We Work

How a portal engagement runs

Map the people and the data before the screens. Every portal we have built that lasted started with the role model.

Employees, managers, directors, executives, HR, leadership, IT. The exclusions matter as much as the permissions.

Compensation years, benefit elections, practice content, entities. Versioned, attributed, recoverable.

Working software in two-week slices. HR clicks the admin view, a manager clicks the team view, on a shared staging environment.

Rees-Jones Holdings launched in 2024 and adds feature enhancements each year. JTaylor has been in daily use since 2014.

Work

Portals and intranets we have shipped

See all work
Firm-wide intranet

JTaylor intranet

A firm-wide intranet in daily use by every employee at a Fort Worth accounting and advisory firm, with practice-gated content and role-based access, maintained since 2014.

View case study

10+

years in daily use

  • Practice-specific content and forms
  • Role-based access for every employee
  • Maintained and extended for a decade
Role-based internal app

MJEC

Role-based authentication on Firebase spanning an internal app and a public client tool, with an activity log and a complete audit history of every record change.

View case study

One

auth layer across two apps

  • Administrators control who can view, edit, or manage
  • Audit log of who changed what and when
  • Desktop and mobile workflows for staff
Role-scoped data

Alcon: Revenue Forecasting

Internal sales staff log in to a role-scoped view of their own products and region, with forecasts up to five years out.

Per-userdata access

View case study

Live demo

Coming soon

Role Portal: see seven roles on one dataset

An interactive demo on synthetic data: switch between employee, manager, director, executive, HR, C-suite, and IT, and watch the interface and the visible data change. Modeled on the Rees-Jones Holdings engagement without any client data.

Synthetic data. No sign-in.

Technology

A conventional stack your IT team can own

Application

  • React
  • TypeScript
  • TanStack Start
  • TanStack Router
  • TanStack Query
  • TanStack Form
  • shadcn/ui
  • Tailwind CSS
  • Zod

Identity, data, and hosting

  • Firebase Auth
  • Firestore
  • MSSQL
  • PostgreSQL
  • Nitro
  • Azure

FAQ

Questions HR and IT leaders ask

Yes. Rees-Jones Holdings has seven role types on one compensation dataset. Role decides the interface and the data, and that is designed into the architecture.

Yes. We build on Firebase Auth or integrate with your identity provider. SSO and directory sync are part of the enterprise path.

No. It is a custom web application with a real data model, role-based access, and dashboards, built in React and TypeScript, that your team owns.

Yes. The portals are browser-based with mobile-friendly workflows. We do not build native iOS or Android apps.

Every change is attributed and versioned. History is modeled in the database, not reconstructed from old spreadsheet copies.

JTaylor has been in daily use since 2014. Rees-Jones Holdings launched in 2024 and adds phases each year. Most clients keep an ongoing cadence with us.

Keep Going

Related services, industries, and reading

Services

Solutions and industries

Reading

Start A Conversation

Tell us who needs to see what.

Roles, data, and the places the current setup leaks or blocks. A technical conversation, not a pitch.

Start a conversation
All solutions