Depending on what exactly you need to have saved the save function might be a bit overkill. I never really used it but iirc it acts like a snapshot of the entire current gamestate (like the one you can make in the debugger) that saves pretty much everything, unless you specifically give it the "no save" behavior.
construct.net/en/tutorials/savegames-11
construct.net/en/make-games/manuals/construct-3/behavior-reference/no-save
In your case you only want to save money (number) and a list of levels that are either locked or unlocked (Array) so what you can do is use local storage and just save/load the data. This will also make your saves much smaller, since you only save exactly what you really need.