ranade-oss makes ROSS loading screens behave as one

A small interface fix removes inconsistent first impressions while users move through sign-in and secure access checks.

securityworkflow

ranade-oss has consolidated ROSS's temporary full-screen loading view across the points where the application is still establishing what a user can access. That is a modest change, but it matters in a product handling sensitive legal work: the system should not briefly render one version of a page before settling on another.

  • Service startup now presents the same loading experience.
  • Signed-in areas use that same view while access is being confirmed.
  • Multi-factor authentication transitions now match the rest of the journey.

The fork keeps its existing data-access boundary, sign-in redirects, multi-factor checks and security controls intact. This is about a calmer, more reliable handoff into the product, not a change to who is authorised to see what.

Legal teams evaluating ROSS should care because dependable access flows are part of whether a secure tool feels trustworthy in daily use.

So what For firms and legal-ops teams, this is a low-risk polish change that makes secure entry points feel more consistent without changing permissions.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?