## Cluster Administration Roles 

• createRole (page 420) 

• createUser (page 420) 

• dropRole (page 420) 

• dropUser (page 420) 

• grantRole (page 420) 

• revokeRole (page 420) 

• viewRole (page 420) 

• viewUser (page 420) 

The admin database includes the following roles for administering the whole system rather than just a single database. These roles include but are not limited to replica set and sharded cluster administrative functions. 

## clusterAdmin 

Provides the greatest cluster-management access. This role combines the privileges granted by the clusterManager (page 408), clusterMonitor (page 409), and hostManager (page 410) roles. Ad- ditionally, the role provides the dropDatabase (page 422) action. 

## clusterManager 

Provides management and monitoring actions on the cluster. A user with this role can access the config and local databases, which are used in sharding and replication, respectively. 

Provides the following actions on the cluster as a whole: 

• addShard (page 421) 

• applicationMessage (page 422) 

• cleanupOrphaned (page 420) 

• flushRouterConfig (page 421) 

• listShards (page 422) 

• removeShard (page 422) 

• replSetConfigure (page 421) 

• replSetGetStatus (page 421) 

• replSetStateChange (page 421) 

• resync (page 421) 

Provides the following actions on all databases in the cluster: 

• enableSharding (page 421) 

• moveChunk (page 422) 

• splitChunk (page 422) 

• splitVector (page 422) 

On the config database, provides the following actions on the settings (page 741) collection: 

• insert (page 419) 

• remove (page 419) 

