When working with teams at BPOs, you may want to ensure that data is not visible to users outside their team. Assembled offers the ability to configure Restricted sites so that configured users can only view agents in their same site.
If you would like to use Restricted sites, please reach out to our Support team to get it enabled on your instance.
Restricted sites functionality
All users will have the permission level determined by their role detailed in the Managing roles and permissions article. With a Restricted site, they will be limited to only view agents in the same Restricted site.
In our example below, we have a Lead and two Basic role agents who have the same Restricted site.
The Lead is only able to view themselves and the two agents on the Staffing timeline, People page, and Agent scorecard. Managers with a Restricted site will only be able to view their site agents on the Team performance report. We do not recommend putting Restricted sites on Admin accounts, but it is possible.
This feature behaves as a site filter that cannot be removed and can only be filtered to the Restricted sites on the agent’s profile. Because of this, our contact and forecast volume are not affected by this filter. If you want to distinguish contact volume for these sites, we recommend using queues to map and distinguish contacts handled by these sites.
Setting up Restricted sites
Create the site in Company Settings → Filters that you want to use as the Restricted site. Please note that a parent site cannot be used as a Restricted site but we can use their child sites as a workaround.
Now create or edit the agents you want to be restricted. Set their Site and Restricted site fields to be the Restricted site you have created. If you want to use a parent site, you’ll need to select all the child sides of the parent as the Restricted site.
This feature can be used for any situation you want to limit data access, not just for BPOs. If you have any questions, feel free to reach out to our Support team!