UX Group Membership looks awkward

Summary

Current hypothesis, a user may have access inherited, with different access in a sub project. If this is true, the user will appear twice in the overall project with two different permission levels

Steps to reproduce

Create a project to with memberships, create a repo of that project, with additional permissions.

Example Project

https://gitlab.com/gitlab-com/runbooks

What is the current bug behavior?

What is the expected correct behavior?

If permissions are inherited, it should minimally be noted. But overall this could improved greatly. If the permissions that are inherited are indicated by the label of GitLab.com title as listed in the screenshot, this is very ambiguous. This is a link to that project and doesn't help decipher why I'm listed in here twice.

Output of checks

on GitLab.com

Possible fixes

The UX may need a large revision.