Overview: Working Safely Across Multiple Developer Teams
Many iOS developers, consultants, and agencies manage applications across multiple Apple Developer teams—for example, balancing personal indie apps, client organization accounts, and corporate enterprise pipelines.
Managing multiple teams with AI assistants introduces a serious risk: cross-account accidental mutations. If an AI coding assistant is asked to update metadata or attach a TestFlight build without explicit account context, it could inadvertently target the wrong organization's application.
FlightDeck implements a strict single-active-profile architecture:
- Isolated Connection Profiles: You can register unlimited Apple Developer profiles in FlightDeck Desktop. Each profile has its own Key ID, Issuer ID, and private key stored in an isolated macOS Keychain record.
- One Active Context at a Time: FlightDeck's MCP server routes all incoming assistant requests strictly through the currently active profile. There is no automatic multi-tenant data merging or cross-account leakage.
- Explicit Profile Switching: Switching accounts is performed intentionally in the FlightDeck Desktop interface. Before staging mutations, your assistant can confirm the active organization name and bundle identifier.
Adding Connection Profiles in FlightDeck Desktop
To add an account profile for a team or client:
┌────────────────────────────────────────────────────────┐
│ Add Connection Profile (FlightDeck Desktop) │
├──────────────────────┬─────────────────────────────────┤
│ Display Name │ Acme Corp Production │
│ API Key Type │ Team API Key (Recommended) │
│ Key ID (kid) │ 2X9R427ADR │
│ Team ID │ 9876543210 (Optional 10-char) │
│ Issuer ID (iss UUID) │ 57246542-96fe-1a63-e053-... │
│ .p8 Private Key │ -----BEGIN PRIVATE KEY----- ... │
└──────────────────────┴─────────────────────────────────┘
Step-by-Step Profile Addition
- Open FlightDeck Desktop.
- Navigate to Settings > Connection Profiles.
- Click Add Profile (
+). - Enter an unambiguous Display Name (e.g., "Acme Corp Production" or "Personal Indie Apps").
- Select the API Key Type: - Team API Key (Recommended): Created in the organization's portal by an Account Holder or Admin. Requires Key ID, Issuer ID, and
.p8key. Grants access to all team apps, builds, and TestFlight groups. - Individual API Key: Bound to a single Apple ID. Does not require an Issuer ID, but cannot access financial, sales, or certificate provisioning endpoints. - Paste the
.p8private key PEM text. - Click Save & Store in Keychain. FlightDeck writes the secret material directly into your encrypted macOS Keychain under service
quest.kip.flightdeck.keys.
Switching Between Developer Teams Safely
Because FlightDeck connects to one active profile at a time, switching accounts is quick and deterministic:
1. Switch the Active Profile in Desktop UI
In the FlightDeck Desktop header or Settings > Connection Profiles, select the desired team profile from the account dropdown. FlightDeck immediately switches its internal signing context to the new profile's Keychain entry.
2. What Happens to Pending Proposals During a Profile Switch?
FlightDeck enforces strict cryptographic profile binding on all staged mutations:
- When your assistant stages an operation (such as modifying localized keywords or creating a beta group), the staging record permanently records the
connectionProfileIdof the profile that was active at that moment. - If you subsequently switch the active profile in the Desktop UI to another team, attempting to approve the pending proposal will be hard-rejected by FlightDeck's safety engine with an
AuthorizationBoundaryViolationException: PROFILE_MISMATCH(Profile binding violation: staged against "Team A", but approval attempted with "Team B"). - An operation cannot accidentally execute against the wrong Apple Developer team credentials.
- Recommended Best Practice: Always resolve (approve or reject) all pending proposals in the Approval Center before switching connection profiles. Never switch profiles while multi-step change sets or background uploads are actively in flight.
3. Verify the Active Account via AI Prompt
Before asking your assistant to perform any tasks on behalf of the newly selected team, run this read-only confirmation prompt:
Using FlightDeck, check which App Store Connect account profile is currently active. Show me the profile display name, key type, and list the first 3 apps visible in this account. Do not make any changes or stage any mutations.
What FlightDeck Executes
The assistant executes apps_list over loopback MCP. FlightDeck signs a short-lived ES256 JWT using the newly active profile's credentials, queries Apple, and returns only the apps belonging to that organization.
Guarding Against Cross-Team Mutations
To guarantee that mutations never touch the wrong organization's app, follow this two-factor verification pattern:
Factor 1: Include App Name AND Bundle ID in Prompts
Never issue generic prompts like "Update the description of my app." Instead, explicitly qualify the target:
Using FlightDeck, check the editable App Store version draft for 'Acme Tasks' (bundle ID: com.acme.tasks). Update the English marketing URL to 'https://acme.com/tasks'. Confirm that the active profile belongs to Acme Corp before staging.
Factor 2: Inspect the Approval Center Card
When the assistant stages a mutation, FlightDeck's native macOS Approval Center pops up a visual review card. The card explicitly displays:
- The Active Profile Display Name (e.g., "Acme Corp Production").
- The App Name and Apple App ID.
- The Bundle Identifier.
- The exact proposed before-and-after values.
If you notice that the active profile is your personal account rather than the client team, simply click Reject in the Approval Center. The mutation is discarded locally with zero side effects on Apple.
Diagnosing Missing Apps Across Accounts
If an application does not appear when running apps_list, check the following common causes:
| Cause | Diagnostic Indicator | Remediation Action |
|---|---|---|
| Wrong Profile Active | apps_list returns apps from your personal account instead of the client team. |
Open FlightDeck Desktop and select the client profile from the account selector dropdown. |
| Restricted API Key Role | App exists in portal, but apps_list returns empty or HTTP 403 Forbidden. |
Check the key role in Apple portal (Users and Access > Integrations). Ensure the key has Admin or App Manager role. Keys with Developer or Marketing roles cannot access all metadata endpoints. |
| Individual Key on Team App | Key was generated under "Individual Keys" rather than "Team Keys". | Individual keys cannot manage team-owned applications. Request that the team Admin generate a Team API Key. |
| App Record Not Created Yet | New app has been coded in Xcode, but never created in App Store Connect. | Initial App Record creation must be performed once in the Apple web portal (My Apps > + > New App). FlightDeck can only discover apps that have a registered App ID. |
Removing and Revoking Profiles Safely
When offboarding a client or decommissioning a development team:
- Delete from FlightDeck Desktop: Go to Settings > Connection Profiles, select the profile, and click Delete Profile. FlightDeck executes
SecItemDeleteon the macOS Keychain, permanently purging the.p8private key from your Mac. - Revoke in Apple Portal: If you created the key, navigate to Users and Access > Integrations > App Store Connect API in Apple's portal, find the Key ID, and click Revoke. Apple instantly invalidates the key.
Related Guides
- Team API Keys vs Individual API Keys: Permissions and Setup Guide — Deep dive into Apple credential roles.
- App Store Connect API Keys Guide: Generating Team Keys for AI Agents — Step-by-step key creation in the Apple portal.
- Human-in-the-Loop Governance & FlightDeck Approval Center — Inspecting diff cards before authorizing writes.
- Troubleshooting MCP Connection Errors — Diagnosing authentication and profile errors.