Skip to content

Cole Speelman

My feedback

1 result found

  1. 113 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Cole Speelman commented  · 

    This is what I came here to recommend. I can't believe a "developer" account or "agency" type account hasn't been implemented for a service of this type/scale.

    I'm finding myself adding domains to my own business account - breaking the arms length relationship I prefer to have with clients. They're now forced to change validation methods and API keys upon leaving our services.

    To add to the problem, if we need to change an API key, we're switching the key on 18+ domains for our one account. Having one account / API key per client would help immensely.

    If I *were* to help a small business client set up their account, I'd be forced to hold on to their password, or ask for that information whenever I need to log in, which is a terrible policy considering that passwords should be regularly changed. Adding to that complication is the fact that I can no longer recommend 2FA considering it would be an added hassle when logging in to a client's account.

    It only makes sense that for a developer oriented service, you would offer the ability to manage client accounts without needing billing/personal information access.

    Seriously considering other solutions as this is a real bummer for us. We don't send many emails, but mailgun's deliverability / validation is incredible. I just wish, every time I log in, that we had access to multiple accounts.

    Cole Speelman supported this idea  · 

Feedback and Knowledge Base