A given end user, Local RA User "firstname.lastname@example.org", has been using locally defined permissions, including a local group membership to Local RA group "Local RA Group", to operate Release Automation. The Release Automation install is also integrated with LDAP, and a decision is made to have the end user's permissions derived from group membership defined in LDAP. But when Local RA group "Local RA Group" is removed, the end user loses all permissions and is not inheriting the rights that are granted by the LDAP group membership.
The existing contact Local RA User "email@example.com" was originally created manually and a manual group, Local RA group "Local RA Group" (which contained the given user's permissions definition) was also defined in RA as well.
The manually created Local RA User "firstname.lastname@example.org" does not automatically have ties to the backend LDAP definitions of the "email@example.com" user and the associated LDAP group memberships.
Solution to address is to delete the Local RA User "firstname.lastname@example.org" and have "email@example.com" log back into RA, relying on the existing LDAP integration to re-create the "firstname.lastname@example.org" user in RA, which would then have all of the LDAP groups in place and permissions defined correctly.