Connecting a store and permissions
What Kobold asks for when you install it, and what it will never touch.
What Kobold asks for
Kobold is installed as a Shopify app with these access scopes:
| Scope | Why |
|---|---|
read_themes | Read your live theme so the agents understand how it is built. |
write_themes | Create and edit a copy of your theme (kobold-NNNN), and publish it only after you approve. |
read_translations | Read the text to translate and the translations you already have, so Kobold never overwrites them. |
write_translations | Add translations you approved, or that auto-translate adds for a language an owner set to apply automatically. Kobold never changes your original content. |
read_locales | See which languages you've added in Shopify. |
read_products | For auto-translate: Shopify tells Kobold when a product or collection is added or changed, so it can translate the new text. The permission also covers product details like prices and stock, and Shopify's change notice includes them: Kobold uses the notice only to know which product changed, and doesn't store those details. |
read_content | For auto-translate: see which pages and blog posts changed since the last check. Also lets Kobold read the metafields of pages and blog posts you choose to translate. |
read_metaobjects | For metafield translation: read the entries of metaobjects whose fields you choose to translate. |
read_metaobject_definitions | For metafield translation: list your metaobject definitions and their fields, so you can choose which ones Kobold translates. |
In plain words: Read your theme · Write to a copy only · Read and add translations · Publish only with your OK · Never checkout, payments or customer data. No other scopes are requested. Kobold never creates or edits products, collections, pages, blog posts, metafields or metaobjects: read_products, read_content, read_metaobjects and read_metaobject_definitions are read-only. Translations of the metafields you choose are added next to the original, like any other translation.
Stores connected before translations
Stores connected before October 2026 only granted the two theme scopes. Theme work keeps working; translations wait until a workspace owner approves the three new permissions in Shopify (Approve translation access, which reopens Shopify's permission screen). See Translations.
Stores that approved translations before 7 October 2026 haven't granted read_products and read_content yet. Translating by hand keeps working; only auto-translate waits, and the Translations page shows Approve 2 Shopify permissions for auto-translate with Approve in Shopify for owners.
Stores that approved Kobold's permissions before metafield translation arrived haven't granted read_metaobjects and read_metaobject_definitions yet. Everything else keeps working; the Translations page's Metafields tab shows Approve access to metafields with Approve in Shopify for owners until they're approved.
Installing from Shopify
You can also start from Shopify: install Kobold from the Shopify App Store or open it from your Shopify admin. Kobold recognizes the store and takes you to Shopify's permission screen first. If you're not signed in to Kobold, it then signs you in with the email of your Shopify login, or creates your Kobold account with it, and starts connecting the store. If Shopify hasn't verified that email, or you work on the store through a collaborator account, Kobold asks you to sign in or sign up instead, with the email filled in. You don't type the store address. If the store is already connected, Kobold opens it, or, for someone who isn't in its workspace, offers to ask for access (below).
When a teammate opens Kobold from Shopify
Once a store is connected, other people on the store's Shopify staff may open Kobold from the Shopify admin too. Shopify confirms who they are first, the same way as when you installed.
- Already in your workspace: they're signed straight in to the store.
- Not in it yet: they can press Request access. The page only shows the store's name, never your workspace's name, your name or your email. Each owner of the workspace gets an email, and the request waits at the top of Settings → Team & roles.
- Add sends them the usual team invite with the role you pick (Developer unless you change it). Like any invite, it holds a seat until they accept. When all your seats are in use, Add is off until you remove someone or, on Starter, move to Growth. On Growth, use Email us about more seats.
- Decline sends nothing. They can ask again after 14 days. A request nobody answers also drops off the list after 14 days.
Requests only come from someone who opens Kobold from the store's own Shopify admin. Typing the address of a connected store on Connect store doesn't send one.
On a store an agency connected, people from the store's own team see No access to this store and can't ask to join. The agency's seats and credits stay with the agency.
More than one store or workspace
You can be in more than one workspace, for example one per store you run, or your own plus a client's that invited you. The workspace name next to the Kobold logo opens a menu of your workspaces with their plans. Pick one to switch to it, or choose New workspace to set up another one; the workspace you're in stays as it is. When you open Kobold from a store's Shopify admin, it opens the workspace that holds that store.
Starter and Growth cover one store. If you're the owner of a store workspace on one of them and you connect or install Kobold on another store, Kobold gives that store its own workspace: a new workspace with its own plan, credits and team. You're its owner, and you pick its plan after Kobold reads the theme. If you already had a free trial, its plan starts right away.
Anyone else at the store limit, including an Agency workspace with all its stores connected, sees Email us about more stores, which writes to hello@usekobold.com.
Theme access
Kobold doesn't need a Theme Access password. Shopify approved Kobold's theme access, so the app you install is all it needs to create and edit copies of your theme, and onboarding goes straight from the Shopify install to reading your theme.
If you saved a Theme Access password for a store earlier, Kobold no longer uses it. You can remove it under Store settings → Storefront access → Theme writes, and you can delete it in Shopify's Theme Access app too.
How copies work
Each task gets its own duplicate of your live theme, named like kobold-0412. Nib only ever writes to that copy; Kobold's Shopify client refuses any write to the theme that is currently live. Shopify allows 20 themes per store, so Kobold cleans up the copies it created:
- Published: the theme it replaced stays for rollback for 30 days, but only the two most recent ones are kept. Older ones are deleted.
- Cancelled or discarded: the copy is deleted 7 days later (a discarded canvas copy right away).
- Left waiting: a task that waits for 30 days with nothing happening (no messages, no open approval link) is cancelled, and its copy is deleted. Paused tasks and tasks your client already approved are never cancelled this way.
- Leftovers: once a day, and before Kobold ever says your store is full, it deletes any of its own copies it no longer tracks.
Kobold never deletes your live theme, your original theme, or a theme it didn't make.
If your live theme is edited in the Shopify admin while a task is waiting for approval, Kobold notices before publishing. You can re-apply the change to a fresh copy (recommended) or publish anyway, which is recorded in the audit log.
Supported themes
Kobold works with Horizon, Dawn and most Online Store 2.0 themes: themes that use JSON templates, sections and blocks. When you connect, Kobold reads the theme and tells you if something isn't supported, for example a vintage (1.0) theme or files it can't parse.
Password-protected stores
If your storefront has a password, Moss needs it to test the preview. Kobold checks for one right after the Shopify install and asks for it on the Read theme step. Starting a new task on a protected store without a working password shows a card above the composer where you can add it. You can add or change it any time under Store settings → Storefront access. Kobold tests the password before saving and refuses one that doesn't open the storefront. Owners and developers can add it; approvers see who to ask.
You can start a task without it. If Moss reaches testing and no working password is saved, the task pauses with an Add password banner and no credits are spent. As soon as you save the password, testing continues. The password is encrypted and only used by the QA browser.
Reconnecting a store
If Shopify stops accepting Kobold's access (for example the app was reinstalled or its access was revoked), the store page shows a red Reconnect on Shopify banner. One click takes you to Shopify to approve Kobold again, and the store comes back with its tasks and history. If the Kobold app was removed from the store, the banner says so and offers Reinstall. Kobold checks every few hours and clears the warning by itself once Shopify answers again. Until then, Re-read theme is off and Store settings shows Reconnect Shopify in its place.
Kobold's access to your store renews itself (Shopify's access keys expire after an hour and Kobold refreshes them in the background), so you don't need to reconnect from time to time. If the store isn't used for about three months, Shopify lets the renewal lapse and the store asks you to reconnect once.
Disconnecting
Uninstall Kobold from Shopify, or disconnect the store from Settings → Stores. Auto-translate turns off for every language right away. Kobold deletes that store's memory, rules and theme index after 30 days. Theme copies stay in your Shopify theme library until you remove them.
If this store pays for your Starter or Growth plan, uninstalling ends the plan in Shopify. You keep access until the end of the paid period; reinstall to approve it again. To keep the plan, Move billing to another store first. Kobold won't disconnect a store that pays for the plan, or one with an approval still open.