User & Content Filter Parameters

The combination of content filters (both at user level and shared URL level) and parameters allow admin users to control user access to a subset of available data on the same dashboard or widget. Filters are replaced at runtime for direct queries, or applied on top of the data returned by a query.

User Level Filters

User level filters limits data based on criteria associated to that user. For example, a national manager may be allowed to see data for all regions, but a Regional manager is only allowed to see data for their specific region for the same dashboard.

To set the user level filters, set the User Filter either during user invitation or if the user is already in the system, via the Edit User From the Team Menu.

Following example limits a user to a specific organizationid, applied on the top of the results of the query. Note that the organizationid must be present in the dataset for the filter to take effect.

Also note the second filter is a query parameter called $c9_region$ passed into the query.

Query Parameters Format

Query parameters are replaced at runtime during query execution based on user level filters set or if contentFilters are passed into the dashboard (typically via the embed API).


Query Example:


$c9_region$ is replaced with contentFilter parameter (and defaults to West in the above example if one is not passed in).

This can be passed in either using the contentFilters URL parameter, via the JavaScript API, or can be set at user level. User level filters are always applied automatically for that user and cannot be modified by the user.

For example, we define a user contentFilters or URL contentFilters as:

    {"fieldName":"$c9_territory$","values":["Bay Area"],"operator":"Equals"}

For filters on the cached datasets in Knowi, omit the $c9_ prefix. Example:

    {"fieldName":"territory","values":["Bay Area"],"operator":"Equals"}

For more details on using contentFilters in an embedded use case, see