Overview
Spek supports App Store and Google Play connections for your own app listings. For App Store Connect, Settings, then Integrations, lists the accounts linked to this workspace.
App Store Connect
A connected account is named by the public seller name of the apps on that key, or by the label you gave it, always in uppercase. The key itself is never displayed, and neither are its Issuer or Key ID: they stay on Spek's servers.
Disconnect removes the stored credential. You can also revoke the key in App Store Connect, which takes effect immediately whatever Spek holds. Setting one up is covered in connect App Store Connect.
Common questions
Why can I not disconnect?
Changing a connection needs a role that allows it. The page says to contact an admin or editor when yours does not.
Confirm that you are looking at the intended workspace and connection before asking for an access change. Removing a store credential affects authenticated reads and writes for the relevant account; it should be coordinated separately from billing changes or a routine metadata review.
What happens to my drafts if I disconnect?
They stay. What stops is Spek's ability to read from or publish to that store account until you connect again.
What should I inspect when an integration needs attention?
Check which store account the connection represents, which apps depend on it and the message shown beside its status. A revoked key, changed provider access or an app outside the credential's account can require different remedies. Confirm the provider account before replacing any values. The integration label helps identify the connection without exposing its secret, so use that context in a support request and keep the private key, password and authentication tokens out of the message.
Can a workspace contain more than one store account?
The App Store Connect workflow can hold multiple connected keys, and an app remains associated with the account it was connected from. Keep the account labels recognizable and verify the app's connection before troubleshooting publishing or catalog access. Multiple connections should still represent a deliberate workspace ownership decision. They are not a reason to share one credential between unrelated clients, and adding an account does not merge its private key with the credentials already stored for the workspace.
What should I do before replacing a credential?
Identify the affected account and apps, check whether a current operation needs attention, and confirm that the replacement credential belongs to the intended provider account with the appropriate access. Keep the old and new secret material out of ordinary team messages. After the change, inspect the integration status and the relevant app access before assuming normal reads or writes have resumed. A new credential does not undo content already published or resolve an unrelated version-state requirement in App Store Connect.
Does disconnecting cancel my workspace subscription?
Store access and billing are separate concerns. Disconnecting an integration removes the credential used for the related authenticated store operations; it does not serve as a subscription cancellation control. Manage the workspace subscription in Billing using an authorized owner or admin account. Likewise, changing a billing plan should not be assumed to revoke a provider key. Review each action in the surface responsible for it so a team can intentionally manage store access, workspace membership and commercial access.