Skip to main content
All Docs
FeaturesmyProp (AgentOS People Portal)Updated April 4, 2026

Legacy AgentOS Route Redirects

Legacy AgentOS Route Redirects

Overview

During the migration from the original AgentOS portal to the new myProp /accounts/* URL structure, all six account-type routes were renamed. Any link that an agency previously shared with a client — via email, SMS, or other channels — using the old route patterns would resolve to a 404 error.

As of v0.1.52, permanent (301) redirects are in place for all legacy route patterns. Existing shared links continue to route clients to the correct page automatically.

Redirect Mappings

Legacy Route (AgentOS)New Route (myProp)
/:company/LettingsTenant/:id/:company/accounts/tenant/:id
/:company/LettingsLandlord/:id/:company/accounts/landlord/:id
/:company/LettingsProspect/:id/:company/accounts/tenant/:id/prospect
/:company/SalesVendor/:id/:company/accounts/vendor/:id
/:company/SalesApplicantBuyer/:id/:company/accounts/buyer/:id
/:company/MaintenanceContractor/:id/:company/accounts/contractor/:id

/:company is the agency's unique slug (e.g. letmcletting) and :id is the client's account identifier.

Behaviour

  • Redirect type: 301 Permanent — browsers and search engines update their records to the new URL.
  • Processing layer: Handled by Next.js at the routing layer, before any page code executes. There is no additional runtime overhead.
  • Transparency: The redirect is invisible to the end user — they land on the correct page without any error or intermediate screen.

Example

A tenant who received a link like:

https://portal.myprop.app/letmcletting/LettingsTenant/abc123

will be automatically redirected to:

https://portal.myprop.app/letmcletting/accounts/tenant/abc123

Implementation

Redirects are defined in next.config.ts using the Next.js redirects() configuration:

// next.config.ts
const nextConfig: NextConfig = {
  async redirects() {
    return [
      {
        source: "/:company/LettingsTenant/:id",
        destination: "/:company/accounts/tenant/:id",
        permanent: true,
      },
      {
        source: "/:company/LettingsLandlord/:id",
        destination: "/:company/accounts/landlord/:id",
        permanent: true,
      },
      {
        source: "/:company/LettingsProspect/:id",
        destination: "/:company/accounts/tenant/:id/prospect",
        permanent: true,
      },
      {
        source: "/:company/SalesVendor/:id",
        destination: "/:company/accounts/vendor/:id",
        permanent: true,
      },
      {
        source: "/:company/SalesApplicantBuyer/:id",
        destination: "/:company/accounts/buyer/:id",
        permanent: true,
      },
      {
        source: "/:company/MaintenanceContractor/:id",
        destination: "/:company/accounts/contractor/:id",
        permanent: true,
      },
    ];
  },
};

No Action Required

Agencies do not need to resend links or update their templates. All previously shared links resolve correctly. However, it is recommended that any new links shared going forward use the current /accounts/* URL structure.