Prisma Cloud Application Security: Why am I seeing the Limited Permissions error for my repository?

Why does Prisma Cloud show the "Limited Permissions" error for my repository in Settings > Providers > Repositories?

• Prisma Cloud Application Security

There are a few reasons why this could be.

1. Lack of Permissions. The Prisma Cloud DevSecOps app will inherit the permissions of the user or service account integrating the repos. Make sure that you have the default System Admin permission group on Prisma Cloud when integrating your repository. Ensure that you have the right permissions in your VCS according to our documentation.
2. Scanned Branch does not exist. If the scanned branch set in Prisma does not exist or has been renamed, update it in Prisma by navigating to Settings > Providers > Code Repositories > Actions > Set scanned branch.
3. The repo has been removed from the Prisma DevSecOps app on GitHub. If using GitHub, then it's possible that the app does not have visibility into the repo (i.e. it has not been selected in the app to scan). This is sometimes the case when users have selected "Choose from repository list" during the onboarding process. Add the repo back in the list and allow Prisma to complete a periodic scan to view these changes.
4. Repo is too large. Make sure that the size of the repository is less than 5GB.
   1. Note: Sometimes, even if the repo is under this limit, Prisma Cloud will still show the Limited Permissions status. If the repository has many graph connections, for instance, then there is a possibility that Prisma will have trouble scanning it due to its large workload.
   2. If all of the above have been met, please open a support ticket.
5. Incorrect integration ID in the backend. It's possible that the repository's integration ID is mismatched in our backend. If all of the above has been met, please open a support ticket.