Document clear criteria and patterns for binding permissions to the Organization, Root Workspace and Default Workspace: This document will serve as crucial reference documentation, providing explicit guidance for Insights teams and ensuring clear expectations for how permissions map to the Kessel hierarchy Detail what metadata is required in rbac-config to signify what level the permission should be bound to.  Detail how the seeding process on the RBAC side will occur based on the metadata update The documentation should explicitly clarify the reasoning behind the chosen migration patterns for permissions, enhancing understanding and reducing ambiguity Detail how the RBAC migrator will determine the correct placement (binding level) for permissions based on the "highest" permission requirement within a V2 Role, following the hierarchy: Organization > Root Workspace > Default Workspace > Any other level  The document should establish a clear decision-making process or mapping for Insights teams to follow when categorizing their permissions, leveraging insights from prior POCs.