The built-in functions will not do that the way they are. Each slide has only one Next and one Previous button, so you will have to create a number of triggers for it, and use conditions to decide what action to take. You will also need to keep track of which layer to close.
See the attached sample for one way you might do it. You will need to set the layer properties to show or hide content on lower layers.
I agree with Judy, you might be better served by using slides instead of layers.
Actually, I never use the built-in Previous and Next buttons, for a variety of reasons,
First, they make your course look like it came out of a cookie-cutter box, instead of being designed by an ID professional. Of course, I realize that there are some clients that don't care, and aren't willing to pay for top level design.
Secondly, Previous and Next work well if you are (re)creating a book, or have a hankering to force the learner into a linear progression through the material. Again, I realize there are clients that don't care. Government entitie, are usually just interested in forcing the learner to be in the presence of some sort of material, without regard to whether learning takes place. Many companies think that being experts at creating a certain widget makes them experts on how to teach people.
Finally, while there may always be a certain amount of material that builds on previous material, and must, therefore, be presented sequentially, maximum learning corresponds to (among other factors) the amount of choice the learner has (know in the industry as learner-centricity).
For a sample of better ways to navigate a course, see the sample at this discussion:
https://community.articulate.com/discussions/articulate-storyline/free-sample-restricted-and-free-random-navigation-using-variables-and-triggers