I had a question about the best way to purchase and manage licenses in an agency environment.
In our workflow, we sometimes have multiple developers working on projects depending on workload. Ideally, I’d like my company to manage the licenses centrally so we can maintain control and disable access if we stop working with a particular developer.
For agencies working with multiple developers, what’s the recommended approach? Should licenses be tied to individual developer accounts, or is it better to purchase them under company email addresses and manage them that way?
Just trying to make sure I set things up the right way from the beginning.
Either approach works, but if you want full control I’d recommend purchasing and using them under company email accounts, that way you can fully control them.
If you ever need us to disable a license (and issue a new one) because a developer left, you can drop support@realmacsoftware.com an email and we can sort that out for you.
@dan Would it be possible for me to purchase Essentials or other add-ons directly for our remote web developers, rather than having them buy individually and then managing reimbursements?
As I begin assigning more projects, I’d like to make sure One Eleven has enough licenses in place for everyone we work with, and streamline the process on our end.
Unfortunately not at this time, but “gifting” is something that would make a great addition to the store. I’ll add it to our internal list to be discussed further.
Thanks so much for your support, it’s awesome to hear Elements being used in an agency style environment.
On a side note, perhaps we could do a case study on your usage of Elements?
Hey @dan, really appreciate the thoughtful response. “Gifting” would honestly be a huge win for agencies like ours, so glad to hear it’s at least on the radar.
I’d definitely be open to a case study. We’ve been using RW since RW3 and lately been leaning pretty heavily into Elements as part of our workflow, especially around speeding up builds and keeping things consistent across projects, so happy to share how we’re using it.
