Re: How to handle Enterprise and Standard Development account IDs?
Re: How to handle Enterprise and Standard Development account IDs?
- Subject: Re: How to handle Enterprise and Standard Development account IDs?
- From: Fritz Anderson <email@hidden>
- Date: Fri, 20 Nov 2015 15:23:37 -0600
Alex has contributed, but I worry about covering all the bases on this subject.
I juggle three developer memberships, all on the same Apple ID, plus two more program memberships for the business end. Here are the excruciating details.
The PER-HUMAN element in all this is _developer registration,_ which you can reach through a tiny link on developer.apple.com, or in the team-invitation process. This is an Apple ID (use an existing one if you like), some demographic information, and assent to terms and conditions. I think this comes with access to a few otherwise-controlled resources like the forums and Radar submissions, but I don’t remember. It’s a moving target.
The PER-DEVELOPER-PROGRAM-MEMBERSHIP element is the _team._ An individual program membership embraces a one-person team, and it’s easy to conflate registration (== Apple ID), membership, and team.
Organizational members have multiple-person teams, with three levels of privilege I won’t get into. Organizations share the benefits and authorizations that come with program membership among team members. The organization sends an invitation to a developer; accepting the invitation associates the developer’s per-human registration with that team.
The developer (person) registration can be associated with at most one individual membership, plus any number of organizational and Enterprise memberships.
Developer Program membership gets you access to the App Stores, but not in-house distribution. The Enterprise program gets you in-house distribution, but not the App Stores. My employer has both, and I’m on both teams.
I use a single developer ID to exercise my privileges with my personal, employer/App Store, and employer/Enterprise team memberships. At my level of privilege, I can register apps, create signatures and distribution profiles, and sign apps under the personal, organizational, or in-house identities. It’s meant to be nearly transparent, and it nearly is.
(I’m also one of those allowed the corporation’s own Apple IDs for top privilege, because nobody else wants to suffer the drizzle of renewals and contract amendments. Plus another for Deployment Programs. Each requires an additional (?) Apple ID, or at least one that isn’t a developer ID (?). That’s a separate issue, but make sure your people understand that somebody must manage agent-level access to Enterprise + App Store * [Developer + iTunes Connect].)
— F
> On 20 Nov 2015, at 7:56 AM, David Hoerl <email@hidden> wrote:
>
> I currently have a private development account using my personal Apple ID, and a separate Apple ID for my company's Enterprise account.
>
> The company now wants to distribute an iOS app through the iOS App Store. I'm going to guess that the best way to handle this is to create yet a third Apple ID for creating this new account, but unsure.
>
> If I do what do I do about an email address - get my company to create an alias for me - or use a GMAIL address etc?
>
> Curious how others have dealt with this.
>
> - David
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden