Owner vs Developer: which account can use ABP Studio, CLI and Suite? #10765

The symptom

You're signed in with your abp.io account and your organization has a commercial license, but the tools still behave as if you have no license:

• ABP Studio falls back to the Community edition and shows an "upgrade your license" message on almost every action.
• ABP CLI fails when creating a pro template or downloading source, with a message like "Could not find your organization! Make sure the owner of your organization set you as a developer...".
• ABP Suite may behave as unlicensed or fail to load its licensed features.

This is not a bug when the signed-in account isn't assigned as a Developer. All three tools read the license from the account you signed in with, and this is what you get when that account is not a Developer in your organization. (The same "no license" state can also mean an expired license, but if your organization's license is active, the developer-seat check is the reason here.)

Owner vs Developer

An abp.io organization has two separate roles, and they are not the same thing:

• Owner: manages the organization, buys licenses and allocates developer seats. An Owner cannot write code in ABP projects, cannot download the pro modules / sample projects, and cannot use the pro features of ABP Studio, CLI or Suite.
• Developer: can write code, download the source code and samples, use the pro tooling, and ask questions on the support website.

So having a commercial license on the organization, or being only an Owner, is not enough. Studio, CLI and Suite all check the same thing: whether your signed-in account holds a Developer seat. If it doesn't, they treat you as unlicensed, they just surface it differently: Studio drops to the Community edition and shows the upgrade dialog, the CLI fails a pro template / download with the "set you as a developer" message, and Suite doesn't load its licensed features. A single person can be both an Owner and a Developer at the same time, most people who buy the license for themselves need to add themselves under both.

How to fix it

1. Open https://abp.io/my-organizations and check whether the account you use in the tools is listed under Developers (not only under Owners).
2. If it isn't, an organization owner adds it to the Developers list. You can be an Owner and a Developer at the same time.
3. Sign out and sign in again in the tool you're using (in ABP Studio, or run abp logout then abp login for the CLI / Suite). This step matters: the developer membership is cached, so just restarting won't pick it up, you have to re-login.

After that the tools see the commercial license and the message goes away.

How to tell which account the tool is using

ABP Studio's upgrade dialog shows the username, email and organization it resolved, and the CLI prints the account it's logged in as. If that email isn't the one holding the developer seat, or the organization is empty, you're signed in with the wrong account, sign out and sign in with the correct one.