@cryptotaxi247 / documentation
Code Commits Issues Pulls Sessions CI/CD
kartykp/upgrade-path-to-regex
@reggi/path-to-regexp dependabot/npm_and_yarn/main/copy-to-clipboard-4.0.2 dependabot/npm_and_yarn/main/eslint-10.4.0 dependabot/npm_and_yarn/main/npmcli/eslint-config-7.0.0 dependabot/npm_and_yarn/main/proc-log-7.0.0 dependabot/npm_and_yarn/npm_and_yarn-826852524d dependabot/npm_and_yarn/npm_and_yarn-ab9a7f4bc2 deprecate-totp-2fa dhei/classic-tokens gat-bypass-2fa-docs jpg619/fix-accessibility-content-flow jpg619/version-bump-tar-2 kartykp/gat-bypass-2fa-docs kartykp/upgrade-path-to-regex main maitxn/version-bump-tar patch-1 reggi/cache-based-on-version reggi/dev-engines reggi/fix-transform-prettier reggi/overrides update-search-sensitivity
mdx 134 lines 4.19 KB
Raw
1 ---
2 title: Managing team access to organization packages
3 redirect_from:
4 - /managing-team-access-to-org-packages
5 - /managing-team-access-to-packages
6 ---
7
8 import shared from '~/shared.js'
9
10 As an organization owner or team admin, you can add or remove package access to or from teams in your organization.
11
12 ## Adding package access to a team
13
14 ### Adding package access to a team on the web
15
16 1. <>{shared['user-login'].text}</>
17
18 <>{shared['user-login'].image}</>
19
20 2. <>{shared['account-settings'].text}</>
21
22 <>{shared['account-settings'].image}</>
23
24 3. <>{shared['organization-selection'].text}</>
25
26 <>{shared['organization-selection'].image}</>
27
28 4. <>{shared['organization-teams-tab'].text}</>
29
30 <>{shared['organization-teams-tab'].image}</>
31
32 5. Beside the team to which you want to add package access, click **Packages**.
33
34 <Screenshot src="/organizations/managing-teams/team-packages-button.png" alt="Screenshot of the packages button" />
35
36 6. On the "Add Packages" page, in the "Package" field, type the name of the package and select from the dropdown menu.
37
38 <Screenshot src="/organizations/managing-teams/team-package-select.png" alt="Screenshot of the package selection" />
39
40 7. Click **+ Add Existing Package**.
41
42 <Screenshot src="/organizations/managing-teams/team-package-add-existing-button.png" alt="Screenshot of the add package button" />
43
44 8. Beside the package name, click **read** or **read/write** to set the team permissions for the package.
45
46 <Screenshot src="/organizations/managing-teams/team-package-permissions.png" alt="Screenshot of the team package permission option" />
47
48 ### Adding package access to a team using the CLI
49
50 As an organization owner or team admin, you can use the CLI `access` command to add package access to a team on the command line:
51
52 ```
53 npm access grant <read-only|read-write> <org:team> [<package>]
54 ```
55
56 For more information, see "[npm-access][access-cli]".
57
58 ## Removing package access from a team
59
60 ### Removing package access from a team on the web
61
62 1. <>{shared['user-login'].text}</>
63
64 <>{shared['user-login'].image}</>
65
66 2. <>{shared['account-settings'].text}</>
67
68 <>{shared['account-settings'].image}</>
69
70 3. <>{shared['organization-selection'].text}</>
71
72 <>{shared['organization-selection'].image}</>
73
74 4. <>{shared['organization-teams-tab'].text}</>
75
76 <>{shared['organization-teams-tab'].image}</>
77
78 5. Beside the team from which you want to remove package access, click **Packages**.
79
80 <Screenshot src="/organizations/managing-teams/team-packages-button.png" alt="Screenshot of the packages button" />
81
82 6. Beside the name of the package from which you want to remove access, click **x**.
83
84 <Screenshot src="/organizations/managing-teams/team-package-remove-button.png" alt="Screenshot of the remove package button" />
85
86 ### Removing package access from a team using the CLI
87
88 As an organization owner or team admin, you can also use the CLI `access` command to revoke package access from a team on the command line:
89
90 ```
91 npm access revoke <org:team> [<package>]
92 ```
93
94 For more information, see "[npm-access][access-cli]".
95
96 ## Changing package access for a team
97
98 ### Changing package access for a team on the web
99
100 1. <>{shared['user-login'].text}</>
101
102 <>{shared['user-login'].image}</>
103
104 2. <>{shared['account-settings'].text}</>
105
106 <>{shared['account-settings'].image}</>
107
108 3. <>{shared['organization-selection'].text}</>
109
110 <>{shared['organization-selection'].image}</>
111
112 4. <>{shared['organization-teams-tab'].text}</>
113
114 <>{shared['organization-teams-tab'].image}</>
115
116 5. Beside the team from which you want to remove package access, click **Packages**.
117
118 <Screenshot src="/organizations/managing-teams/team-packages-button.png" alt="Screenshot of the packages button" />
119
120 6. Beside the package name, click **read** or **read/write** to set the team permissions for the package.
121
122 <Screenshot src="/organizations/managing-teams/team-package-change-permissions.png" alt="Screenshot of the change package permission option" />
123
124 ### Changing package access for a team from the CLI
125
126 As an organization owner or team admin, you can change package access for a team from the command line:
127
128 ```
129 npm access
130 ```
131
132 For more information, see the [`npm-access` CLI documentation][access-cli].
133
134 [access-cli]: /cli/access