1 ---
2 title: npm-owner
3 section: 1
4 description: Manage package owners
5 github_repo: npm/cli
6 github_branch: release/v6
7 github_path: docs/content/commands/npm-owner.md
8 redirect_from:
9 - /cli-documentation/v6/cli-commands/npm-owner
10 - /cli-documentation/v6/cli-commands/owner
11 - /cli-documentation/v6/commands/npm-owner
12 - /cli-documentation/v6/commands/owner
13 - /cli-documentation/v6/npm-owner
14 - /cli-documentation/v6/owner
15 - /cli/v6/cli-commands/npm-owner
16 - /cli/v6/cli-commands/owner
17 - /cli/v6/commands/owner
18 - /cli/v6/npm-owner
19 - /cli/v6/owner
20 ---
21
22 ### Synopsis
23
24 ```bash
25 npm owner add <user> [<@scope>/]<pkg>
26 npm owner rm <user> [<@scope>/]<pkg>
27 npm owner ls [<@scope>/]<pkg>
28
29 aliases: author
30 ```
31
32 ### Description
33
34 Manage ownership of published packages.
35
36 - ls: List all the users who have access to modify a package and push new versions. Handy when you need to know who to bug for help.
37 - add: Add a new user as a maintainer of a package. This user is enabled to modify metadata, publish new versions, and add other owners.
38 - rm: Remove a user from the package owner list. This immediately revokes their privileges.
39
40 Note that there is only one level of access. Either you can modify a package, or you can't. Future versions may contain more fine-grained access levels, but that is not implemented at this time.
41
42 If you have two-factor authentication enabled with `auth-and-writes` then you'll need to include an otp on the command line when changing ownership with `--otp`.
43
44 ### See Also
45
46 - [npm publish](/cli/v6/commands/npm-publish)
47 - [npm registry](/cli/v6/using-npm/registry)
48 - [npm adduser](/cli/v6/commands/npm-adduser)