@aglyn/aglyn 1.12.0 → 1.13.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (54) hide show
  1. package/package.json +11 -11
  2. package/src/lib/app-utils/docs-help-sections.generated.js +8 -2
  3. package/src/lib/app-utils/docs-help-sections.generated.js.map +1 -1
  4. package/src/lib/app-utils/docs-help.generated.d.ts +1 -1
  5. package/src/lib/app-utils/docs-help.generated.js +7 -0
  6. package/src/lib/app-utils/docs-help.generated.js.map +1 -1
  7. package/src/lib/app-utils/docs-index.generated.js +44 -30
  8. package/src/lib/app-utils/docs-index.generated.js.map +1 -1
  9. package/src/lib/app-utils/host-permissions.d.ts +12 -0
  10. package/src/lib/app-utils/host-permissions.js +26 -1
  11. package/src/lib/app-utils/host-permissions.js.map +1 -1
  12. package/src/lib/app-utils/media-asset-facts.d.ts +2 -2
  13. package/src/lib/app-utils/media-asset-facts.js +4 -3
  14. package/src/lib/app-utils/media-asset-facts.js.map +1 -1
  15. package/src/lib/app-utils/media-cdn-scope.d.ts +19 -4
  16. package/src/lib/app-utils/media-cdn-scope.js +19 -5
  17. package/src/lib/app-utils/media-cdn-scope.js.map +1 -1
  18. package/src/lib/app-utils/media-ref.d.ts +10 -6
  19. package/src/lib/app-utils/media-ref.js +34 -8
  20. package/src/lib/app-utils/media-ref.js.map +1 -1
  21. package/src/lib/app-utils/org-permissions.d.ts +7 -0
  22. package/src/lib/app-utils/org-permissions.js +2 -0
  23. package/src/lib/app-utils/org-permissions.js.map +1 -1
  24. package/src/lib/app-utils/org-role-grants.d.ts +7 -0
  25. package/src/lib/app-utils/org-role-grants.js +7 -5
  26. package/src/lib/app-utils/org-role-grants.js.map +1 -1
  27. package/src/lib/app-utils/scope-tokens.d.ts +132 -3
  28. package/src/lib/app-utils/scope-tokens.js +276 -3
  29. package/src/lib/app-utils/scope-tokens.js.map +1 -1
  30. package/src/lib/app-utils/site-placement.d.ts +56 -0
  31. package/src/lib/app-utils/site-placement.js +88 -0
  32. package/src/lib/app-utils/site-placement.js.map +1 -0
  33. package/src/lib/app-utils/transfer-launcher-context.d.ts +17 -1
  34. package/src/lib/app-utils/transfer-launcher-context.js.map +1 -1
  35. package/src/lib/data-transfer/access.d.ts +10 -18
  36. package/src/lib/data-transfer/access.js +21 -25
  37. package/src/lib/data-transfer/access.js.map +1 -1
  38. package/src/lib/data-transfer/resource.d.ts +13 -14
  39. package/src/lib/data-transfer/resource.js +9 -10
  40. package/src/lib/data-transfer/resource.js.map +1 -1
  41. package/src/lib/plugin-manager/first-party-plugins.generated.js +3 -4
  42. package/src/lib/plugin-manager/first-party-plugins.generated.js.map +1 -1
  43. package/src/lib/plugin-manager/plugin-entitlements.d.ts +12 -0
  44. package/src/lib/plugin-manager/plugin-entitlements.js +3 -1
  45. package/src/lib/plugin-manager/plugin-entitlements.js.map +1 -1
  46. package/src/lib/plugin-manager/plugin-scope-sharing.d.ts +52 -0
  47. package/src/lib/plugin-manager/plugin-scope-sharing.generated.d.ts +10 -0
  48. package/src/lib/plugin-manager/plugin-scope-sharing.generated.js +82 -0
  49. package/src/lib/plugin-manager/plugin-scope-sharing.generated.js.map +1 -0
  50. package/src/lib/plugin-manager/plugin-scope-sharing.js +85 -0
  51. package/src/lib/plugin-manager/plugin-scope-sharing.js.map +1 -0
  52. package/src/lib/plugin-manager/plugin-transfer-resources.d.ts +56 -1
  53. package/src/lib/plugin-manager/plugin-transfer-resources.js +13 -0
  54. package/src/lib/plugin-manager/plugin-transfer-resources.js.map +1 -1
@@ -429,7 +429,7 @@ export const DOCS_SECTION_INDEX = [
429
429
  title: 'Build from Assist chat',
430
430
  heading: 'When a build makes your site a store',
431
431
  anchor: '#a-store',
432
- text: 'When you ask Assist to add a shop or make this a store, and the build makes products, a product page template or a Shop page, it also adds the pages every store needs. It adds only the ones your site does not already have:\n- Your account at /account, where shoppers sign in, see their orders and find what they saved;\n- Your cart at /cart;\n- Shipping & returns, Privacy policy and Terms of sale, as drafts with the details only you know left in [brackets] for you to fill in.\nA page you already have stands in for its store page, at its own address or by what it is called. For example, an existing Privacy Policy page at /privacy-policy is used, and no second one is added. The plan card lists the pages it will add as added for your store automatically. They are built without AI and use no credits. The account and cart pages are hidden from search engines. Your site\'s user accounts are turned on so that shoppers can sign in, unless you turned them off.\nThe header links the account page, and the cart page too if the header has no cart. The footer links the account and policy pages. If the build makes a header and footer, they come with these links. If it doesn\'t, Aglyn adds them to your site\'s existing layout as a new draft version. Links already there are not added again. The version you have live is not changed: the new one goes live when the build publishes, or when you publish it. If your header or footer has no list of links to add to, the layout is left as it is, and Finish your store asks you to add the links yourself.\nThis needs a plan that includes a store, with Commerce on for the site, and the editor role. When the build is done, the card shows Finish your store: connect payments, review your products, set shipping and tax, and fill in your policies. The payments step'
432
+ text: 'When you ask Assist to add a shop or make this a store, and the build makes products, a product page template or a Shop page, it also adds the pages every store needs. It adds only the ones your site does not already have:\n- Your account at /account, where shoppers sign in, see their orders and find what they saved;\n- Your cart at /cart;\n- Shipping & returns, Privacy policy and Terms of sale, as drafts with the details only you know left in [brackets] for you to fill in.\nA page you already have stands in for its store page, at its own address or by what it is called. For example, an existing Privacy Policy page at /privacy-policy is used, and no second one is added. The plan card lists the pages it will add as added for your store automatically. They are built without AI and use no credits. The account and cart pages are hidden from search engines. Your site\'s user accounts are turned on so that shoppers can sign in, unless you turned them off.\nThe header links the account page, and the cart page too if the header has no cart. The footer links the account and policy pages. If the build makes a header and footer, they come with these links. If it doesn\'t, Aglyn adds them to your site\'s existing layout as a new draft version. Links already there are not added again. The version you have live is not changed: the new one goes live when the build publishes, or when you publish it. If your header or footer has no list of links to add to, the layout is left as it is, and Finish your store asks you to add the links yourself.\nThis needs a plan that includes a store, with Commerce on for the site, and the Edit site content permission. When the build is done, the card shows Finish your store: connect payments, review your products, set shipping and tax, and fill in your policies. '
433
433
  },
