Roles and permissions
What Admin, Developer, and Team member actually unlock, and how that changes with what you are adding someone to.
A project's Team tab offers different roles depending on what kind of project it is. Every share still grants one flat level of access, there is no partial or read-only role for project membership. Sharing a single item, a profile in particular, is different, that has its own finer-grained access, covered on Sharing projects and items.
Roles by project type
A static website or a server has no Studio behind it to give a Developer role meaning, so the invite screen skips the role picker entirely and every person added is an Admin of that deployment.
Who administers a User Group deployment
A User Group deployment is built for OTHER people to sign in to, its Team tab lists them as members, not as Admins or Developers. Administering the deployment itself, changing its setup, approving a member's signup, is a separate question, and it is answered by who holds an Admin or Developer share, either on the deployment directly or on the Studio project that built it. Both are checked, so the person who built the app in Studio can approve a member without ever being added to the deployment's own team.
A member can also be handed one of the deployment's own API keys (Assign key, on the Team tab). A screen running on that key can act with delegated admin authority inside the app, for example to add another member, but it can never approve or deny a self-signup: that decision is refused to anything that is not a signed-in person.
Changing someone's role
Edit access, on an Admin or Developer's row, moves them between the two without removing and re-inviting them. It only appears once they have joined, a pending invitation is cancelled and re-sent with a different role instead.
Once someone holds Admin or Developer access to a project, they can invite others to it too, the invite is not limited to the project's owner. The one exception is a self-signup waiting for approval on a User Group deployment: an account holding only a delegated API key cannot approve one, only a signed-in Admin, Developer, or the owner can.