Remove references to the Override checkbox for filters

guides/common/modules/proc_adding-permissions-to-a-role-by-using-web-ui.adoc

@@ -12,11 +12,5 @@ Use this procedure to add permissions to a role by using {ProjectWebUI}.
 . Select the *Resource type* from the drop-down list.
 The _(Miscellaneous)_ group gathers permissions that are not associated with any resource group.
 . Click the permissions you want to select from the *Permission* list.
-. Depending on the *Resource type* selected, you can select or deselect the *Unlimited* and *Override* checkbox.
-The *Unlimited* checkbox is selected by default, which means that the permission is applied on all resources of the selected type.
-When you disable the *Unlimited* checkbox, the *Search* field activates.
-In this field you can specify further filtering with use of the {Project} search syntax.
-For more information, see xref:Granular_Permission_Filtering_{context}[].
-When you enable the *Override* checkbox, you can add additional locations and organizations to allow the role to access the resource type in the additional locations and organizations; you can also remove an already associated location and organization from the resource type to restrict access.
 . Click *Next*.
 . Click *Submit* to save changes.

guides/common/modules/proc_cloning-a-role.adoc

@@ -27,7 +27,5 @@ You are then prompted to insert a name for the cloned role, for example _org-1 a
 . Click _org-1 admin_, and click *Filters* to view all associated filters.
 The default filters work for most use cases.
 However, you can optionally click *Edit* to change the properties for each filter.
-For some filters, you can enable the *Override* option if you want the role to be able to access resources in additional locations and organizations.
-For example, by selecting the *Domain* resource type, the *Override* option, and then additional locations and organizations using the *Locations* and *Organizations* tabs, you allow this role to access domains in the additional locations and organizations that is not associated with this role.
 You can also click *New filter* to associate new filters with this role.
 ====

guides/common/modules/proc_creating-a-granular-permission-filter-by-using-web-ui.adoc

@@ -11,7 +11,6 @@ For example, limiting the _create_locations_ action with _name = "Default Locati
 
 .Procedure
 . Specify a query in the *Search* field on the *Edit Filter* page.
-Deselect the *Unlimited* checkbox for the field to be active.
 Queries have the following form:
 +
 [options="nowrap", subs="+quotes,verbatim,attributes"]

guides/common/modules/ref_examples-of-using-granular-permission-filters.adoc

@@ -28,8 +28,3 @@ To do so, specify the environment name in the *Search* field, for example:
 ----
 Dev
 ----
-
-You can limit user permissions to a certain organization or location with the use of the granular permission filter in the *Search* field.
-However, some resource types provide a GUI alternative, an *Override* checkbox that provides the *Locations* and *Organizations* tabs.
-On these tabs, you can select from the list of available organizations and locations.
-For more information, see xref:Cloning_a_Role_{context}[].