I suspect this can't be done exactly how you describe. Parameters can be entered into Power Query and used to drive queries, but that's only within the query editor. Unless you allow the end user to access the PBIX itself, they won't be able to edit the query. Any filters etc. within the published report will only affect the data already delivered by the query, not cause it to be re-queried.
Assuming you don't want users accessing the raw data itself, you could set up your query(s) pointing to the base data and a separate query pointing to a shared 'parameter' file that they can amend and save. By merging queries you can use the parameter query to drive the output of the data query.
An alternative which isn't really what you look like you want could be to create various versions of your report with the difference being the parameters the users could use. But this would be impractical unless you are dealing with a minimal number of parameters or they have a small range of values.
Alternatively, you could set up a variety of bookmarks with preset combinations of filters that would equate to the same thing. Though beyond a handful of bookmarks this could too be impractical if you are trying to offer a large range of parameters and/or the parameters have a large number of available values.
But no, you can't use the Power BI service/published reports to send parameters to the PQ queries in your PBIX dynamically.
