Restricting source code
![](http://jazz.net/_images/myphoto/66e177e2048ef539f521aa8ee20ae030.jpg)
4 answers
![](http://jazz.net/_images/myphoto/66e177e2048ef539f521aa8ee20ae030.jpg)
Source code viewing (reading) can be restricted by license type, repository access, and project visibility, but not by team level role. I'd suggest opening a work item if you require restricting by team level roles.
License type - remove their developer license and they will not be able to view source code at all
Repository access - some teams use separate physical repositories due to compliance. Also look into Distributed Version Control
Project visibility - you can have two projects on the same server, but place the source code under one of the projects with restricted visibility
License type - remove their developer license and they will not be able to view source code at all
Repository access - some teams use separate physical repositories due to compliance. Also look into Distributed Version Control
Project visibility - you can have two projects on the same server, but place the source code under one of the projects with restricted visibility
![](http://jazz.net/_images/myphoto/66e177e2048ef539f521aa8ee20ae030.jpg)
Thanks. The options I don't believe will work easily for us. The people who cannot see the restricted code still will require developer access as they with with other source code. Putting it in a separate repository or project would require us to re-architect our source and build structures, which we would be unable to do in the short term.
I believe there is already a workitem open for this ... we were hoping it may be available in 3.0 but it looks like it is not.
Susan
I believe there is already a workitem open for this ... we were hoping it may be available in 3.0 but it looks like it is not.
Susan