Search filters offer a way to control user access to documents in the index. This may be required for document security purposes or to allow the user to search within a specific data set. This functionality uses Solr's filter query capability, where a predefined search is added to the end of the user's query without the user entering it themselves.
In order for content to be filtered based on who the user is or what group they belong to, the criteria used for filtering must exist on each document prior to indexing. This may require some preprocessing of each document to make sure it contains the data to be used in filtering. For more information, see Securing Access to Content.
If using LDAP for user authentication, LDAP-defined usernames and/or groups can be mapped to a filter. This filter would then be applied when the user logs in the LucidWorks Enterprise.
Creating a New Filter
A default filter is included with LucidWorks Enterprise. This filter is used for anonymous users (that is, users who have not logged in to the system). The default "admin" user is also a member of the default filter. The filter can be modified to customize the search experience for users who are not logged in, but it should not be disabled or deleted if anonymous access to the system is desired.
New filters can be created with the form below by clicking Add Filter.
You can enter the following parameters:
| Parameter | Description |
|---|---|
| Search Filter Name | The name of the filter. Search filter names may contain only letters, digits, underscores and hyphens. Spaces and other punctuation symbols are not allowed, and search filter names are case sensitive. |
| Groups | The list of LDAP groups that are given this role; a user who is a member of this group will be assigned this role. The list can be separated by either a space or a comma. |
| Users | The list of users who are given this role. This can be a manually created user or an LDAP user. The list can be separated by either a space or a comma. |
| Filters | The filter query parameters to apply to this role. Any supported LucidWorks Enterprise and Solr syntax (dependent on the query parser in use) can be employed (such as, range queries, field queries, dates, and so on). |
When you are done, click Create to create and save the filter. LucidWorks Enterprise verifies the new filter by running it against documents indexed, and displays an message if there are no documents in the collection that match.
 | Filter Queries and Alerts At this time, filter queries applied to a user's query are not saved with the user's query when they save an alert. This is a consideration if using search filters for document-level security. |