Skip to content

Commit 3c83505

Browse files
authored
Adding permissions level
That sentence looked funny and only by editing it did I see the html comment. I think this change is right based on this doc https://docs.microsoft.com/en-us/azure/devops/organizations/security/permissions-access?view=azure-devops#azure-artifacts
1 parent 0a74467 commit 3c83505

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

Diff for: docs/artifacts/nuget/upstream-sources.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ To learn more about the concept of upstream sources, please see the [concepts pa
4545

4646
### Adding upstreams to a popular feed
4747

48-
Once you enable the nuget.org upstream source, any <!-- what permissions tier? --> that runs a package request against your feed can save packages from nuget.org into your feed. If you've distributed your feed URL to a large set of consumers, this means that users outside your team could save packages you weren't expecting into your feed.
48+
Once you enable the nuget.org upstream source, any Contributor or Owner that runs a package request against your feed can save packages from nuget.org into your feed. If you've distributed your feed URL to a large set of consumers, this means that users outside your team could save packages you weren't expecting into your feed.
4949

5050
If you're concerned about this, consider creating a new feed then adding nuget.org and your current feed as upstream sources to that feed.
5151

0 commit comments

Comments
 (0)