• dbStats (page 423) 

• find (page 419) 

• killCursors (page 420) 

• listIndexes (page 423) 

• listCollections (page 423) 

• dropCollection (page 420) and createCollection (page 419) on system.profile (page 291) only 

Changed in version 2.6.4: dbAdmin (page 406) added the createCollection (page 419) for the system.profile (page 291) collection. Previous versions only had the dropCollection (page 420) on the system.profile (page 291) collection. 

Provides the following actions on all non -system collections. This role does not include full read access on non-system collections: 

## dbOwner 

• collMod (page 422) 

• collStats (page 423) 

• compact (page 422) 

• convertToCapped (page 422) 

• createCollection (page 419) 

• createIndex (page 420) 

• dbStats (page 423) 

• dropCollection (page 420) 

• dropDatabase (page 422) 

• dropIndex (page 422) 

• enableProfiler (page 420) 

• indexStats (page 423) 

• reIndex (page 422) 

• renameCollectionSameDB (page 423) 

• repairDatabase (page 423) 

• storageDetails (page 421) 

• validate (page 424) 

The database owner can perform any administrative action on the database. This role combines the privileges granted by the readWrite (page 406), dbAdmin (page 406) and userAdmin (page 407) roles. 

## userAdmin 

Provides the ability to create and modify roles and users on the current database. This role also indirectly provides superuser (page 412) access to either the database or, if scoped to the admin database, the cluster. The userAdmin (page 407) role allows users to grant any user any privilege, including themselves. 

The userAdmin (page 407) role explicitly provides the following actions: 

• changeCustomData (page 419) 

• changePassword (page 419) 

