Both of the above approaches are indeed correct based on the premise that you want to truly restrict access to the underlying data such that each end user can only see the data for, in this case, their region.
If instead you want something that’s more like a default filter, where the user can explore all of the data, but when they load the page they are only shown what’s in their region, there are ways to accomplish this as well.
In Workshop, you can create a string variable backed by a Multipass property of the current user:
If the regional information you need is actually a property on their account, then you can maybe access it directly as a custom property. Otherwise you’ll need to use the username or id to retrieve the information from wherever you have it available.
The pattern I use most often relies on having a Object Type that models employees or platform users with a property for their Multipass username, but you can also do this with a Typescript function that accesses the User object and reads of the relevant properties from their user profile or from some other source.