Permissions

outline each user on your merchant portal can be given a role that controls which parts of the portal they can access this lets you give your warehouse team access to returns without exposing invoices, or give your finance team invoices without settings access permissions are set per store the same person can have different access levels across different merchant portals roles when adding or editing a user, you can select one of the following role presets admin full access to everything returns only dashboard, return details, and return processing analyst analytics and reporting finance invoices and reporting custom pick the exact access yourself access options each role is made up of the following access options, which you can also tick individually returns dashboard, return details, and return processing analytics analytics overview and analytics sub pages invoices invoice viewing and downloads reporting reports, exports, and reporting schedules settings admin settings pages, integrations, and user management role presets pre select these options for you if you manually change any option, the role switches to custom how it works users only see the pages they have access to anything else is hidden from their sidebar when a user logs in, they land on the first page they can access only users with settings admin access can add, edit, or delete users editing a user's access go to settings > users click the edit icon next to the user change their role or access options and click save changes default store each user can also be given a default store one of your drop off locations docid\ okielfbgggkcqy1mf3buo when that user opens the in store lodgement flow ( refundid pos docid 3zbl0tuu6w6cqdiupgkbj ), their default store is preselected as the store location, so counter staff don't have to pick their store at the start of every shift a few notes the default only applies where no store is already selected on the device staff can still change the store from the selector at the top of the flow at any time leave it as no store for users who don't lodge returns at a counter; the flow then preselects the nearest store as usual if the location later stops being a drop off location, the default is ignored and no store is preselected deleting a location clears it as a default from any users it was assigned to you'll find the dropdown in the same dialog as the role and access options, when adding or editing a user