# RBAC Configuration

You must configure Kloudfuse to implement RBAC in your deployment.

Copy the following code in your `custom-values.yaml` file and make necessary edits.

The following sections outline the basic steps and provide examples on how to configure various components of RBAC.

- [Enable RBAC](https://docs.kloudfuse.com/platform/3.2.5/rbac-configuration/#rbac-enable)
- [Default User Role](https://docs.kloudfuse.com/platform/3.2.5/rbac-configuration/#default-role)
- [Default Policy](https://docs.kloudfuse.com/platform/3.2.5/rbac-configuration/#default-policy)

To review general concepts, see [Role-Based Access Control (RBAC)](https://docs.kloudfuse.com/platform/3.2.5/rbac/).

## Enable RBAC

The default RBAC policy is a fully-enabled RBAC, with full access.

To enable RBAC, add the following code to the `<custom_values.yaml>` file:

```yaml
RBACEnabled: true
```

## Default User Role

The default user role for new users in Kloudfuse is **Editor**.

**Admins** can change this setting in the UI for individual users. See [Assign Roles](https://docs.kloudfuse.com/platform/3.2.5/admin-user-management/#assign-roles).

To change the default assignment for new users to **Viewer**, use the following code to the `<custom_values.yaml>` file:

```yaml
rbacDefaultUserRole: Viewer
```

## Default Policy

Users who do not have a Policy assigned through the UI get a default level of access, depending on configuration:

```yaml
default_rbac_policy: rbac_allow_all
```

To change the default policy for the various roles, use the following code to the `<custom_values.yaml>` file:

```yaml
default_rbac_policy: rbac_allow_none
```

See [Change a Policy](https://docs.kloudfuse.com/platform/3.2.5/admin-policy-management/#policy-change) to set the policy in the UI.