Purchasing Plugins for another account user

Thank You for your thorough and informative post @erinferinferinf 

I'll share it with our manager and agreed there probably a simpler way, even if it's just 'gift this plug-in'.

Basically, you can reach out to the developer for a coupon code, or email ccintrev@adobe.com to generate a code. Your manager can then purchase a coupon code for your coworker to use for installation.

This process may change in the future (I hope!) as we build out more marketplace tools.

I think the above should help. But what if you wanted to get the plugin for say, your entire team? Or your whole Enterprise? There are ways to do this currently, and, we're lacking documentation on this elsewhere, so I'll give some examples below:

How to sell paid plugins to Enterprises or Teams

1.        The customer reaches out to the developer saying how many plugin licenses they need for their teams or enterprise installation environment.
2.        The developer and customer agree on a price.
3.        The developer emails ccintrev@adobe.com and requests to generate a coupon code (or codes) for the negotiated price.
4.        The customer uses the code(s) to purchase the plugin.

Example A

Roy runs a small studio with eight artists and Creative Cloud Teams account. He reaches out to a plugin developer for eight coupons for the plugin for each artist in his studio. Each artist uses their own coupon code to install the plugin via the Creative Cloud Desktop app. (In this scenario, each coupon and plugin is associated with each artists’ AdobeID.)

Enterprise Deployments

Step four is different for large Enterprise deployments; If the customer wants to deploy via the Adobe Admin Console (or another packaging and deployment tool), they probably need an unencrypted version of the plugin (one that has never been uploaded to the Exchange Marketplace) to include in a deployment package.

Example B

Amanda is an Adobe Administrator for a college. She wants to deploy a plugin to 200 computers in a campus computer lab. She reaches out to the plugin developer and negotiates a price. The developer requests a coupon code. Amanda pays with the coupon. The developer then provides Amanda with an unencrypted ZXP or CCX file. Amanda bundles the file with her deployment of other Creative Cloud apps and deploys it to the entire computer lab using her deployment tool of choice. (In this scenario, the plugin is not associated with any specific AdobeID, as Amanda doesn’t know which students will sit at which computer in the lab.)