---
title: "Comment by Yoel Navas Escalante on \"Schema-Based Multi-Tenancy with NestJS and Prisma\" | Hashnode"
description: "Very neat solution, congrats; I just want to point out a little detail (and please correct me if I&#39;m wrong), you don&#39;t need to explicitly make prismaCli"
url: "https://hashnode.com/posts/schema-based-multi-tenancy-with-nestjs-and-prisma/5fe1c2b1a669d865551f6756/comment/6073634b1494367be6d2b4ec"
---

[Discussion](https://hashnode.com/posts/schema-based-multi-tenancy-with-nestjs-and-prisma/5fe1c2b1a669d865551f6756)

Comment [Schema-Based Multi-Tenancy with NestJS and Prisma](https://hashnode.com/posts/schema-based-multi-tenancy-with-nestjs-and-prisma/5fe1c2b1a669d865551f6756)

[Yoel Navas Escalante](https://hashnode.com/@ynavas)

[Apr 11, 2021](https://hashnode.com/posts/schema-based-multi-tenancy-with-nestjs-and-prisma/5fe1c2b1a669d865551f6756/comment/6073634b1494367be6d2b4ec)

Very neat solution, congrats; I just want to point out a little detail (and please correct me if I'm wrong), you don't need to explicitly make prismaClientProvider request-scpoed, since you are injecting REQUEST into it, wich is in itself a request-scpoed provider, then his scope is bubbled up by the injection chain.

[Dario Ielardi](https://hashnode.com/@darioielardi)

[Apr 12, 2021](https://hashnode.com/posts/schema-based-multi-tenancy-with-nestjs-and-prisma/5fe1c2b1a669d865551f6756/comment/6073634b1494367be6d2b4ec#reply-6074849385f3a21e3926c07c)

Hello, thank you for your kind words.

You're right, there's no need to explicitly make the custom provider request-scoped, I did that just to be totally explicit about the intended behavior.