434
434
  {
435
435
  path: '/ai/assist-builds',
@@ -800,7 +800,7 @@ export const DOCS_SECTION_INDEX = [
800
800
  title: 'Create with AI on every list',
801
801
  heading: 'On every plan',
802
802
  anchor: '#without-the-add-on',
803
- text: 'On every paid plan, Create with AI runs on the AI credits your plan includes each month; nothing else needs to be bought. Blocks of AI credits add more on top when you need them, and a member holding Manage billing adds them in Billing.\nA Free workspace\'s buttons work from the 300 AI credits it gets each month.\nIf Create with AI is switched off for your workspace, the button is still there and opens a short window saying what it would make:\n- a member holding Manage billing sees Add Aglyn AI, which opens Billing to choose a tier, or Not now;\n- anyone else is asked to have a workspace owner or admin choose one.'
803
+ text: 'On every paid plan, Create with AI runs on the AI credits your plan includes each month; nothing else needs to be bought. Blocks of AI credits add more on top when you need them, and a member holding Manage billing adds them in Billing.\nA Free workspace\'s buttons work from the 300 AI credits it gets each month.\nIf Create with AI is switched off for your workspace, the button is still there and opens a short window saying what it would make:\n- a member holding Manage billing sees Add Aglyn AI, which opens Billing to choose a tier, or Not now;\n- anyone else is asked to have a member holding Manage billing choose one.'
804
804
  },
805
805
  {
806
806
  path: '/ai/create-with-ai',
@@ -5077,7 +5077,7 @@ export const DOCS_SECTION_INDEX = [
5077
5077
  title: 'Fulfillment networks (ShipBob, ShipMonk, Flexport and Amazon MCF)',
5078
5078
  heading: 'Connect a network',
5079
5079
  anchor: '#connect-a-network',
5080
- text: '1. Open Products → Shipping & delivery and find the Fulfillment networks card.\n2. Next to ShipBob or Amazon Multi-Channel Fulfillment (when the card offers them), select Connect.\n3. Sign in to that account and allow Aglyn access. You come back to the store settings with the network connected.\nYou need to be an admin of the site to connect, change or disconnect a network. Aglyn never sees your ShipBob or Amazon password; it keeps only the access the network grants, encrypted.\nShipMonk: connect with your API key\nShipMonk connects with an API key from your own ShipMonk account instead of a sign-in:\n1. In ShipMonk, open Account Settings, then Integration API Keys. If you have no API store yet, ShipMonk sets one up for you when you ask under Stores.\n2. Create an API key for your API store, and note the store\'s id shown beside it.\n3. On Products → Shipping & delivery, select Connect ShipMonk, paste the key, enter the store id and select Connect.\nAglyn checks the key with ShipMonk before keeping it, keeps it encrypted, and never shows it again. To use a new key, revoke the old one in ShipMonk: the card asks you to Connect again, and you paste the new one.\nAfter you connect, the card shows a webhook address and a signing secret, once. Give both to ShipMonk (its webhook settings under Integrations, or ShipMonk support) so it tells Aglyn the moment an order ships. Aglyn checks every webhook\'s signature and ignores any that does not match. Without webhooks, Aglyn still reads each order back from ShipMonk every 15 minutes. New webhook secret makes a new secret and ends the old one at once.\nFlexport: connect with your API token\nFlexport connects with an API token from your own Flexport account. You need a Flexport account with billing set up, since Flexport ships orders only for acc'
5080
+ text: '1. Open Products → Shipping & delivery and find the Fulfillment networks card.\n2. Next to ShipBob or Amazon Multi-Channel Fulfillment (when the card offers them), select Connect.\n3. Sign in to that account and allow Aglyn access. You come back to the store settings with the network connected.\nConnecting, changing or disconnecting a network takes Manage fulfillment network connections, which a site\'s admins hold by default (custom roles). Aglyn never sees your ShipBob or Amazon password; it keeps only the access the network grants, encrypted.\nShipMonk: connect with your API key\nShipMonk connects with an API key from your own ShipMonk account instead of a sign-in:\n1. In ShipMonk, open Account Settings, then Integration API Keys. If you have no API store yet, ShipMonk sets one up for you when you ask under Stores.\n2. Create an API key for your API store, and note the store\'s id shown beside it.\n3. On Products → Shipping & delivery, select Connect ShipMonk, paste the key, enter the store id and select Connect.\nAglyn checks the key with ShipMonk before keeping it, keeps it encrypted, and never shows it again. To use a new key, revoke the old one in ShipMonk: the card asks you to Connect again, and you paste the new one.\nAfter you connect, the card shows a webhook address and a signing secret, once. Give both to ShipMonk (its webhook settings under Integrations, or ShipMonk support) so it tells Aglyn the moment an order ships. Aglyn checks every webhook\'s signature and ignores any that does not match. Without webhooks, Aglyn still reads each order back from ShipMonk every 15 minutes. New webhook secret makes a new secret and ends the old one at once.\nFlexport: connect with your API token\nFlexport connects with an API token from your own Flexport account. You need a Flexport a'
5081
5081
  },
5082
5082
  {
5083
5083
  path: '/commerce-and-bookings/commerce/fulfillment-networks',
@@ -5133,7 +5133,7 @@ export const DOCS_SECTION_INDEX = [
5133
5133
  title: 'Help desks (Gorgias, Re:amaze, Kustomer, Gladly and Richpanel)',
5134
5134
  heading: 'Before you start',
5135
5135
  anchor: '#before-you-start',
5136
- text: '- Role: you need to be an admin of the site to connect, change or disconnect a help desk. Editors can see the card and the sync log.\n- Verified email: verify your email address first.\n- A plan that includes your store. Help desks carry your buyers and their orders, so they come with the plans that include selling.\n- Your help desk\'s API credentials, listed for each help desk below.'
5136
+ text: '- Permission: connecting, changing or disconnecting a help desk takes Manage help desk connections, which a site\'s admins hold by default. Seeing the card and the sync log takes See help desk connections, which a site\'s admins and editors hold by default. See custom roles.\n- Verified email: verify your email address first.\n- A plan that includes your store. Help desks carry your buyers and their orders, so they come with the plans that include selling.\n- Your help desk\'s API credentials, listed for each help desk below.'
5137
5137
  },
5138
5138
  {
5139
5139
  path: '/commerce-and-bookings/commerce/help-desks',
@@ -5196,7 +5196,7 @@ export const DOCS_SECTION_INDEX = [
5196
5196
  title: 'Inventory and ERP sync (Cin7 Core, inFlow, Brightpearl, Ordoro)',
5197
5197
  heading: 'Connect a system',
5198
5198
  anchor: '#connect-a-system',
5199
- text: 'You need to be an admin of the site to connect, change or disconnect a system.\n1. Open Products → Integrations and find the Inventory and ERP card.\n2. Connect the system you use:\n- Cin7 Core: in Cin7 Core, go to Integrations → API and add an API application. Paste its Account ID and Application key into the card and select Connect Cin7 Core.\n- inFlow: in inFlow, go to Options → Integrations and generate an API key (your inFlow plan needs the API access add-on). Paste the Company ID and API key and select Connect inFlow Inventory.\n- Brightpearl: enter your Brightpearl account code (the name in your Brightpearl address) and select Connect Brightpearl. Sign in to Brightpearl and allow access; you come back to Integrations with it connected.\n- Ordoro: in Ordoro, go to Account Settings → API Keys, add an API key and select Edit beside it. Paste its Client ID and Client secret and select Connect Ordoro. Ordoro\'s API is available on its Premium plan and above.\nKeys are checked with the system before they are saved, and stored encrypted. They are never shown again. Aglyn never sees your Brightpearl password.\nWhen you connect, nothing is synced until you choose what to sync below.'
5199
+ text: 'Connecting, changing or disconnecting a system takes Manage the inventory connection, which a site\'s admins hold by default (custom roles).\n1. Open Products → Integrations and find the Inventory and ERP card.\n2. Connect the system you use:\n- Cin7 Core: in Cin7 Core, go to Integrations → API and add an API application. Paste its Account ID and Application key into the card and select Connect Cin7 Core.\n- inFlow: in inFlow, go to Options → Integrations and generate an API key (your inFlow plan needs the API access add-on). Paste the Company ID and API key and select Connect inFlow Inventory.\n- Brightpearl: enter your Brightpearl account code (the name in your Brightpearl address) and select Connect Brightpearl. Sign in to Brightpearl and allow access; you come back to Integrations with it connected.\n- Ordoro: in Ordoro, go to Account Settings → API Keys, add an API key and select Edit beside it. Paste its Client ID and Client secret and select Connect Ordoro. Ordoro\'s API is available on its Premium plan and above.\nKeys are checked with the system before they are saved, and stored encrypted. They are never shown again. Aglyn never sees your Brightpearl password.\nWhen you connect, nothing is synced until you choose what to sync below.'
5200
5200
  },
5201
5201
  {
5202
5202
  path: '/commerce-and-bookings/commerce/inventory-and-erp-sync',
@@ -5343,7 +5343,7 @@ export const DOCS_SECTION_INDEX = [
5343
5343
  title: 'Commerce',
5344
5344
  heading: 'Gift cards & store credit',
5345
5345
  anchor: '#gift-cards',
5346
- text: 'Gift cards lists every card your store has issued, what is left on each one, and what that adds up to. Pro plan and up.\nCards arrive two ways:\n- A shopper buys one. A gift-card purchase mints a card with a code at the moment the payment settles.\n- You issue one by hand. Enter an amount and, optionally, an email address and the code is created and mailed to that person. This is the goodwill gesture and the service-recovery path — a refund you would rather keep as store credit.\n- You import them. Moving from another platform, Import issues one card per row of a file, under the codes your shoppers already hold, once you have typed back the total. Owners and admins only. See Import and export store data.\nBalances apply automatically at checkout; a shopper enters the code and the card is drawn down by what the order uses. Search by code or email finds a card anywhere in the list, not only on the page in front of you: type the start of its code (with or without GC-) or a word of the recipient\'s address. Search matches one word at a time and reads the first 12 characters of it.\nOutstanding balance is a liability, not revenue The outstanding total at the top is money customers have already paid you and have not yet spent. It is store credit you owe against future orders, and it belongs on the liability side of your books — not in a sales figure. Cards are counted at zero or above, so a card that has somehow gone negative cannot flatter that total downward.\nVoiding a card zeroes whatever is left on it. The holder can no longer redeem it and the action cannot be undone, so you are asked to confirm the remaining amount first.'
5346
+ text: 'Gift cards lists every card your store has issued, what is left on each one, and what that adds up to. Pro plan and up.\nCards arrive two ways:\n- A shopper buys one. A gift-card purchase mints a card with a code at the moment the payment settles.\n- You issue one by hand. Enter an amount and, optionally, an email address and the code is created and mailed to that person. This is the goodwill gesture and the service-recovery path — a refund you would rather keep as store credit.\n- You import them. Moving from another platform, Import issues one card per row of a file, under the codes your shoppers already hold, once you have typed back the total. Importing takes a workspace owner or admin, or an admin of the site. See Import and export store data.\nBalances apply automatically at checkout; a shopper enters the code and the card is drawn down by what the order uses. Search by code or email finds a card anywhere in the list, not only on the page in front of you: type the start of its code (with or without GC-) or a word of the recipient\'s address. Search matches one word at a time and reads the first 12 characters of it.\nOutstanding balance is a liability, not revenue The outstanding total at the top is money customers have already paid you and have not yet spent. It is store credit you owe against future orders, and it belongs on the liability side of your books — not in a sales figure. Cards are counted at zero or above, so a card that has somehow gone negative cannot flatter that total downward.\nVoiding a card zeroes whatever is left on it. The holder can no longer redeem it and the action cannot be undone, so you are asked to confirm the remaining amount first.'
5347
5347
  },
5348
5348
  {
5349
5349
  path: '/commerce-and-bookings/commerce/overview',
@@ -5777,7 +5777,7 @@ export const DOCS_SECTION_INDEX = [
5777
5777
  title: 'Quotes',
5778
5778
  heading: 'Make a quote',
5779
5779
  anchor: '#make-a-quote',
5780
- text: '1. On the Orders tab, choose New quote in the Quotes card.\n2. Find the customer in your contacts, or type their details.\n3. Choose Add product or Add custom item for each line, and set its quantity.\n4. Add a discount, shipping, the addresses, notes and terms as you need them.\n5. Choose Create quote.\nThe quote gets the next number from your store\'s order numbers and is listed as Quote #1042, for example. Choose a quote in the list to open it again; change anything and choose Save. A draft quote you no longer need can be deleted.\nThe list shows each quote\'s customer, total, status and when it last changed, and sorts by any column.'
5780
+ text: '1. On the Orders tab, choose New quote in the Quotes card.\n2. Find the customer in your contacts, or type their details.\n3. Choose Add product or Add custom item for each line, and set its quantity.\n4. Add a discount, shipping, the addresses, notes and terms as you need them.\n5. Choose Create quote.\nSending a design before it has a price? See Send a proof before it has a price.\nThe quote gets the next number from your store\'s order numbers and is listed as Quote #1042, for example. Choose a quote in the list to open it again; change anything and choose Save. A draft quote you no longer need can be deleted.\nThe list shows each quote\'s customer, total, status and when it last changed, and sorts by any column.'
5781
5781
  },
5782
5782
  {
5783
5783
  path: '/commerce-and-bookings/commerce/quotes-and-proofs',
@@ -5819,7 +5819,7 @@ export const DOCS_SECTION_INDEX = [
5819
5819
  title: 'Quotes',
5820
5820
  heading: 'What your customer gets',
5821
5821
  anchor: '#quote-email',
5822
- text: 'One email in your site\'s look, from your site\'s name, with:\n- Your quote from your business name as its heading, or Your updated quote when it\'s a new revision of a quote you already emailed (the first email you send for a quote, and sending the same revision again, keep Your quote from);\n- your message;\n- the quote number, its revision and its total;\n- the first three proof images, each opening the quote page, and the other proof files by name, to see on the quote page (a WebP image is named rather than shown, because some inboxes can\'t show one);\n- what to do next, and one button:\n- Review and approve while the proof must be approved before paying and isn\'t yet;\n- otherwise View and pay with the total;\n- the quote attached as a PDF, the same one as Download PDF, with the pay link on it.\nThe button opens the quote\'s pay link. Replies go to the Email in your site\'s Business details, and to your own email when your site has none. The email ends with a line saying so.\nThe email is the Quote email under Emails, where you can change its wording and colors like your other site emails. It can use these tokens:\n| Token | Value |\n| -- | -- |\n| {{quote.number}}, {{quote.revision}}, {{quote.total}} | The quote number, like #1042, its revision, and its total (with "before tax" when Stripe Tax adds the tax at payment) |\n| {{quote.heading}}, {{quote.intro}} | The heading, and one sentence on whether this is a new quote or an updated revision |\n| {{quote.message}} | The message you typed; empty when you typed none |\n| {{quote.proofImages}}, {{quote.proofFiles}} | Up to three proof images, and the other proof files by name |\n| {{quote.nextStep}}, {{quote.buttonLabel}}, {{quote.url}} | What to do next, the button\'s words, and the pay link |\n| {{quote.subject}} | The subject you sent it'
5822
+ text: 'One email in your site\'s look, from your site\'s name, with:\n- Your quote from your business name as its heading, or Your updated quote when it\'s a new revision of a quote you already emailed (the first email you send for a quote, and sending the same revision again, keep Your quote from);\n- your message;\n- the quote number, its revision and its total;\n- the first three proof images, each opening the quote page, and the other proof files by name, to see on the quote page (a WebP image is named rather than shown, because some inboxes can\'t show one);\n- what to do next, and one button:\n- Review and approve while the proof must be approved before paying and isn\'t yet;\n- otherwise View and pay with the total;\n- the quote attached as a PDF, the same one as Download PDF, with the pay link on it.\nThe button opens the quote\'s pay link. Replies go to the Email in your site\'s Business details, and to your own email when your site has none. The email ends with a line saying so.\nA proof with no price yet goes out as a proof: Your proof from your business name as its heading, no total, no PDF, and a Review the proof button.\nThe email is the Quote email under Emails, where you can change its wording and colors like your other site emails. It can use these tokens:\n| Token | Value |\n| -- | -- |\n| {{quote.label}} | Quote, or Proof for a proof with no price yet |\n| {{quote.number}}, {{quote.revision}}, {{quote.total}} | The quote number, like #1042, its revision, and its total (with "before tax" when Stripe Tax adds the tax at payment; empty for a proof with no price yet) |\n| {{quote.heading}}, {{quote.intro}} | The heading, and one sentence on whether this is a new quote or an updated revision |\n| {{quote.message}} | The message you typed; empty when you typed none |\n| {{quote.proofImage'
5823
5823
  },
5824
5824
  {
5825
5825
  path: '/commerce-and-bookings/commerce/quotes-and-proofs',
@@ -5854,14 +5854,21 @@ export const DOCS_SECTION_INDEX = [
5854
5854
  title: 'Quotes',
5855
5855
  heading: 'Attach proofs',
5856
5856
  anchor: '#proofs',
5857
- text: 'A proof shows your customer what they\'re getting before you make it: the canopy with their logo on it, the sign laid out at size. Attach proofs to a saved quote, and your customer sees them on the quote page, where they approve them or ask for changes.\n1. Open the quote and find Proofs in the editor.\n2. Choose Add proof and pick one or more files.\nA proof can be a PNG, JPEG, WebP, GIF, PDF, SVG, AI, EPS, PSD or TIFF file, up to 25 MB each, and a revision holds up to 10. Images show as pictures, and the other files as a chip with the file\'s name and size. Choose a picture or a chip to download the file.\nEvery file is checked before it\'s kept: a file whose contents aren\'t what its name says, or that carries a program, isn\'t taken, and an SVG is stripped of anything that could run. Proofs are kept privately with the quote. Only your team and the holder of the quote\'s link can open them, and never through a public address.\nTo take a proof off, choose Remove under it. You can add and remove proofs until your customer answers. After that, start a new revision to send different proofs.\nProofs, and the files your customer sends with an answer, count toward your workspace\'s storage like files in the media library. Removing a proof or deleting the quote frees the space. A proof that would go past a storage cap you set, or past a full workspace on Free, is refused with the reason, as a media library upload would be. Your customer\'s files are always taken.\nAdding or removing a proof changes what your customer sees, so it counts as an edit: a customer who has the page open is asked to look again before they answer or pay.'
5857
+ text: 'A proof shows your customer what they\'re getting before you make it: the canopy with their logo on it, the sign laid out at size. Attach proofs to a saved quote, and your customer sees them on the quote page, where they approve them or ask for changes.\n1. Open the quote and find Proofs in the editor.\n2. Choose Add proof and pick one or more files from your device, or choose From media library and pick a file you keep there.\nFrom media library offers the files you can read in this site\'s library and in your workspace\'s shared library, including private ones. The quote keeps its own private copy, made the moment you choose the file, so changing or deleting the file in the library afterward doesn\'t change what your customer sees or approved. A library file that isn\'t private still has its own public address in the library. To keep a design off the web entirely, turn on Private for it there too.\nA proof can be a PNG, JPEG, WebP, GIF, PDF, SVG, AI, EPS, PSD or TIFF file, up to 25 MB each, and a revision holds up to 10. Images show as pictures, and the other files as a chip with the file\'s name and size. Choose a picture or a chip to download the file.\nEvery file is checked before it\'s kept: a file whose contents aren\'t what its name says, or that carries a program, isn\'t taken, and an SVG is stripped of anything that could run. Proofs are kept privately with the quote. Only your team and the holder of the quote\'s link can open them, and never through a public address.\nTo take a proof off, choose Remove under it. You can add and remove proofs until your customer answers. After that, start a new revision to send different proofs. A proof with no price yet keeps its last proof until it has another.\nProofs, and the files your customer sends with an answer, count toward your work'
5858
+ },
5859
+ {
5860
+ path: '/commerce-and-bookings/commerce/quotes-and-proofs',
5861
+ title: 'Quotes',
5862
+ heading: 'Send a proof before it has a price',
5863
+ anchor: '#proof-only',
5864
+ text: 'A design often goes out before it\'s priced. A quote with a proof and no items is Proof only: you send your customer a link to the proof, and only someone with that link can open it, with no account.\n1. On the Orders tab, choose New quote in the Quotes card, and fill in the customer.\n2. Under Proofs, choose From media library and pick the design. Add more if you have them.\n3. Leave the items empty, and choose Create proof.\n4. Open it in the list, then choose Send proof, or Copy proof link to send the link yourself.\nYour customer sees the proof with Approve this proof and Request changes, and no items, totals, Pay or PDF. The email they get says the same.\nAdd an item and choose Save whenever you\'re ready to price it. It\'s then a normal quote on the same link, with its total and Pay, and an approval they already gave still stands. Taking every item off a quote with a proof makes it proof only again; a quote with no items and no proof can\'t be saved.\nA proof only quote has no invoice and no Download PDF, and starting a new revision works as it does for any quote. Until the new revision has a proof, it can\'t be emailed, and the link tells your customer the next version is on its way.'
5858
5865
  },
5859
5866
  {
5860
5867
  path: '/commerce-and-bookings/commerce/quotes-and-proofs',
5861
5868
  title: 'Quotes',
5862
5869
  heading: 'What your customer sees of the proofs',
5863
5870
  anchor: '#customer-proofs',
5864
- text: 'When the current revision has proofs, the quote page shows them under the quote: each image as a picture and every other file as a download. Beside them are two choices:\n- Approve this proof. Your customer types their name and chooses Approve. The quote keeps their name, the time, and the address and browser it came from, as the record of the approval, and moves to Approved.\n- Request changes. Your customer says what should change, and can attach their own artwork: up to 10 files of the same kinds and size as proofs. The quote moves to Changes requested, with their comment and files. Files they attach and never send are deleted a day later.\nThe latest answer is the one that counts. A customer who asked for changes can still approve, and one who approved can still ask for changes, which withdraws the approval. The page tells them what they last said.\nYou\'re notified of every answer, in the console and by email, as Proof approved or Changes requested, with the quote, the customer, the revision, the quote\'s total and what they said. View quote opens the quote, and replying to the email reaches your customer. These notices follow your settings for order notifications.\nA paid quote still shows its proofs, with nothing to press. A link you replaced shows nothing of the quote, proofs included, and takes no answer.'
5871
+ text: 'When the current revision has proofs, the quote page shows them under the quote: each image as a picture and every other file as a download. Beside them are two choices:\n- Approve this proof. Your customer types their name and chooses Approve. The quote keeps their name, the time, and the address and browser it came from, as the record of the approval, and moves to Approved.\n- Request changes. Your customer says what should change, and can attach their own artwork: up to 10 files of the same kinds and size as proofs. The quote moves to Changes requested, with their comment and files. Files they attach and never send are deleted a day later.\nThe latest answer is the one that counts. A customer who asked for changes can still approve, and one who approved can still ask for changes, which withdraws the approval. The page tells them what they last said.\nYou\'re notified of every answer, in the console and by email, as Proof approved or Changes requested, with the quote, the customer, the revision, the quote\'s total (if it has one) and what they said. View quote opens the quote, and replying to the email reaches your customer. These notices follow your settings for order notifications.\nA paid quote still shows its proofs, with nothing to press. A link you replaced shows nothing of the quote, proofs included, and takes no answer.'
5865
5872
  },
5866
5873
  {
5867
5874
  path: '/commerce-and-bookings/commerce/quotes-and-proofs',
@@ -5917,7 +5924,7 @@ export const DOCS_SECTION_INDEX = [
5917
5924
  title: 'Quotes',
5918
5925
  heading: 'Who can make and send quotes',
5919
5926
  anchor: '#permissions',
5920
- text: 'Making, editing and deleting quotes, adding and removing proofs, starting a revision, seeing earlier revisions and your customer\'s files, and downloading a quote\'s PDF, takes the Create and edit quotes permission. Emailing a quote or its invoice, and copying and replacing its pay link, takes Send quotes and invoices to customers, and so does a PDF that carries the pay link. Everyone who can manage orders on the site has both to start with; a custom role or a per-member override can grant or deny each one. See Order permissions.'
5927
+ text: 'Making, editing and deleting quotes, adding and removing proofs, starting a revision, seeing earlier revisions and your customer\'s files, and downloading a quote\'s PDF, takes the Create and edit quotes permission. A proof from the media library also takes being able to read that file in the library. Emailing a quote or its invoice, and copying and replacing its pay link, takes Send quotes and invoices to customers, and so does a PDF that carries the pay link. Everyone who can manage orders on the site has both to start with; a custom role or a per-member override can grant or deny each one. See Order permissions.'
5921
5928
  },
5922
5929
  {
5923
5930
  path: '/commerce-and-bookings/commerce/review-platforms',
@@ -5980,7 +5987,7 @@ export const DOCS_SECTION_INDEX = [
5980
5987
  title: 'Rewards, referrals and store credit',
5981
5988
  heading: 'Set up your program',
5982
5989
  anchor: '#set-up-your-program',
5983
- text: '1. Go to Products → Promotions and find the Rewards card.\n2. Turn on Customers earn and spend rewards.\n3. Set the rates:\n- Points per dollar spent — how many points each whole dollar of goods earns.\n- Points for $1 off — what points are worth when a customer spends them. With the defaults, 5 points per dollar and 100 points for $1 off, a customer gets back 5% of what they spend. The card shows the rate as you change it.\n- Points needed to redeem — a customer spends points once they hold at least this many.\n- Welcome points — given with a customer\'s first order. Leave it at 0 for none.\n4. Select Save in the card\'s header.\nThe card also shows how many members you have, the points they hold and what those points are worth, and the store credit they hold. Points and store credit are money your store owes, so keep an eye on these figures.\nOnly a site admin can change the program; anyone on the site can read it.'
5990
+ text: '1. Go to Products → Promotions and find the Rewards card.\n2. Turn on Customers earn and spend rewards.\n3. Set the rates:\n- Points per dollar spent — how many points each whole dollar of goods earns.\n- Points for $1 off — what points are worth when a customer spends them. With the defaults, 5 points per dollar and 100 points for $1 off, a customer gets back 5% of what they spend. The card shows the rate as you change it.\n- Points needed to redeem — a customer spends points once they hold at least this many.\n- Welcome points — given with a customer\'s first order. Leave it at 0 for none.\n4. Select Save in the card\'s header.\nThe card also shows how many members you have, the points they hold and what those points are worth, and the store credit they hold. Points and store credit are money your store owes, so keep an eye on these figures.\nChanging the program takes Change the rewards program, which a site\'s admins hold by default; anyone on the site can read it. See custom roles.'
5984
5991
  },
5985
5992
  {
5986
5993
  path: '/commerce-and-bookings/commerce/rewards-and-referrals',
@@ -6015,7 +6022,7 @@ export const DOCS_SECTION_INDEX = [
6015
6022
  title: 'Rewards, referrals and store credit',
6016
6023
  heading: 'Members and store credit',
6017
6024
  anchor: '#members-and-store-credit',
6018
- text: 'The Rewards members card under Products → Promotions lists every member, newest first. Sort by most points, or type the start of an email to find someone. Select a member to see their points, store credit, rewards and referral codes, and their last fifty changes.\n- Adjust adds or takes away points or store credit for a member, with a note kept in their history.\n- Give store credit in the card\'s header does the same for any email, and makes them a member if they are not one yet. Turn on Email the customer when credit is added to send them their new balance and rewards code.\nAdjusting balances needs an editor or admin on the site.'
6025
+ text: 'The Rewards members card under Products → Promotions lists every member, newest first. Sort by most points, or type the start of an email to find someone. Select a member to see their points, store credit, rewards and referral codes, and their last fifty changes.\n- Adjust adds or takes away points or store credit for a member, with a note kept in their history.\n- Give store credit in the card\'s header does the same for any email, and makes them a member if they are not one yet. Turn on Email the customer when credit is added to send them their new balance and rewards code.\nAdjusting balances takes Adjust rewards balances, which a site\'s admins and editors hold by default.'
6019
6026
  },
6020
6027
  {
6021
6028
  path: '/commerce-and-bookings/commerce/rewards-and-referrals',
@@ -6064,7 +6071,7 @@ export const DOCS_SECTION_INDEX = [
6064
6071
  title: 'Sales channels',
6065
6072
  heading: 'Turn on a channel',
6066
6073
  anchor: '#turn-on-a-channel',
6067
- text: 'Each channel has its own card: switch its feed on, copy the feed\'s address and paste it into the channel\'s own setup, which then fetches your products on a schedule.\n1. On the channel\'s card, switch the feed On. The card shows the feed\'s address.\n2. Select Copy address.\n3. Follow the steps on the card: each one opens the channel\'s own setup and says where the address goes. In short:\n| Channel | Where the address goes | Format |\n| -- | -- | -- |\n| Google | Merchant Center → Products → add products from a file → enter a link to your file | XML |\n| Meta | Commerce Manager → Catalog → Data sources → data feed → scheduled feed | XML |\n| TikTok | Ads Manager → Assets → Catalogs → add products with a data feed → scheduled feed | CSV |\n| Pinterest | Ads → Catalogs → create a data source | TSV |\n| Snapchat | Ads Manager → Catalogs → add products from a feed URL | CSV |\n| Microsoft | Microsoft Advertising → Merchant Center → Catalog → Feeds → scheduled download | Text |\nSet the channel to fetch at least daily. Products appear on YouTube through Google: link your YouTube channel to Merchant Center in Merchant Center\'s settings.\nThe address appears once the site has a web address — a subdomain or a custom domain — and it is always on your store\'s own domain.\nKeep the address private {#keep-the-address-private}\nEach feed\'s address carries a long random code, different for every channel, and the feed answers only that address. Anyone holding it can read what your storefront already shows publicly, nothing more. If an address is shared by mistake, select Replace address (site admins): the old address stops at once and the card shows the new one to paste into the channel.\nSwitching a feed Off stops it answering; switching it back on keeps the same address, so the channel picks up where'
6074
+ text: 'Each channel has its own card: switch its feed on, copy the feed\'s address and paste it into the channel\'s own setup, which then fetches your products on a schedule.\n1. On the channel\'s card, switch the feed On. The card shows the feed\'s address.\n2. Select Copy address.\n3. Follow the steps on the card: each one opens the channel\'s own setup and says where the address goes. In short:\n| Channel | Where the address goes | Format |\n| -- | -- | -- |\n| Google | Merchant Center → Products → add products from a file → enter a link to your file | XML |\n| Meta | Commerce Manager → Catalog → Data sources → data feed → scheduled feed | XML |\n| TikTok | Ads Manager → Assets → Catalogs → add products with a data feed → scheduled feed | CSV |\n| Pinterest | Ads → Catalogs → create a data source | TSV |\n| Snapchat | Ads Manager → Catalogs → add products from a feed URL | CSV |\n| Microsoft | Microsoft Advertising → Merchant Center → Catalog → Feeds → scheduled download | Text |\nSet the channel to fetch at least daily. Products appear on YouTube through Google: link your YouTube channel to Merchant Center in Merchant Center\'s settings.\nThe address appears once the site has a web address — a subdomain or a custom domain — and it is always on your store\'s own domain.\nKeep the address private {#keep-the-address-private}\nEach feed\'s address carries a long random code, different for every channel, and the feed answers only that address. Anyone holding it can read what your storefront already shows publicly, nothing more. If an address is shared by mistake, select Replace address (it takes Replace a feed address, which a site\'s admins hold by default): the old address stops at once and the card shows the new one to paste into the channel.\nSwitching a feed Off stops it answering; switching it ba'
6068
6075
  },
6069
6076
  {
6070
6077
  path: '/commerce-and-bookings/commerce/sales-channels',
@@ -6211,7 +6218,7 @@ export const DOCS_SECTION_INDEX = [
6211
6218
  title: 'Shipping labels and live carrier rates',
6212
6219
  heading: 'Before you start',
6213
6220
  anchor: '#before-you-start',
6214
- text: '- A store that ships. The site sells products, and shipping is on for it.\n- A way to pay for labels. Labels on the platform\'s carrier accounts are paid from your store\'s Stripe balance, which needs your Stripe account connected, or on your workspace\'s monthly invoice, which needs a payment method on the Billing page. Labels on a carrier account of your own are billed to you by that carrier. See Paying for labels.\n- Who can do what:\n| Task | Who |\n| See the Shipping labels card, get rates, buy, print and void labels, buy batch and return labels, check addresses | An editor or admin of the site |\n| Save the Shipping labels card, see Paying for labels and the Carrier accounts card | An admin of the site |\n| Turn Stripe balance payments on or off, switch a carrier on or off, connect a carrier account | An admin of the site who also has the workspace\'s Manage billing permission |\n| See the Shipping labels card on Billing → Usage | A workspace member with View billing |'
6221
+ text: '- A store that ships. The site sells products, and shipping is on for it.\n- A way to pay for labels. Labels on the platform\'s carrier accounts are paid from your store\'s Stripe balance, which needs your Stripe account connected, or on your workspace\'s monthly invoice, which needs a payment method on the Billing page. Labels on a carrier account of your own are billed to you by that carrier. See Paying for labels.\n- Who can do what:\n| Task | Permission | Who holds it by default |\n| See the Shipping labels card | See shipping settings | A site\'s admins and editors |\n| Get rates, check addresses, see an order\'s labels | Check rates and see labels | A site\'s admins and editors |\n| Buy a label, a batch of labels or a return label | Buy shipping labels | A site\'s admins and editors |\n| Void a label | Void shipping labels | A site\'s admins and editors |\n| Save the Shipping labels card | Change shipping settings | A site\'s admins |\n| See Paying for labels | Manage label charges | A site\'s admins |\n| See the Carrier accounts card | Manage carrier accounts | A site\'s admins |\n| Turn Stripe balance payments on or off | Manage label charges, and the workspace\'s Manage billing | A site\'s admins who also hold Manage billing |\n| Switch a carrier on or off, connect a carrier account | Manage carrier accounts, and the workspace\'s Manage billing | A site\'s admins who also hold Manage billing |\n| Connect or disconnect your own shipping account | Manage your own shipping accounts, and the workspace\'s Manage billing | A site\'s admins who also hold Manage billing |\n| See the Shipping labels card on Billing → Usage | View billing | Workspace members holding it |'
6215
6222
  },
6216
6223
  {
6217
6224
  path: '/commerce-and-bookings/commerce/shipping-labels-and-live-rates',
@@ -6239,7 +6246,7 @@ export const DOCS_SECTION_INDEX = [
6239
6246
  title: 'Shipping labels and live carrier rates',
6240
6247
  heading: 'Carrier rates at checkout',
6241
6248
  anchor: '#carrier-rates-at-checkout',
6242
- text: '1. Open Products → Shipping & delivery and, on the Shipping card, add a rate to a zone with the Type Carrier rates.\n2. Turn on the services this rate offers, or leave every one off to offer all of them.\n3. Optionally set Markup (%) and Handling fee ($). Both are added to each carrier\'s quote.\n4. Under If no live rate, pick another rate of the same zone. Checkout offers it whenever a live quote isn\'t available.\n5. Select Save shipping settings.\nShoppers then see each carrier\'s service and price for their address, with the delivery estimate in business days when the carrier gives one. Checkout asks for the postal code before it quotes, and the postal code field in the cart and on the product page notes that carrier rates depend on it. While live quotes are offered, the fallback rate is hidden.\nCheckout falls back when no carrier answers within a few seconds, and until labels are ready for your workspace: an address to ship from, and your workspace set up with the carrier platform, which happens the first time someone gets label rates or an admin opens the Carrier accounts card. If live rates aren\'t available on your site, a Carrier rates rate says so and checkout offers the fallback rate.'
6249
+ text: '1. Open Products → Shipping & delivery and, on the Shipping card, add a rate to a zone with the Type Carrier rates.\n2. Turn on the services this rate offers, or leave every one off to offer all of them.\n3. Optionally set Markup (%) and Handling fee ($). Both are added to each carrier\'s quote.\n4. Under If no live rate, pick another rate of the same zone. Checkout offers it whenever a live quote isn\'t available.\n5. Select Save shipping settings.\nShoppers then see each carrier\'s service and price for their address, with the delivery estimate in business days when the carrier gives one. Checkout asks for the postal code before it quotes, and the postal code field in the cart and on the product page notes that carrier rates depend on it. While live quotes are offered, the fallback rate is hidden.\nCheckout falls back when no carrier answers within a few seconds, and until labels are ready for your workspace: an address to ship from, and your workspace set up with the carrier platform, which happens the first time someone gets label rates or someone holding Manage carrier accounts opens the Carrier accounts card. If live rates aren\'t available on your site, a Carrier rates rate says so and checkout offers the fallback rate.'
6243
6250
  },
6244
6251
  {
6245
6252
  path: '/commerce-and-bookings/commerce/shipping-labels-and-live-rates',
@@ -6302,7 +6309,7 @@ export const DOCS_SECTION_INDEX = [
6302
6309
  title: 'Import and export store data',
6303
6310
  heading: '',
6304
6311
  anchor: '',
6305
- text: 'Import and export store data\nYour store\'s products, categories, orders, discounts, coupons and gift cards each have an Export button, and the ones a file may change have an Import button. Export lets you pick every field, including computed ones. Import shows you how each column is read and which record each row matches, and asks how to handle every conflict before anything is written.\n| What | Where | Import | Export |\n| Products and variants | Products page, above the table | Yes | Yes |\n| Categories | Categories & collections card | Yes | Yes |\n| Discounts | Discounts card | Yes | Yes |\n| Coupons | Coupons card | Yes | Yes |\n| Orders | Orders tab, Export orders or Export for shipping | No | Yes |\n| Gift cards | Gift cards card | Yes, by issuing each card | Yes |\n| Tracking numbers | Orders tab, Import tracking | Yes, by shipping each order | Yes |\nYou need permission to manage the site\'s data to import or undo an import. Importing gift cards also needs you to be an owner or admin of the workspace, or an admin of the site. Exporting needs read access to the site.'
6312
+ text: 'Import and export store data\nYour store\'s products, categories, orders, discounts, coupons and gift cards each have an Export button, and the ones a file may change have an Import button. Export lets you pick every field, including computed ones. Import shows you how each column is read and which record each row matches, and asks how to handle every conflict before anything is written.\n| What | Where | Import | Export |\n| Products and variants | Products page, above the table | Yes | Yes |\n| Categories | Categories & collections card | Yes | Yes |\n| Discounts | Discounts card | Yes | Yes |\n| Coupons | Coupons card | Yes | Yes |\n| Orders | Orders tab, Export orders or Export for shipping | No | Yes |\n| Gift cards | Gift cards card | Yes, by issuing each card | Yes |\n| Tracking numbers | Orders tab, Import tracking | Yes, by shipping each order | Yes |\nYou need permission to manage the site\'s data to import or undo an import. Importing gift cards also takes Import gift cards, which the workspace\'s owners and admins, and a site\'s admins, hold by default. Exporting needs read access to the site.'
6306
6313
  },
6307
6314
  {
6308
6315
  path: '/commerce-and-bookings/commerce/store-import-and-export',
@@ -6337,7 +6344,7 @@ export const DOCS_SECTION_INDEX = [
6337
6344
  title: 'Tax services (Avalara AvaTax and TaxJar)',
6338
6345
  heading: 'Connect',
6339
6346
  anchor: '#connect',
6340
- text: '1. Open Products → Taxes and find the Tax service card.\n2. Choose Avalara AvaTax or TaxJar, and Sandbox or Production.\n3. Enter your credentials and select Connect. Aglyn tests them with the vendor first and stores nothing they refuse. The credentials are encrypted on the server and are never shown again, not even to you.\n4. Enter the ship-from address: the street, city, state and postal code you ship or sell from. Aglyn checks it with the service. It is the origin of every sale and the place an in-person sale is taxed.\nOnly an admin of the site can connect, test or disconnect a service and change its address. Test connection checks the stored credentials again whenever you like; the card shows the answer.'
6347
+ text: '1. Open Products → Taxes and find the Tax service card.\n2. Choose Avalara AvaTax or TaxJar, and Sandbox or Production.\n3. Enter your credentials and select Connect. Aglyn tests them with the vendor first and stores nothing they refuse. The credentials are encrypted on the server and are never shown again, not even to you.\n4. Enter the ship-from address: the street, city, state and postal code you ship or sell from. Aglyn checks it with the service. It is the origin of every sale and the place an in-person sale is taxed.\nConnecting, testing or disconnecting a service and changing its address takes Manage the tax engine connection, which a site\'s admins hold by default (custom roles). Test connection checks the stored credentials again whenever you like; the card shows the answer.'
6341
6348
  },
6342
6349
  {
6343
6350
  path: '/commerce-and-bookings/commerce/tax-services',
@@ -7975,7 +7982,7 @@ export const DOCS_SECTION_INDEX = [
7975
7982
  title: 'Share records across sites',
7976
7983
  heading: 'Who can do this',
7977
7984
  anchor: '#who-can-do-this',
7978
- text: 'Sharing, unsharing and sharing rules are for workspace owners and admins. Other members see the Sharing card and the chips, but no share buttons.\nSharing is part of the CRM, included from Starter. It is only useful with more than one site, and the number of sites is set by your plan.'
7985
+ text: 'Sharing, unsharing and sharing rules take the Change CRM settings permission, which owners and admins hold by default. Other members see the Sharing card and the chips, with the share buttons switched off and the permission named.\nEditing a shared record is a different permission. A member invited to one site who holds Manage data can change and delete records shared with the whole workspace, because a record shared with every site is shared with theirs too; see Custom roles & permissions. They can\'t change what a record is shared with.\nSharing is part of the CRM, included from Starter. It is only useful with more than one site, and the number of sites is set by your plan.'
7979
7986
  },
7980
7987
  {
7981
7988
  path: '/content-and-data/crm/sharing',
@@ -8136,7 +8143,7 @@ export const DOCS_SECTION_INDEX = [
8136
8143
  title: 'Import & export',
8137
8144
  heading: '',
8138
8145
  anchor: '',
8139
- text: 'Import & export\nDatasets move in and out as CSV, JSON or NDJSON, so you can back them up, edit them in bulk in a spreadsheet, or bring records over from another tool. Both run on the server: a large dataset is never loaded into your browser, and nothing is written until you have seen what an import will do.\nPlan availability Starter and above (datasets need the data store). Importing needs the Manage data permission. Exporting needs only access to the dataset: any member who can see it can export it, and Export is shown to them while Import is not.\nPick the dataset on the Data page, then use Import or Export beside it.'
8146
+ text: 'Import & export\nDatasets move in and out as CSV, JSON or NDJSON, so you can back them up, edit them in bulk in a spreadsheet, or bring records over from another tool. Both run on the server: a large dataset is never loaded into your browser, and nothing is written until you have seen what an import will do.\nPlan availability Starter and above (datasets need the data store). Importing takes what writing the dataset takes: Manage data, or Manage this site\'s data on a dataset shared with that site alone. Exporting takes Export data, which every role holds by default, and access to the dataset. Whichever a member doesn\'t hold is switched off for them, naming the permission. See Dataset permissions.\nPick the dataset on the Data page, then use Import or Export beside it.'
8140
8147
  },
8141
8148
  {
8142
8149
  path: '/content-and-data/datasets/import-export',
@@ -8507,7 +8514,7 @@ export const DOCS_SECTION_INDEX = [
8507
8514
  title: 'Media Library & CDN',
8508
8515
  heading: 'Private files',
8509
8516
  anchor: '#private-files',
8510
- text: 'Private is a separate switch from sharing, and it answers a different question:\n| | Question it answers |\n| -- | -- |\n| Shared with | Which of your sites may use this file? |\n| Private | May anyone fetch these bytes at all? |\nA private file:\n- has no public URL — the normal media link does not exist for it, and Copy URL is hidden on it in both the card menu and the drawer,\n- loses any public URL it already had. Turning Private on revokes the file\'s public address at the moment you confirm it, so a link you copied and sent last month stops working too. That is the part people expect and the part that is easy to get wrong: a switch that only stopped new links would leave the one already in circulation serving the file forever,\n- cannot be placed on a page; the picker refuses it and says why. The one place a private file can be added is a product\'s members videos and digital downloads,\n- is viewable and downloadable in the console by people who can already see it, through a temporary link that stops working after about fifteen minutes.\nTwo menu items do that last part, and they are not interchangeable:\n- Copy temporary link (organization library, organization-wide members) puts a fifteen-minute link on your clipboard — for handing to one person, once, now. Nothing in Aglyn renews it, so it is a trap in a document or a page: what you paste stops working while the page still looks fine.\n- Download file saves the bytes. Aglyn mints a fresh link for that click, so the expiry never reaches you.\nCopy URL being hidden rather than disabled is deliberate: there is no permanent address to hand over, and a copied link that 404s is worse than no button.\nThat expiry is the point. A normal media URL, once shared, works forever and there\'s no way to take it back. A private file\'s link di'
8517
+ text: 'Private is a separate switch from sharing, and it answers a different question:\n| | Question it answers |\n| -- | -- |\n| Shared with | Which of your sites may use this file? |\n| Private | May anyone fetch these bytes at all? |\nA private file:\n- has no public URL — the normal media link does not exist for it, and Copy URL is hidden on it in both the card menu and the drawer,\n- loses any public URL it already had. Turning Private on revokes the file\'s public address at the moment you confirm it, so a link you copied and sent last month stops working too. That is the part people expect and the part that is easy to get wrong: a switch that only stopped new links would leave the one already in circulation serving the file forever,\n- cannot be placed on a page; the picker refuses it and says why. The one place a private file can be added is a product\'s members videos and digital downloads,\n- is viewable and downloadable in the console by people who can already see it, through a temporary link that stops working after about fifteen minutes.\nTwo menu items do that last part, and they are not interchangeable:\n- Copy temporary link (organization library, anyone who can see the file) puts a fifteen-minute link on your clipboard — for handing to one person, once, now. Nothing in Aglyn renews it, so it is a trap in a document or a page: what you paste stops working while the page still looks fine.\n- Download file saves the bytes. Aglyn mints a fresh link for that click, so the expiry never reaches you.\nCopy URL being hidden rather than disabled is deliberate: there is no permanent address to hand over, and a copied link that 404s is worse than no button.\nThat expiry is the point. A normal media URL, once shared, works forever and there\'s no way to take it back. A private file\'s link '
8511
8518
  },
8512
8519
  {
8513
8520
  path: '/content-and-data/media/overview',
@@ -8836,7 +8843,7 @@ export const DOCS_SECTION_INDEX = [
8836
8843
  title: 'Guide: import and export screens',
8837
8844
  heading: 'Open it',
8838
8845
  anchor: '#open-it',
8839
- text: 'Your plugin never renders the screens itself: the console does, and hands your plugin a launcher. Ask for it with useTransferLauncher() from @aglyn/aglyn and open the wizard or the dialog on the resource you declared in transferResources:\nShow only what the person may do\ntransfer.can(\'import\' | \'export\', { resource, scope, hostId? }) answers what the transfer routes would: synchronously, from the permissions the console already holds, with no request per button. It reads false until those permissions have loaded, so a button appears once rather than flickering away.\n- Import needs the Manage data permission — on the named site for a site\'s records, on the workspace otherwise.\n- Export asks what your resource declares beside its key in transferResources:\n- "readableByMembers": true — every member may read these records (the rules let them), so any member may export what they can see, and a site collaborator only on a site they reach. Your readPage and count keep a scoped reader to their own records through scopeTokens.\n- "readPermission": " " — whoever holds that permission (a key your plugin declared, say) may export, beside Manage data.\n- Neither — Manage data, the same as importing. This is the default because a resource\'s records may be ones only managers read.\n- The plan comes before either, when your resource declares a "featureFlag" (the flag your console surfaces are gated by): on a plan without it, can answers false for every intent your resource doesn\'t list in "featureFlagExempt", and the routes refuse with 403 planrequired. Register planGate with the server half so the refusal is in your plugin\'s own words. The CRM declares "featureFlag": "crm" on every resource and exempts only the contacts and leads exports. Declare the same flag your console extension (or '
8846
+ text: 'Your plugin never renders the screens itself: the console does, and hands your plugin a launcher. Ask for it with useTransferLauncher() from @aglyn/aglyn and open the wizard or the dialog on the resource you declared in transferResources:\nShow only what the person may do\ntransfer.can(\'import\' | \'export\', { resource, scope, hostId? }) answers what the transfer routes would: synchronously, from the permissions the console already holds, with no request per button. It reads false until those permissions have loaded, so a button appears once rather than flickering away.\n- Import needs the Manage data permission — on the named site for a site\'s records, on the workspace otherwise.\n- Export asks what your resource declares beside its key in transferResources:\n- "readableByMembers": true — every member may read these records (the rules let them), so any member may export what they can see, and a site collaborator only on a site they reach. Your readPage and count keep a scoped reader to their own records through scopeTokens.\n- "readPermission": " " — whoever holds that permission (a key your plugin declared, say) may export, beside Manage data. Add "readPermissionOnly": true for that key alone to decide, so taking it away stops the export whoever may write the records. A dataset\'s records are declared this way, with Export data.\n- Neither — Manage data, the same as importing. This is the default because a resource\'s records may be ones only managers read.\n- Import can answer per instance: register importAccess with the server half when who may import depends on the instance, as a dataset\'s does on where it is shared. It answers in place of Manage data on the workspace, every transfer route asks it, and your surface passes the same answer to can as importAllowed on the target. '
8840
8847
  },
8841
8848
  {
8842
8849
  path: '/developers/plugins/guides/import-and-export',
@@ -9480,7 +9487,7 @@ export const DOCS_SECTION_INDEX = [
9480
9487
  title: 'Plugin-manager API reference',
9481
9488
  heading: 'Import and export — `plugin-transfer-resources`',
9482
9489
  anchor: '#import-and-export--plugin-transfer-resources',
9483
- text: 'Everything a person imports or exports is a transfer RESOURCE: rows in a file (records) or a set of items carried as a package (package). The matching, cell reading, conflict policy and dry run are the core\'s (@aglyn/aglyn/data-transfer, see docs/DATATRANSFER.md); the plugin that owns the records declares the resource and answers for it. Declare it in plugins.config.json, in the core\'s TransferResourceDescriptor shape:\n| Field | Semantics |\n| key | Lowercase words joined by - or ., at most 64 characters; one owner per key. The URL and storage name. |\n| label / singularLabel / description | What the hub and the wizard call it. |\n| scope | org (the workspace\'s records) or host (one site\'s). |\n| kinds | records, package, or both. |\n| formats | csv, json, ndjson. |\n| limits | maxRows (and optional maxBytes) one file may carry. |\n| instances | true for a resource moved one instance at a time — one dataset\'s records, not every dataset\'s. Every key that reaches it names the instance as : (transferResourceInstanceKey, data.dataset: ), so a job, the person\'s remembered choices and the one running import are each kept per instance; the hooks read which one with transferResourceInstanceOf(ctx). |\n| readableByMembers | true when every member may read the records, so any member may export what their scope lets them see (a collaborator only on a site they reach) and open the export dialog. A dataset\'s records are declared this way. |\n| readPermission | The permission that admits a member to export the records, beside Manage data (data.manage), which always admits. A resource that declares neither this nor readableByMembers exports for Manage data alone; importing needs Manage data either way. The launcher\'s can(\'import\' \\| \'export\', target) answers the same rule for a list\'s buttons.'
9490
+ text: 'Everything a person imports or exports is a transfer RESOURCE: rows in a file (records) or a set of items carried as a package (package). The matching, cell reading, conflict policy and dry run are the core\'s (@aglyn/aglyn/data-transfer, see docs/DATATRANSFER.md); the plugin that owns the records declares the resource and answers for it. Declare it in plugins.config.json, in the core\'s TransferResourceDescriptor shape:\n| Field | Semantics |\n| key | Lowercase words joined by - or ., at most 64 characters; one owner per key. The URL and storage name. |\n| label / singularLabel / description | What the hub and the wizard call it. |\n| scope | org (the workspace\'s records) or host (one site\'s). |\n| kinds | records, package, or both. |\n| formats | csv, json, ndjson. |\n| limits | maxRows (and optional maxBytes) one file may carry. |\n| instances | true for a resource moved one instance at a time — one dataset\'s records, not every dataset\'s. Every key that reaches it names the instance as : (transferResourceInstanceKey, data.dataset: ), so a job, the person\'s remembered choices and the one running import are each kept per instance; the hooks read which one with transferResourceInstanceOf(ctx). |\n| readableByMembers | true when every member may read the records, so any member may export what their scope lets them see (a collaborator only on a site they reach) and open the export dialog. |\n| readPermission | The permission that admits a member to export the records, beside Manage data (data.manage), which always admits. A resource that declares neither this nor readableByMembers exports for Manage data alone; importing needs Manage data either way. The launcher\'s can(\'import\' \\| \'export\', target) answers the same rule for a list\'s buttons. |\n| readPermissionOnly | true when readPer'
9484
9491
  },
9485
9492
  {
9486
9493
  path: '/developers/plugins/reference/plugin-manager-api',
@@ -9524,6 +9531,13 @@ export const DOCS_SECTION_INDEX = [
9524
9531
  anchor: '#entity-pickers--plugin-entity-pickers',
9525
9532
  text: 'An element\'s attribute can name another record by id — the product a product grid shows, the form a Form element files into, the dataset a repeat walks — and the Besigner offers it as a picker of the site\'s records of that kind, listed by current name and stored by id. A plugin that keeps records an element can name declares each kind in an entityPickers block of plugins.config.json:\n| Field | Semantics |\n| kind | The key the picker context holds the kind under (options[kind], status[kind], resolved[kind]) and a repeat source names as its entityKind. One owner per kind. |\n| attribute | The attribute type (FieldComponentType) whose picker lists the kind. One kind per attribute type. |\n| scope | host — the site\'s own hosts/{hostId}/{collection}; orgData — the organization\'s data, read where the site\'s data scope resolves and narrowed to what the site may use (visibleTo against the site\'s scope tokens), with anything else resolved as unavailable. |\n| collection, nameField | Where the documents are and the field a document is named by; name, then the id, when it is empty. |\n| where | Equality clauses applied on the server to the browse and the search alike. |\n| searchable | The documents carry nameTokens/nameLower, so a typed query reaches past the browse window. |\n| fieldsAttribute, fieldsFrom | Together: an attribute type whose options are the FIELDS of an entity of this kind an ancestor chose, and the record kind whose console list source (Record lists) shares each entity\'s fields as { id, name }. The plugin declares the entityPickers load point among its console.slots, so the picker provider loads its source. |\n| singular, plural, page | The words a picker says: "No bottles yet — add one on the Cellar page". |\nCore keeps the machinery every kind shares: the browse windo'
9526
9533
  },
9534
+ {
9535
+ path: '/developers/plugins/reference/plugin-manager-api',
9536
+ title: 'Plugin-manager API reference',
9537
+ heading: 'Shared with all sites except some — `plugin-scope-sharing` (`/server`)',
9538
+ anchor: '#shared-with-all-sites-except-some--plugin-scope-sharing-server',
9539
+ text: 'A document in an org collection can be shared with every site but a few. It keeps the sites it reaches in visibleTo, so that list has to change when a site joins or leaves the workspace. One sweep does that for every collection, and it walks what plugins declare in the scopeSharingCollections block of plugins.config.json, compiled with no runtime door.\n| Declaration field | Semantics |\n| -- | -- |\n| name | The subcollection under orgs/{orgId}. One collection has one owner. |\n| patch | true when stored fields follow visibleTo, such as scoped search tokens. The sweep writes nothing to the collection until the patch is registered. |\n| maxIncluded | The most sites one document may reach. Past it the document stops gaining sites, still loses sites that left, and shows in the weekly drift report. |\n| keepSiteFields | Fields naming sites that stay included though they are excluded, such as the site that captured a person. |\n| API | Semantics |\n| -- | -- |\n| listScopeSharingCollections() | Every collection the sweep walks, with its owner, in a stable order. |\n| registerPluginScopeSharingPatch(collections, patch, { pluginId? }) | Registers the function that recomputes those fields. It receives the collection and the whole document as it will be stored, and its answer is merged into the write. Refuses a collection the plugin did not declare with patch: true. |\nRegister a patch from serverDeclarations, deferring what it needs behind an await import: it registers in every server process, and only a sweep that finds a marked document calls it.'
9540
+ },
9527
9541
  {
9528
9542
  path: '/developers/plugins/reference/plugin-manager-api',
9529
9543
  title: 'Plugin-manager API reference',
@@ -10824,7 +10838,7 @@ export const DOCS_SECTION_INDEX = [
10824
10838
  title: 'Commerce end to end',
10825
10839
  heading: '5. Run orders from the console',
10826
10840
  anchor: '#5-run-orders-from-the-console',
10827
- text: 'The Products hub\'s Orders tab lists every sale, newest first. Its Search finds an order by the start of a word in its number, the buyer\'s email or an item\'s name, and Filters narrows it by order number, product, date, status, channel, customer and dispute — across every order in the store, not only the page on screen (see The Orders page for what combines). Beside it sit Export orders and Draft order (build an order by hand and send a payment link).\nExport orders writes every order the filters and the search match, however many there are, one row per order, with the fields you pick: the order number and date, status and channel, the customer and addresses, the items, and the money — items subtotal, shipping, tax, discount, Total (the gross charge), fee, Refunded and Net. Reconcile against a Stripe payout with Net, or Total less Refunded. An order with several line items names the first and counts the rest in Product, e.g. Blue Mug +2 more, and lists every line in Items. See Import and export store data.\nOpen an order for the detail dialog — customer, line items, totals, timeline, and internal notes:\n- Fulfill… — enter a carrier and tracking number; the order moves to fulfilled and the buyer\'s account page shows the tracking. Mark delivered closes the loop, and Packing slip prints one.\n- Refund — confirms "Refund this order?", then refunds the buyer through Stripe (full or partial) and reverses the platform fee. Site-admin role only.\n- Cancel order — for orders that shouldn\'t proceed (does not auto-refund).\nStatuses move through a guarded machine: pending → paid → fulfilled → delivered, with cancel/refund exits — see the orders reference.'
10841
+ text: 'The Products hub\'s Orders tab lists every sale, newest first. Its Search finds an order by the start of a word in its number, the buyer\'s email or an item\'s name, and Filters narrows it by order number, product, date, status, channel, customer and dispute — across every order in the store, not only the page on screen (see The Orders page for what combines). Beside it sit Export orders and Draft order (build an order by hand and send a payment link).\nExport orders writes every order the filters and the search match, however many there are, one row per order, with the fields you pick: the order number and date, status and channel, the customer and addresses, the items, and the money — items subtotal, shipping, tax, discount, Total (the gross charge), fee, Refunded and Net. Reconcile against a Stripe payout with Net, or Total less Refunded. An order with several line items names the first and counts the rest in Product, e.g. Blue Mug +2 more, and lists every line in Items. See Import and export store data.\nOpen an order for the detail dialog — customer, line items, totals, timeline, and internal notes:\n- Fulfill… — enter a carrier and tracking number; the order moves to fulfilled and the buyer\'s account page shows the tracking. Mark delivered closes the loop, and Packing slip prints one.\n- Refund — confirms "Refund this order?", then refunds the buyer through Stripe (full or partial) and reverses the platform fee. It takes the Refund orders permission, which site admins hold by default.\n- Cancel order — for orders that shouldn\'t proceed (does not auto-refund).\nStatuses move through a guarded machine: pending → paid → fulfilled → delivered, with cancel/refund exits — see the orders reference.'
10828
10842
  },
10829
10843
  {
10830
10844
  path: '/guides/commerce-end-to-end',
@@ -11342,7 +11356,7 @@ export const DOCS_SECTION_INDEX = [
11342
11356
  title: 'Your first API call',
11343
11357
  heading: '',
11344
11358
  anchor: '',
11345
- text: 'Your first API call\nBy the end of this page you\'ll have made a real request to your own data and handled the errors properly. It assumes nothing — if you\'ve never used an API before, start at the top and follow along; if you have, skip to Step 3 and then read the API reference instead of the rest of this.\nEverything here uses curl, which is already installed on macOS and Linux and ships with Windows 10 and later. There\'s a JavaScript version of each step underneath.\nWhat you need\n- An organization on a plan that includes API access — Pro or Custom.\n- Permission to manage the organization — only owners and admins can create keys.\n- A terminal.'
11359
+ text: 'Your first API call\nBy the end of this page you\'ll have made a real request to your own data and handled the errors properly. It assumes nothing — if you\'ve never used an API before, start at the top and follow along; if you have, skip to Step 3 and then read the API reference instead of the rest of this.\nEverything here uses curl, which is already installed on macOS and Linux and ships with Windows 10 and later. There\'s a JavaScript version of each step underneath.\nWhat you need\n- An organization on a plan that includes API access — Pro or Custom.\n- The Manage API keys permission, which owners and admins hold by default.\n- A terminal.'
11346
11360
  },
11347
11361
  {
11348
11362
  path: '/guides/your-first-api-call',
@@ -11979,7 +11993,7 @@ export const DOCS_SECTION_INDEX = [
11979
11993
  title: 'Email platforms (Mailchimp, Klaviyo, Omnisend)',
11980
11994
  heading: 'Connect a platform',
11981
11995
  anchor: '#connect',
11982
- text: '1. Open the site, then Setup → Integrations. The Email platforms card lists each platform on a row of its own.\n2. On the platform\'s row, select Connect.\n3. Paste your API key, then Check and connect. Aglyn checks the key with the platform before it saves it, and stores it encrypted; it is never shown again.\n- Mailchimp: in Mailchimp, Profile → Extras → API keys → Create a key. It ends in your data center, like -us21.\n- Klaviyo: in Klaviyo, Settings → API keys → Create private API key, with full access to Profiles, Lists, Subscriptions and Events.\n- Omnisend: in Omnisend, Store settings → API keys → Create API key, with access to Contacts and Events.\n4. For Mailchimp and Klaviyo, choose the audience or list contacts go into. If your account has only one, it is chosen for you.\nThe first sync starts within 15 minutes. Sync now runs it straight away.\nOnly a site admin can connect, change or disconnect a platform; editors can see the card and each platform\'s sync log.\nAttentive connects by signing in to Attentive rather than with an API key, and works one way only: see Connect Attentive.'
11996
+ text: '1. Open the site, then Setup → Integrations. The Email platforms card lists each platform on a row of its own.\n2. On the platform\'s row, select Connect.\n3. Paste your API key, then Check and connect. Aglyn checks the key with the platform before it saves it, and stores it encrypted; it is never shown again.\n- Mailchimp: in Mailchimp, Profile → Extras → API keys → Create a key. It ends in your data center, like -us21.\n- Klaviyo: in Klaviyo, Settings → API keys → Create private API key, with full access to Profiles, Lists, Subscriptions and Events.\n- Omnisend: in Omnisend, Store settings → API keys → Create API key, with access to Contacts and Events.\n4. For Mailchimp and Klaviyo, choose the audience or list contacts go into. If your account has only one, it is chosen for you.\nThe first sync starts within 15 minutes. Sync now runs it straight away.\nConnecting, changing or disconnecting a platform takes Manage email platform connections, which a site\'s admins hold by default. Seeing the card and each platform\'s sync log takes See email platform connections, which a site\'s admins and editors hold by default. See custom roles.\nAttentive connects by signing in to Attentive rather than with an API key, and works one way only: see Connect Attentive.'
11983
11997
  },
11984
11998
  {
11985
11999
  path: '/marketing-and-automation/email-campaigns/email-platforms',
@@ -12364,7 +12378,7 @@ export const DOCS_SECTION_INDEX = [
12364
12378
  title: 'Org automations',
12365
12379
  heading: 'Every site\'s own automations',
12366
12380
  anchor: '#every-sites-own-automations',
12367
- text: 'The organization hub\'s Workflows, Actions and Webhooks sections list every site\'s own workflows, actions and webhooks side by side, with the site each belongs to. Each row opens that site\'s Automation, where it is edited, and Add … on a site asks which site first. The lists open with the first few sites and show the rest when asked; a site with more than fits in the list links to its own page for all of them. Webhooks are listed for admins and editors, because each holds its site\'s secret.'
12381
+ text: 'The organization hub\'s Workflows, Actions and Webhooks sections list every site\'s own workflows, actions and webhooks side by side, with the site each belongs to. Each row opens that site\'s Automation, where it is edited, and Add … on a site asks which site first. The lists open with the first few sites and show the rest when asked; a site with more than fits in the list links to its own page for all of them. Each site\'s webhooks are listed for members who hold See orders and webhooks on that site, because each holds its site\'s secret. A site\'s Admins and Editors hold it by default.'
12368
12382
  },
12369
12383
  {
12370
12384
  path: '/marketing-and-automation/workflows-and-actions/org-automations',
@@ -12721,7 +12735,7 @@ export const DOCS_SECTION_INDEX = [
12721
12735
  title: 'Import and export',
12722
12736
  heading: '',
12723
12737
  anchor: '',
12724
- text: 'Import and export\nEverything you can move in or out of your workspace is listed in one place: Settings → Import & export. Each import works the same way. It shows you what it would do before it writes anything, asks you how to handle every conflict, and can be undone for seven days.\nThe page is open to anyone who can export something. Importing, packages and the list of past imports need the Manage data permission. Owners, admins and editors have it by default, and a custom role can grant or withhold it. Without it you see Export only for data your role lets you read, such as a dataset\'s records. Every page with its own Import and Export buttons, such as a list of products or an email list, shows each button only when you can use it.\nGift cards are stricter. Only the workspace\'s owners and admins, and a site\'s admins, can import them, because an import issues spendable money.'
12738
+ text: 'Import and export\nEverything you can move in or out of your workspace is listed in one place: Settings → Import & export. Each import works the same way. It shows you what it would do before it writes anything, asks you how to handle every conflict, and can be undone for seven days.\nThe page is open to anyone who can export something. Importing, packages and the list of past imports need the Manage data permission. Owners, admins and editors have it by default, and a custom role can grant or withhold it. Without it you see Export only for data your role lets you read, such as a dataset\'s records, and Import is switched off and names the permission. A dataset placed on one site answers to that site: Manage this site\'s data, which the site\'s admins and editors hold by default, decides its Import here, as it does on the Data page. Every page with its own Import and Export buttons, such as a list of products or an email list, shows each button only when you can use it.\nGift cards are stricter, because an import issues spendable money: importing them also takes Import gift cards, which the workspace\'s owners and admins, and a site\'s admins, hold by default.'
12725
12739
  },
12726
12740
  {
12727
12741
  path: '/workspace-and-billing/import-and-export',
@@ -12980,7 +12994,7 @@ export const DOCS_SECTION_INDEX = [
12980
12994
  title: 'Signing In & Sessions',
12981
12995
  heading: 'Downloading your data',
12982
12996
  anchor: '#downloading-your-data',
12983
- text: 'Manage Account → Close account → Download my data gives you a machine-readable JSON copy of everything we hold about you: your profile and contact details, your workspace memberships, your passkeys, your public publisher handle, and the support messages you wrote. It is the same file we would send if you asked us in writing.\nIt is deliberately scoped to you. A workspace is shared, so your colleagues\' details are not in it — a support thread you took part in contributes only the messages you wrote yourself, not the replies. To take a whole workspace with you, use the workspace export below instead.\nIt never contains a secret. API keys, webhook secrets, password hashes and payment links are listed as present rather than reproduced, so the file tells you what exists without becoming something you can lose. An API key\'s identifier is withheld too, because that identifier is derived from the key itself.\nThat is decided by what a value looks like, not only by what the field is called — a credential is withheld whether it sits in a field named webhooksecret, one named supplierToken, or one named nothing in particular. A credential carried inside a URL is stripped out of the address while the address itself stays, so you can still see where your own files live. Ordinary content, prose, identifiers and content hashes are not touched: a list of names is a list somebody has to keep up to date, and the whole point of this file is that it does not quietly stop covering something.\nThe file opens with a coverage section naming every place we looked and what was done with each — including the two things that are deliberately not included, and why. If something you expected is missing, that section is where to check first.\nDownloading a whole workspace\nThe workspace owner can export an '
12997
+ text: 'Manage Account → Close account → Download my data gives you a machine-readable JSON copy of everything we hold about you: your profile and contact details, your workspace memberships, your passkeys, your public publisher handle, and the support messages you wrote. It is the same file we would send if you asked us in writing.\nIt is deliberately scoped to you. A workspace is shared, so your colleagues\' details are not in it — a support thread you took part in contributes only the messages you wrote yourself, not the replies. To take a whole workspace with you, use the workspace export below instead.\nIt never contains a secret. API keys, webhook secrets, password hashes and payment links are listed as present rather than reproduced, so the file tells you what exists without becoming something you can lose. An API key\'s identifier is withheld too, because that identifier is derived from the key itself.\nThat is decided by what a value looks like, not only by what the field is called — a credential is withheld whether it sits in a field named webhooksecret, one named supplierToken, or one named nothing in particular. A credential carried inside a URL is stripped out of the address while the address itself stays, so you can still see where your own files live. Ordinary content, prose, identifiers and content hashes are not touched: a list of names is a list somebody has to keep up to date, and the whole point of this file is that it does not quietly stop covering something.\nThe file opens with a coverage section naming every place we looked and what was done with each — including the two things that are deliberately not included, and why. If something you expected is missing, that section is where to check first.\nDownloading a whole workspace\nAnyone who holds the Export worksp'
12984
12998
  },
12985
12999
  {
12986
13000
  path: '/workspace-and-billing/signing-in-and-sessions',
@@ -13281,7 +13295,7 @@ export const DOCS_SECTION_INDEX = [
13281
13295
  title: 'White-label',
13282
13296
  heading: 'Where the settings are',
13283
13297
  anchor: '#where',
13284
- text: '1. Open your organization\'s Settings page — the heading reads Organization Settings.\n2. Choose the Branding tab.\n3. The card is White-label brand.\nYou need the admin role. The Branding tab is not shown at all to members below it, so a teammate who cannot find it is looking at a shorter tab strip than you are, not at a hidden card.\nWhile your plan is still being read the card says "Checking your plan…". On a plan without the entitlement it shows an information notice pointing you to Billing instead of the editor.'
13298
+ text: '1. Open your organization\'s Settings page — the heading reads Organization Settings.\n2. Choose the Branding tab.\n3. The card is White-label brand.\nYou need the Organization settings permission, which owners and admins hold by default. The Branding tab is not shown at all to members without it, so a teammate who cannot find it is looking at a shorter tab strip than you are, not at a hidden card.\nWhile your plan is still being read the card says "Checking your plan…". On a plan without the entitlement it shows an information notice pointing you to Billing instead of the editor.'
13285
13299
  },
13286
13300
  {
13287
13301
  path: '/workspace-and-billing/white-label',