v0.1.74 — Fixing the Company Root Redirect

Overview

Release v0.1.74 is a targeted bug fix that corrects the routing behaviour at the /:company entry point. Prior to this release, visiting /:company rendered a welcome dashboard. It now correctly redirects authenticated users to /:company/accounts/, matching the original CompanySpecificHomeView specification.

Background

The myProp portal is structured around company-namespaced routes (e.g. /acme/accounts, /acme/jobs). The /:company path is the root of that namespace. According to the CompanySpecificHomeView spec, this path is purely an entry point — not a content page — and its job is simply to get the user to the right destination as quickly as possible.

The intended flow is:

Step	Responsibility	Handled by
1	Verify the company exists and apply its theme	Company layout
2	If unauthenticated, redirect to sign-in	Company layout (auth gate)
3	If authenticated, redirect to /:company/accounts/	Page component

Steps 1 and 2 were already handled by the company layout. Step 3 — the redirect to the accounts list — was missing. Instead, the page rendered a welcome message and a grid of quick-access cards (Accounts, Maintenance Jobs, Documents, Messages).

What Changed

File: src/app/[company]/page.tsx

The entire welcome dashboard UI was removed and replaced with a single server-side redirect:

// Before (simplified)
export default async function CompanyPage({ params }) {
  const { company } = await params;
  const session = await auth();

  return (
    <div>
      <h1>Welcome{session?.user?.name ? `, ${session.user.name}` : ""}</h1>
      {/* Quick-access cards: Accounts, Jobs, Documents, Messages */}
    </div>
  );
}

// After
import { redirect } from "next/navigation";

export default async function CompanyPage({ params }) {
  const { company } = await params;
  redirect(`/${company}/accounts`);
}

Because the company layout guarantees the user is authenticated before the page component runs, no additional auth check is needed in the page itself.

Impact

• Users navigating to the company root (e.g. https://portal.example.com/acme) are immediately sent to their accounts list (/acme/accounts) rather than seeing an intermediate welcome screen.
• No new features are introduced — this is a corrective fix to restore intended behaviour.
• No configuration changes are required for agencies or deployments.