Scope accessible fields in tenant tokens

[aaroncueckermann]

It is difficult to use tenant tokens from the front end of an application as it is not possible to choose which fields to return at the token level.

It is difficult because it is not possible to hide internal data in the document or in the case where a document is shared between multiple users it is not possible to hide the information from different users from one another.

Examples would include

1. Customer specific prices are stored in a document and should not be shared between customers.
2. Ranking criteria/scores stored in the index you don't want to share with users.

There is a similar discussion however it is old and has not received activity but I see this as a common use case which should be looked at so I am raising it again cc - https://github.com/orgs/meilisearch/discussions/636

[macraig]

Hi @aaroncueckermann, thanks for your feedback! Your use case makes sense, and we understand the need for more control over the fields in tenant tokens. While we haven’t been able to prioritize this feature yet, we’re still interested in supporting it in the future. We don’t have an ETA, but we appreciate you raising this again and will keep it in mind for our roadmap.

Thank you again for sharing your thoughts!