Divine Charles · Fullstack Product EngineerLoading
000%
Getting things ready…

(W/03 · F/04) · Case study

Office & team hierarchy

Loans, savings, users, and transactions respect which office you sit in, and team settings got easier to run.

01

The problem

Lenders with many offices saw mixed branch data. Lists mixed offices. Team settings were hard to use. Parent offices needed to see child offices without showing the whole company to everyone.

02

The story

National lenders run many branches. What you see in admin should depend on your office, and managers above you still need a clear view of the offices below them.

03

What changed

Lists of loans, savings, users, and transactions filter by office. A parent office can reach people in offices under it without dumping the whole company into one flat list. Team settings make office mapping clearer.

04

How it was built

Offices were treated as a real structure, not a label. Branch staff see their branch first. Managers keep oversight without erasing that structure. Team settings were cleaned up so people are not guessing which office a person belongs to.

05

Outcome

  • Branch staff see their branch’s work first.
  • Parent offices keep oversight without mixing every office together.
  • Team settings match how lenders organize people.