.. _connect-rbac-index: |kconnect-long| and |rbac| -------------------------- :ref:`Role-Based Access Control (RBAC) ` can be enabled for your |cp| environment. If |rbac| is enabled, there are role bindings that you may need to configure (or have set up for you) before you work with |kconnect| and |kconnect| resources. There are also |rbac| configuration parameters that you need to add to your |kconnect| worker configuration and connectors. |kconnect| roles are managed by the |rbac| system administrator for your environment. Make sure to review your user principal, |rbac| role, and permissions with your |rbac| system administrator before creating a |kconnect| cluster or connectors. .. tip:: Before configuring RBAC for |kconnect-long|, read the white paper `Role-Based Access Control (RBAC) for Kafka Connect `__. This white paper covers basic RBAC concepts and provides a deep dive into using RBAC with |kconnect-long| and connectors. It also contains a link to a GitHub demo so you can see how it all works on a local |cp| installation. The following sections provide information about how to configure |rbac| access as it applies to |kconnect-long|. For information about how to configure |rbac| for the overall |cp| environment and other components, see :ref:`Role-Based Access Control (RBAC) `. .. toctree:: :maxdepth: 1 :titlesonly: rbac/connect-rbac-getting-started rbac/connect-rbac-connect-cluster rbac/connect-rbac-worker rbac/connect-rbac-connectors rbac/connect-rbac-secret-registry rbac/connect-rbac-example