# DataSHIELD authorization between Project and Database **URL:** \ **Category:** Beginner Support\ **Created:** [20 February 2023 14:40 UTC](https://datashield.discourse.group/t/datashield-authorization-between-project-and-database/717 "2023-02-20T14:40:05Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![esalehi](https://avatars.discourse-cdn.com/v4/letter/e/3e96dc/32.png) [@esalehi](https://datashield.discourse.group/u/esalehi)\ **Post date:** [20 February 2023 14:40 UTC](https://datashield.discourse.group/t/datashield-authorization-between-project-and-database/717/1 "2023-02-20T14:40:05Z")
Hello Everyone, we have a DataSHIELD instance where we need to habe multiple separated projects with their databases for data import. For example, Project A (with database A) and Project B (with database B). It means that the users with role administrate inside Project A should only be able to import tables from database A (via an access token), not database B. But it seems to be impossible to manage this. When the admin of Project A creates a token for its project, he can import data from all connected databases to DataSHIELD instance. Isn’t it a kind of security issue? Thank you in advance for any help 🙂 P.S: I know that the admin of Project A should know the name of database B and its tables to load the data, but nevertheless, I guess it should be managed by datashield. ---
**Author:** ![yannick](https://yyz2.discourse-cdn.com/free1/user_avatar/datashield.discourse.group/yannick/32/19_2.png) [@yannick](https://datashield.discourse.group/u/yannick)\ **Post date:** [20 February 2023 15:05 UTC](https://datashield.discourse.group/t/datashield-authorization-between-project-and-database/717/2 "2023-02-20T15:05:38Z")
Hi, This use case is not supported. Make on Opal server per database instead (it is easy with docker and a reverse proxy). Regards Yannick