Hi @ChrisB,
I’ve had a look at your setup and can see than you’ve created state-based workgroups. Which is a very most common configuration. There’s one more thing you need to do to make this setup work, which is to define ‘Default Workgroup’ rules to ensure that NSW work is routed to your NSW workgroup, Vic work to your Vic workgroup etc.
Out of the box, only the ‘Primary Default Workgroup’ has a rule attached to it. And that rule is a “catch-all” (all jurisdictions, all roles, with or without Financial Settlement). When creating a workspace, PEXA checks whether the user is a member of the workgroup that matches the parameters of the workspace being created. In your case, the NSW Caveat workspace matched with the catch-all ‘Primary Default Workgroup’ (because there are no other rules defined). As the user wasn’t a member of the ‘Primary Default Workgroup’, they were shown the error and prevented from creating the workspace.
We’ve built PEXA this way to ensure a hard separation between the workgroups (teams). Users that are members of your NSW workgroup shouldn’t be able to create Vic workspaces, and vice versa. (If they do need to, then they can be added to both workgroups.)
So all you need to do now is define default rules for each workgroup. You can do this by going to Administrator Tools -> Manage Workgroups -> Manage Default Workgroups -> Add Rule.
Example:
(Where you have multiple workgroups for a particular state, use the Role and Financial Settlement parameters to differentiate between them.)
Once set up in this way you’ll also notice that workspace invitations will route to the appropriate workgroups, and only users of those workgroups will be able to view and accept them.
I hope my answer is helpful. We’ve built a lot of smarts into the workgroup functionality, but by doing so have made it a bit complex and therefore tough to understand. We’re looking at how we can make it a bit simpler.
Martin Karpowicz
Product Owner, Practitioner Service
PEXA