- Reference >
- Database Commands >
- Role Management Commands >
- grantPrivilegesToRole
grantPrivilegesToRole¶
On this page
Definition¶
-
grantPrivilegesToRole
¶ Assigns additional privileges to a user-defined role defined on the database on which the command is run. The
grantPrivilegesToRole
command uses the following syntax:{ grantPrivilegesToRole: "<role>", privileges: [ { resource: { <resource> }, actions: [ "<action>", ... ] }, ... ], writeConcern: { <write concern> } }
The
grantPrivilegesToRole
command has the following fields:Field Type Description grantPrivilegesToRole
string The name of the user-defined role to grant privileges to. privileges
array The privileges to add to the role. For the format of a privilege, see privileges
.writeConcern
document Optional. The level of write concern for the modification. The writeConcern
document takes the same fields as thegetLastError
command.
Behavior¶
A role’s privileges apply to the database where the role is created. A
role created on the admin
database can include privileges that apply
to all databases or to the cluster.
Required Access¶
You must have the grantRole
action on the database a privilege targets in order to
grant the privilege. To grant a privilege on multiple databases or on the
cluster
resource, you must have the grantRole
action on
the admin
database.
Example¶
The following grantPrivilegesToRole
command grants two
additional privileges to the service
role that exists in the
products
database:
use products
db.runCommand(
{
grantPrivilegesToRole: "service",
privileges: [
{
resource: { db: "products", collection: "" }, actions: [ "find" ]
},
{
resource: { db: "products", collection: "system.js" }, actions: [ "find" ]
}
],
writeConcern: { w: "majority" , wtimeout: 5000 }
}
)
The first privilege in the privileges
array allows the user to
search on all non-system collections in the products
database. The
privilege does not allow queries on system collections, such as the system.js
collection. To grant access to these
system collections, explicitly provision access in the privileges
array. See Resource Document.
The second privilege explicitly allows the find
action on
system.js
collections on all
databases.