# Territory Security logic - where located **URL:** \ **Category:** Epicor ERP 10\ **Tags:** e10\ **Created:** [June 2, 2020, 6:40pm UTC](https://www.epiusers.help/t/territory-security-logic-where-located/67730 "2020-06-02T18:40:38Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![skhayatt](https://www.epiusers.help/letter_avatar_proxy/v4/letter/s/71c47a/32.png) [@skhayatt](https://www.epiusers.help/u/skhayatt)\ **Post date:** [June 2, 2020, 6:40pm UTC](https://www.epiusers.help/t/territory-security-logic-where-located/67730/1 "2020-06-02T18:40:38Z")
We have given our sales folks access to the Salesperson WB Tracker. The menu item behind it is SalespersonWorkBenchTracker.dll. However when I go to dashboards, I see only Salesperson Workbench. We would like to create s second dashboard, with different information, that has the same security rules as the Salesperson Workbench tracker. Where can I find the implementation of the security rules? I made a copy of the SalesPersonWorkbench so that I could poke through it, but have found nothing. Thus far, I have tried the the following: 1. About half the z queries in the WB tracker (am still going through them) 2. In the tracker itself I am assuming that I am looking for criteria that has something to do with whether the current user is an authorized user of a specific workforce ID, but I have not yet come across anything like that. Any ideas? Thanks. ---
**Author:** ![ckrusen](https://www.epiusers.help/user_avatar/www.epiusers.help/ckrusen/32/50584_2.png) [@ckrusen](https://www.epiusers.help/u/ckrusen)\ **Post date:** [June 2, 2020, 6:46pm UTC](https://www.epiusers.help/t/territory-security-logic-where-located/67730/2 "2020-06-02T18:46:17Z")
DB security related to sales info is heavily influenced by Territories. If you’re using Territories, you might have hit some impassable security issues. ---
**Author:** ![skhayatt](https://www.epiusers.help/letter_avatar_proxy/v4/letter/s/71c47a/32.png) [@skhayatt](https://www.epiusers.help/u/skhayatt)\ **Post date:** [June 2, 2020, 6:48pm UTC](https://www.epiusers.help/t/territory-security-logic-where-located/67730/3 "2020-06-02T18:48:47Z")
We are using territories. I just want to be able to take the same security logic and apply it to another dashboard, but I can’t see where the security logic is to even read it. ---
**Author:** ![ckrusen](https://www.epiusers.help/user_avatar/www.epiusers.help/ckrusen/32/50584_2.png) [@ckrusen](https://www.epiusers.help/u/ckrusen)\ **Post date:** [June 2, 2020, 7:06pm UTC](https://www.epiusers.help/t/territory-security-logic-where-located/67730/4 "2020-06-02T19:06:49Z")
We don’t use territories. I’m only familiar with their impact on data access, from posts I’ve seen on here. I may be wrong but those security rules are at the DB level. Yo may have to make the dashboards BAQ in such a way, that it inherits those rules. ---
**Author:** ![Mark\_Wonsil](https://www.epiusers.help/user_avatar/www.epiusers.help/mark_wonsil/32/51594_2.png) [@Mark\_Wonsil](https://www.epiusers.help/u/Mark_Wonsil)\ **Post date:** [June 2, 2020, 7:21pm UTC](https://www.epiusers.help/t/territory-security-logic-where-located/67730/5 "2020-06-02T19:21:28Z")
From my experience, if you use BAQs or Business objects, the framework just handles it. If you’re going to the database via dbContext and code then you’re on your own. A BAQ definitely respects territory (and plant, and company, and tenant) rules. ---
**Author:** ![timshuwy](https://www.epiusers.help/user_avatar/www.epiusers.help/timshuwy/32/90122_2.png) [@timshuwy](https://www.epiusers.help/u/timshuwy)\ **Post date:** [June 2, 2020, 7:24pm UTC](https://www.epiusers.help/t/territory-security-logic-where-located/67730/6 "2020-06-02T19:24:15Z")
> [@skhayatt](#): > > using territories. I just want to be able to take the same security logic and apply it to another dashboard, but I can’t see where the security logic is to even read it. As long as you include the Customer table into your BAQ, then the normal territory logic will be used. Epicor applies additional security logic automatically to certain tables, which automatically includes the customer table as one of those tables. ---
**Author:** ![skhayatt](https://www.epiusers.help/letter_avatar_proxy/v4/letter/s/71c47a/32.png) [@skhayatt](https://www.epiusers.help/u/skhayatt)\ **Post date:** [June 2, 2020, 7:35pm UTC](https://www.epiusers.help/t/territory-security-logic-where-located/67730/7 "2020-06-02T19:35:29Z")
That’s the piece I was missing. Did not know it was enforced, if not done so explicitly. Thanks.