# Generate a deploy key for private submodules on Netlify now in the UI **URL:** \ **Category:** Updates\ **Tags:** updates\ **Created:** [April 16, 2020, 4:05pm UTC](https://answers.netlify.com/t/generate-a-deploy-key-for-private-submodules-on-netlify-now-in-the-ui/12373 "2020-04-16T16:05:53Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![luke](https://sea1.discourse-cdn.com/netlify/user_avatar/answers.netlify.com/luke/32/39_2.png) [@luke](https://answers.netlify.com/u/luke)\ **Post date:** [May 24, 2021, 2:23am UTC](https://answers.netlify.com/t/generate-a-deploy-key-for-private-submodules-on-netlify-now-in-the-ui/12373/6 "2021-05-24T02:23:36Z")
Hi, @johtso and @dpcY. We do explain a workaround for this in the support guide below: > [@\[Support Guide\] How do I access private repositories in the build environment?](https://answers.netlify.com/t/support-guide-how-do-i-access-private-repositories-in-the-build-environment/723): > > Last reviewed by Netlify Support on December 2022 The link from your repository to our service only authenticates us against the “main” repo that you first configured, and won’t automatically allow access to submodules even if they also belong to you and you’ve granted Netlify access to those repositories. In case your submodule is public, you can change the URI schema for it to start with https://, and it should work without further adjustment (so, in .gitmodules, change git@github.com… to h… Quoting: > 4. You can use this workflow with multiple private submodules attached to the same repository, but that does take some extra work since GitHub does not allow Deploy Keys to be used in multiple places. You’ll have to instead add them to a user (perhaps you? or maybe a robot-account that you create on GitHub) that has access to all repos. Will that solution work for you? If there are other questions, please let us know. --- _[View the full topic](https://answers.netlify.com/t/generate-a-deploy-key-for-private-submodules-on-netlify-now-in-the-ui/12373)._