docker / hub-feedback

Feedback and bug reports for the Docker Hub
https://hub.docker.com
233 stars 48 forks source link

Confusing "Docker Personal" on billing for Team subscription #2194

Open avbentem opened 2 years ago

avbentem commented 2 years ago

Problem description

Users who are assigned a seat in a Team subscription still see "Docker Personal" in Docker Hub.

Docker Desktop does show "TEAM TIER" though. Also, some limits op the page (such as "0 of unlimited tokens active") seem to indicate that the Team subscription is somehow known. I have not validated what limits actually apply; maybe Hub really thinks this is a personal account, not a seat in a Team.

URL: https://hub.docker.com/billing (also, there seems to be no other place where the correct details are shown)

Hub Username: avanbentem (this is NOT about my private Pro account, which is linked to this GitHub account)

Screenshots of the issue

image

Task List

avbentem commented 2 years ago

Also, confusion commenced as, after clicking the link in the Team invite email and setting up the account following that, I was shown some Choose a Plan page. That page should not be shown when a new new account is already paid for by a seat in a Team subscription.

mark-dr commented 1 year ago

This is deliberate, but I understand the confusion. Every user of Docker Hub has a personal account that's separate from their organization memberships. In this case, it sounds like your personal account (avanbentem) is on Docker Personal, but is a member of an organization on Docker Team.

Which plan applies will vary according to what you're doing. For instance:

If you only use your account to contribute to repositories belonging to your team, then in practice you can ignore this distinction.

avbentem commented 1 year ago

Of course, I could deduct this is how it works. But, deliberate? 🤔 I still feel that being shown all this, along with "Choose a plan" after clicking the link from the team's invite email, is just very bad UX for your paying customers. 🤯

(Note that this issue is half a year old. Maybe things have improved since.)

mark-dr commented 1 year ago

You make an excellent point - I agree that could be a clearer experience. Thanks for reporting it! I've passed it onto the relevant team here.