# VAULTROLES

Location: [gRPC API](https://developer.m-files.com/APIs/gRPC-API/index.md) > [Reference](https://developer.m-files.com/APIs/gRPC-API/Reference/index.md) > [Messages](https://developer.m-files.com/APIs/gRPC-API/Reference/Messages/index.md)

HTML version: https://developer.m-files.com/APIs/gRPC-API/Reference/Messages/MFiles.VAULTROLES/

Vault roles (bitfields).

- **Full name:** `MFiles.VAULTROLES`
- **Proto file:** [`mfiles/enums.proto`](https://developer.m-files.com/APIs/gRPC-API/downloads/proto/mfiles/enums.proto)

<a id="fields"></a>

## Fields

| Field | Type | Number | Description |
|---|---|---|---|
| <a id="f-all"></a>`all` | `bool` | 1 | Specifies all flags set; Including any future flags. |
| <a id="f-full_control"></a>`full_control` | `bool` | 2 | Can perform any activity in the vault. |
| <a id="f-can_log_in"></a>`can_log_in` | `bool` | 3 | Can log in to the vault. |
| <a id="f-can_create_objects"></a>`can_create_objects` | `bool` | 4 | Can create new documents. |
| <a id="f-can_see_all_objects"></a>`can_see_all_objects` | `bool` | 5 | Sees all documents in listings, regardless of security settings and deletion state. |
| <a id="f-can_undelete_objects"></a>`can_undelete_objects` | `bool` | 6 | Can undelete previously deleted documents. |
| <a id="f-can_destroy_objects"></a>`can_destroy_objects` | `bool` | 7 | Has permission to permanently destroy documents. |
| <a id="f-can_force_undo_checkout"></a>`can_force_undo_checkout` | `bool` | 8 | Has permission to undo a check-out performed by another user. |
| <a id="f-can_change_all_object_permissions"></a>`can_change_all_object_permissions` | `bool` | 9 | Can change the security settings of all documents and modify all documents. |
| <a id="f-can_change_metadata_structure"></a>`can_change_metadata_structure` | `bool` | 10 | Can modify the meta data structure of the vault (propertydefs, profiles, value lists etc.). |
| <a id="f-can_manage_users"></a>`can_manage_users` | `bool` | 11 | Can create, edit and delete user accounts. Cannot add or remove the Vault Manager role. |
| <a id="f-is_internal_user"></a>`is_internal_user` | `bool` | 12 | An internal user of the vault. This role separates internal enad external users in the vault. |
| <a id="f-can_manage_traditional_folders"></a>`can_manage_traditional_folders` | `bool` | 13 | Can create, modify and delete traditional folders. OBSOLETE: const VAULTROLES VAULTROLE_DEFINE_TEMPLATES = 1 << 12;  //!< Can define templates. |
| <a id="f-can_manage_common_views"></a>`can_manage_common_views` | `bool` | 14 | Can create, modify and delete common views. |
| <a id="f-can_manage_workflows"></a>`can_manage_workflows` | `bool` | 15 | Can create, modify and delete workflows. Modifying event handlers within the workflow still requires SERVERACCESS_RUN_CODE. |
| <a id="f-cannot_manage_private_views"></a>`cannot_manage_private_views` | `bool` | 16 | Cannot create or modify private views. |
| <a id="f-anonymous"></a>`anonymous` | `bool` | 17 | Anonymous role. |
| <a id="f-run_code_on_server"></a>`run_code_on_server` | `bool` | 18 | Can run code on the server hosting this vault. Not included in VAULTROLE_FULL_CONTROL, and cannot be ordinarily granted by it. |

<a id="used-in-fields"></a>

## Used in fields

- [`BasicUserAccountInfo.vaultroles`](https://developer.m-files.com/APIs/gRPC-API/Reference/Messages/MFiles.BasicUserAccountInfo/index.md#f-vaultroles): Bitmask of the vault roles of the user.
- [`UserAccount.vault_roles`](https://developer.m-files.com/APIs/gRPC-API/Reference/Messages/MFiles.UserAccount/index.md#f-vault_roles): Bitmask of the vault roles of the user.