Restrict a tenant token to see a subset of the displayedAttributes

[gmourier]

Use case

In the situation where I create tenant tokens using Meilisearch in a multi-tenancy use case, I want certain types of users not to be able to see specific fields within the retrieved documents.

Workarounds

• Do a custom curation depending on the user's type before displaying the search results.
• Maintain an index per tenant token type with different displayed attributes for each index.

Ideas

Goal: I want to hide the partner_price field for non-partner end-users interacting with the search.

When creating a tenant token, I could override the displayedAttributes index setting; the drawback is that I must list every displayable attributes while omitting the one I want to hide.

{
      "product": {
             "displayedAttributes": ["name", "price"] //partner_price is hidden since not listed,
             ...
      }
}

Another solution could be having a proper tenant token property to hide some fields from the displayedAttributes index settings

{
      "product": {
             "hiddenAttributes": ["partner_price"],
             ...
      }
}

[derekperkins]

Great suggestion

[gmourier]

Hey, @derekperkins 👋

Thanks! Do you have a need for it?

[derekperkins]

Not for our current usage of meilisearch, but I can definitely see times where that would be useful. We use similar patterns in our other datastores today.

[Rohukas]

It'd be awesome to have this in Meilisearch!

Here’s my use case:
We currently store forum posts in Meilisearch.
Admins could access fields like user.email, while regular users wouldn’t see any of that.

Another scenario:
Our app has a feature to anonymize usernames by creating a pseudonym for each user.
We can't use Meilisearch for post-searching when anonymization is on since it could reveal the user's real name. However, we still want admins to see the names when searching with Meilisearch.

[aaroncueckermann]

Bumping this as we have a strong need for it too