> For the complete documentation index, see [llms.txt](https://docs.enate.net/whats-new/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/whats-new/older-versions/changes-overview-older-versions/2021.1-changes-overview/builder/external-contact-scoping.md). # External Contact Scoping v2021.1 You can change the scope of your external contacts to either Global, Local or Global and Local: ![](https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MMq3QmswWRu5qbijFN8%2F-MXmHl1QNf7p4c5XcWrN%2F-MXmIN36-oKXqQlKopjH%2FContact-Scoping.gif?alt=media\&token=7bf4e1dc-c770-42ba-9e9c-f1cabfdb8aa9) #### Global * Setting the contact scope to Global means that all the external contacts are scoped to Global/All Companies and those contacts can access/create work items of All the Companies. * Contact Creation in Work Manager : All the contacts created via Quick Find search or contact card in work item and Bulk creation are by default scoped to Global/All Companies. {% hint style="info" %} Please note that selecting this option will clear the company relationship from every external contact. {% endhint %} #### Local * Setting the contact scope to Local means that all the external contacts are scoped to a particular company and those contacts can access/create work items of the particular scoped company. * Contact Creation in Work Manager : All the contacts created via Quick Find search or contact card in work item and Bulk creation provides an option to set the scope of the contact to particular company. * Search from Contact Card: users in Work Manager will only be able to search for external contacts belonging to companies which the contact has associated to. * Scope Change in Work Manager : Any locally scoped contact can be changed to a different company when the contact has no active work items associated. If the contact has associated work items the contact should be removed from the work items to change the scope successfully. {% hint style="info" %} Please note that it is only possible to set the scope to Local if all existing external contacts have a company associated with them. This can be achieved by editing them in the Contact Management view in Work Manager. {% endhint %} #### Global and Local * This setting lets you set some external contacts to Local and some to Global. This means that you can assign some external contacts with a company (and therefore users in work manager will only be able to create and work items for these 'local' external contact for the particular company that the external contact is associated with), and you can assign some external contacts as 'Global', so users in work manager will be able to create work items for all companies for these 'Global' external contacts. * Contact Creation in Work Manager : All the contacts created via Quick Find search or contact card in work item and Bulk creation provides an option to set the scope of the contact to particular company or set the scope to Global/All Companies. * Search from Contact Card: users in Work Manager will be able to search for all external contacts which are associated to company to which work item is associated and all other global external contacts. * Scope Change in Work Manager : Any locally scoped contact can be changed to Global and any globally scoped contact cannot be changed to a particular company if the contact has associated to work items of multiple companies, in this case the contact should be removed from the work items of other companies. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.enate.net/whats-new/older-versions/changes-overview-older-versions/2021.1-changes-overview/builder/external-contact-scoping.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.