Configuring user and group sync filters

You can configure the bitwarden Directory Connector to use filters to limit the users and/or groups that are processed for syncing to your bitwarden organization.

The syntax for filtering is different for each directory server type and is covered in detail below.

Table of Contents

Active Directory and Other LDAP Directories

The group and user filters can be in the form of any LDAP compatible search filter. Additionally, Active Directory provides a few more advanced options as well as a few limitations when writing search filters as opposed to other more standard LDAP directories. You can read more about writing LDAP search filters here:


Search for all entries that have objectClass=user AND cn that contains the word ‘Marketing’.



Active Directory does not implement extensible matching, the following examples won’t work with it.

Find entries with an OU component of their DN which is either ‘Miami’ or ‘Orlando’.


To exclude entities which match an expression, use ‘!’. Find all Chicago entries except those with a Wrigleyville OU component.



These examples are written for Active Directory. In order to use them for something such as OpenLDAP the attributes will need to be changed.

Users in the ‘Heroes’ group


Users that are a member of the ‘Heroes’ group, either directly or via nesting


Azure Active Directory

The Microsoft Graph API provides advanced filtering capabilities through the $filter parameter using OData syntax. This parameter is exposed to you in both the user and group filters of the Directory Connector.

Read more about the $filter parameter with OData syntax here:



G Suite


The G Suite APIs do not provide a way to filter groups directly, however, you can use our custom filtering syntax that allows you to exclude or include a comma separated list of group names.


include:Group A,Sales People,My Other Group
exclude:Group C,Developers,Some Other Group


We provide the same custom filtering syntax that allows you to exclude or include a comma separated list of user emails.

Additionally, the G Suite APIs provide limited filtering capabilities for users that are exposed to you. Read more about filtering with the query parameter here:

You can combine both of these filtering options by concatenating the two strings with a pipe (|);


Only the include/exclude filter:

An include/exclude filter + a G Suite query search:

exclude:[email protected],[email protected]|orgName=Engineering orgTitle:Manager

Only the G Suite query search (notice the | prefix that is required):

|orgName=Engineering orgTitle:Manager

Was this helpful?

Rate this article:

Email Us

Want to talk to a human?

Send Us An Email