Allow applications to belong to an organization rather than an individual login

Currently applications are tied to the individual account of the person who created them. However in reality an application rarely belongs to an individual but rather an organization. I would like to see the ownership structure change so that should the individual whose login is tied the application leave an organization, the application is not orphaned and somebody else at the organization can easily take over the application.

 

At a minimum you should be able to transfer ownership between individuals but this I feel is somewhat of a half baked solution and I would rather see ownership tied to the organization.

  • David Zeidman
  • Jun 10 2016
  • Reviewed: Voting Open
Developer Account
  • Attach files
  • James Phillips commented
    January 10, 2022 11:13

    Our team has dealt with this by using a generic user account e.g. skyapiuser@ourdomain.com.


    The account is managed by our IT team, the development team is issued with the password, This means it's not tied to an individual user, also the 'modified by' fields show as 'skyapiuser@ourdomain.com' which helps the admin team understand when an integration process has changed the data.

    ×

    Attachments Open full size

  • Dan Bowman commented
    March 08, 2017 14:05

    Brief update on this item...

    We're still evaluating if/how we'd associate registered applications with organizations, instead of or in addition to the individual developer account. Please provide thoughts on the topic.

    In the meantime,

    1. We now have the ability to reassign an app from one developer account to another. In the event one of your developers leaves your organization, or you otherwise wish to transfer app ownership, contact Blackbaud Support with the developer and application details so we can process the reassignment.
    2. As a recommended practice, we advise organizations set up "org" SKY API developer accounts, using an alias/team mailbox account. You can then register and manage applications under this account, along with using the account's API subscription keys within your production apps.
    ×

    Attachments Open full size

  • Dan Bowman commented
    June 27, 2016 22:49

    Thanks David. We've heard this request from others, as it's something that'd be universally applicable to partners and customer org's. Our team is mulling ways to solve this problem. In meantime, I'd love to see others vote on this item and comment on any expectations you'd have for a solution, whether you've seen another API handle org's effectively, etc. 

    ×

    Attachments Open full size

Related ideas