Basically, it may seem like what I'm saying is complicated gobbledy-beloved patriot, but think of it in LAYERS.
Outermost layer: Public IPv4 address provided by ISP - AAA.BBB.CCC.DDD
First router layer: WAN IPv4 as assigned by ISP, using DHCP most likely, could be static. AAA.BBB.CCC.DDD, LAN IP address designated in settings, usually but not always, 192.168.1.1 or .0.1.
Second router layer: WAN IPv4 address assigned by first router's LAN DHCP, so something in the 192.168.1.x range, could be set dynamic (DHCP), or static, LAN IP address needs to be on a different subnet than first router, so LAN IP would be 192.168.16.1, with a DHCP pool set to 192.168.16.50-100, say.
Then the PCs that you connect to your secondary router, will get IP addresses assigned (using DHCP) from the secondary router's LAN IPv4 range (DHCP pool), such as 192.168.16.54.
Note that if there are other PCs connected to the first router layer (primary Fios router), then they can still be accessed via IP address, from PCs behind your secondary router, but those PCs on the primary router, will not be allowed to connect inward to PCs connected to your secondary router.
If you want to have two isolated LANs (more or less), hanging off of the FIOS router, than you would want two secondary routers hanging off of it, LAN A and LAN B. Give them different local LAN IP subnet ranges.
With that configuration, if you wanted a shared NAS or ethernet-based printer, you could connect it directly to the Fios / primary router, and still have access to those network devices, from PCs behind both secondary routers. So you could set up a shared printer, for example, if two offices wanted to split the cost on a big shared networked office printer, for example.