@banjo Thank you for posting your question here.
From your screenshots, I see that you have a rolebinding for your user to the clusterrole `k10-admin` in bookinfo namespace.
However, Profiles are part of `kasten-io` namespace and your user should have at-least get/list permissions for profile resources in `kasten-io` namespace.
The documentation here will help you with a basic-config clusterrole and rolebinding creation for listing some/all profiles and blueprints for a non-cluster-admin user.
Thanks @jaiganeshjk isn’t it its better for user experience that these clusterrole were already created during install?
Not all non-admin users have need to use all the profiles. In a multi-tenant environment, Profiles are segregated for each tenant.
Since, the idea of this cluster role is to restrict the non-admin users to use only a particular profile or blueprint(specified explicitly by name), It is not added by default during K10 installation.