Organisation account

What actually differs

Note the last row. Nothing about being an organisation makes a listing appear differently in the catalog — the benefit is ownership, attribution and a badge.

When to use one

A solo developer with no plans to grow should not bother: an individual account does everything an organisation does except display a company name.

• More than one person will ever publish, edit or take money from these listings.
• The product is expected to outlive any individual's involvement.
• You need the verified badge because users ask who is behind a publisher name.
• Payouts must reach a company account rather than a person.

Setting one up

1. Register the account. Under a role alias — studio@yourcompany — not a personal mailbox. This is the single most important step, and it is irreversible without support.
2. Verify the address. The 6-digit code goes to that alias, so someone must own the inbox.
3. Set the display name to the legal entity. It becomes the publisher line on every listing; Trademark applies to it.
4. Get the entity verified. Ask [email protected] with the registration documents.
5. Add members. Least privilege first, see Roles and permissions.

Ownership and handover

The owner is whoever holds the login. There is no ownership-transfer form in Studio, so a handover is a support case and a documented one.

Practical rules: never let the owner be a single employee's personal address; keep the alias in your own password manager rather than an individual's; and record who can access it.

For removing the account entirely, see Delete developer account.