denoland
[Bug]: Pro accounts
Problem description
I have created an organisation, and pay the subscription, but my personal account is still there - when I need to look at access tokens, I see the banner encouraging me to sign up for a pro account.
Maybe the 'bug' is as small as - don't show that message to people who have a paid subscription. Or even better: somehow let me abandon the personal account. I only really want the organisation membership. And it is distracting having to repeatedly keep selecting the organisation entity when I dive into deno-deploy to manage my portfolio.
More clarity may be required - on professional / personal membership is the summary.
Steps to reproduce
- Sign up for a personal account
- Create an organisation
- Join pro using that organisation
- Enjoy confusion
Expected behavior
When I started the pro subscription I expected to have that as main focus. Perhaps it is good to also have a personal, free-tier membership. I don't know. But I don't want that as the default once I have paid and started building - and am being billed.
Environment
No response
Possible solution
Have the option to transfer the personal account to an organisation instead. Move personal account access behind new menu settings for pro users. Check out the deploy site UX for pro members.
Additional context
No response
Hi @jorjun, thanks for the feedback. You make some very good points.
don't show that message to people who have a paid subscription. Or even better: somehow let me abandon the personal account. And it is distracting having to repeatedly keep selecting the organisation entity when I dive into deno-deploy to manage my portfolio. [...] When I started the pro subscription I expected to have that as main focus. Perhaps it is good to also have a personal, free-tier membership. I don't know. But I don't want that as the default once I have paid and started building - and am being billed.
One thing to keep in mind is that there are users that belong to multiple pro organizations. What should be the main focus in these cases? What would you say to something like being able to change the primary organization? This would define the organization that is loaded by default on the landing page.
Regarding creating/checking PATs, I will report as a bug that the "projects" button shown at the top when in the account settings page should navigate to the projects of the organization that was previously selected, instead of always navigating to the projects of the personal account. However, that page is the personal account settings page (they are the personal access tokens after all), therefore it makes sense to show the billing status of the personal account, which might be free or pro. Having said that, another feature we are contemplating is organization access tokens. The scope of their capabilities is still something being defined, but presumably they would be managed in the respective organization's settings page, and would allow one to push deployments only to said organization. Would this replace your need for using PATs?
