@aglyn/aglyn 1.11.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 (86) hide show
  1. package/package.json +11 -11
  2. package/src/lib/app-utils/account-preferences.d.ts +15 -13
  3. package/src/lib/app-utils/account-preferences.js +20 -20
  4. package/src/lib/app-utils/account-preferences.js.map +1 -1
  5. package/src/lib/app-utils/crm.d.ts +3 -1
  6. package/src/lib/app-utils/crm.js +6 -3
  7. package/src/lib/app-utils/crm.js.map +1 -1
  8. package/src/lib/app-utils/docs-help-sections.generated.js +10 -4
  9. package/src/lib/app-utils/docs-help-sections.generated.js.map +1 -1
  10. package/src/lib/app-utils/docs-help.generated.d.ts +2 -2
  11. package/src/lib/app-utils/docs-help.generated.js +8 -0
  12. package/src/lib/app-utils/docs-help.generated.js.map +1 -1
  13. package/src/lib/app-utils/docs-index.generated.js +117 -96
  14. package/src/lib/app-utils/docs-index.generated.js.map +1 -1
  15. package/src/lib/app-utils/host-permissions.d.ts +12 -0
  16. package/src/lib/app-utils/host-permissions.js +26 -1
  17. package/src/lib/app-utils/host-permissions.js.map +1 -1
  18. package/src/lib/app-utils/markdown-lite.js +8 -1
  19. package/src/lib/app-utils/markdown-lite.js.map +1 -1
  20. package/src/lib/app-utils/media-asset-facts.d.ts +2 -2
  21. package/src/lib/app-utils/media-asset-facts.js +4 -3
  22. package/src/lib/app-utils/media-asset-facts.js.map +1 -1
  23. package/src/lib/app-utils/media-cdn-scope.d.ts +19 -4
  24. package/src/lib/app-utils/media-cdn-scope.js +19 -5
  25. package/src/lib/app-utils/media-cdn-scope.js.map +1 -1
  26. package/src/lib/app-utils/media-ref.d.ts +10 -6
  27. package/src/lib/app-utils/media-ref.js +34 -8
  28. package/src/lib/app-utils/media-ref.js.map +1 -1
  29. package/src/lib/app-utils/org-permissions.d.ts +7 -0
  30. package/src/lib/app-utils/org-permissions.js +2 -0
  31. package/src/lib/app-utils/org-permissions.js.map +1 -1
  32. package/src/lib/app-utils/org-role-grants.d.ts +13 -0
  33. package/src/lib/app-utils/org-role-grants.js +9 -5
  34. package/src/lib/app-utils/org-role-grants.js.map +1 -1
  35. package/src/lib/app-utils/person-erasure.d.ts +8 -0
  36. package/src/lib/app-utils/person-erasure.js +6 -0
  37. package/src/lib/app-utils/person-erasure.js.map +1 -1
  38. package/src/lib/app-utils/scope-tokens.d.ts +132 -3
  39. package/src/lib/app-utils/scope-tokens.js +276 -3
  40. package/src/lib/app-utils/scope-tokens.js.map +1 -1
  41. package/src/lib/app-utils/site-placement.d.ts +56 -0
  42. package/src/lib/app-utils/site-placement.js +88 -0
  43. package/src/lib/app-utils/site-placement.js.map +1 -0
  44. package/src/lib/app-utils/site-preview.d.ts +6 -2
  45. package/src/lib/app-utils/site-preview.js +5 -3
  46. package/src/lib/app-utils/site-preview.js.map +1 -1
  47. package/src/lib/app-utils/site-unavailable.d.ts +4 -7
  48. package/src/lib/app-utils/site-unavailable.js +4 -8
  49. package/src/lib/app-utils/site-unavailable.js.map +1 -1
  50. package/src/lib/app-utils/transfer-launcher-context.d.ts +17 -1
  51. package/src/lib/app-utils/transfer-launcher-context.js.map +1 -1
  52. package/src/lib/data-transfer/access.d.ts +10 -18
  53. package/src/lib/data-transfer/access.js +21 -25
  54. package/src/lib/data-transfer/access.js.map +1 -1
  55. package/src/lib/data-transfer/resource.d.ts +13 -14
  56. package/src/lib/data-transfer/resource.js +9 -10
  57. package/src/lib/data-transfer/resource.js.map +1 -1
  58. package/src/lib/foundation/definitions/org-billing.types.js +2 -2
  59. package/src/lib/foundation/definitions/org-billing.types.js.map +1 -1
  60. package/src/lib/foundation/definitions/platform.types.d.ts +1 -1
  61. package/src/lib/foundation/definitions/platform.types.js.map +1 -1
  62. package/src/lib/foundation/definitions/write-deny-coverage.util.d.ts +1 -1
  63. package/src/lib/foundation/definitions/write-deny-coverage.util.js +1 -1
  64. package/src/lib/foundation/definitions/write-deny-coverage.util.js.map +1 -1
  65. package/src/lib/plugin-manager/first-party-plugins.generated.js +4 -5
  66. package/src/lib/plugin-manager/first-party-plugins.generated.js.map +1 -1
  67. package/src/lib/plugin-manager/plugin-contact-capture.d.ts +18 -0
  68. package/src/lib/plugin-manager/plugin-contact-capture.js +26 -0
  69. package/src/lib/plugin-manager/plugin-contact-capture.js.map +1 -1
  70. package/src/lib/plugin-manager/plugin-entitlements.d.ts +12 -0
  71. package/src/lib/plugin-manager/plugin-entitlements.js +3 -1
  72. package/src/lib/plugin-manager/plugin-entitlements.js.map +1 -1
  73. package/src/lib/plugin-manager/plugin-person-erasure-notes.d.ts +61 -0
  74. package/src/lib/plugin-manager/plugin-person-erasure-notes.js +114 -0
  75. package/src/lib/plugin-manager/plugin-person-erasure-notes.js.map +1 -0
  76. package/src/lib/plugin-manager/plugin-scope-sharing.d.ts +52 -0
  77. package/src/lib/plugin-manager/plugin-scope-sharing.generated.d.ts +10 -0
  78. package/src/lib/plugin-manager/plugin-scope-sharing.generated.js +82 -0
  79. package/src/lib/plugin-manager/plugin-scope-sharing.generated.js.map +1 -0
  80. package/src/lib/plugin-manager/plugin-scope-sharing.js +85 -0
  81. package/src/lib/plugin-manager/plugin-scope-sharing.js.map +1 -0
  82. package/src/lib/plugin-manager/plugin-site-starters.d.ts +7 -0
  83. package/src/lib/plugin-manager/plugin-site-starters.js.map +1 -1
  84. package/src/lib/plugin-manager/plugin-transfer-resources.d.ts +56 -1
  85. package/src/lib/plugin-manager/plugin-transfer-resources.js +13 -0
  86. package/src/lib/plugin-manager/plugin-transfer-resources.js.map +1 -1
@@ -352,7 +352,7 @@ export const DOCS_SECTION_INDEX = [
352
352
  title: 'Privacy and Aglyn AI',
353
353
  heading: 'Turn AI off',
354
354
  anchor: '#turn-ai-off',
355
- text: 'A site admin can switch AI off for one site; every AI request for that site is then refused. See Switch AI off for one site. A member whose role lacks the AI permissions cannot use AI at all; see Who can use it.'
355
+ text: 'A member holding Manage site settings, which a site\'s admins hold by default, can switch AI off for one site; every AI request for that site is then refused. See Switch AI off for one site. A member whose role lacks the AI permissions cannot use AI at all; see Who can use it.'
356
356
  },
357
357
  {
358
358
  path: '/ai/ai-privacy',
@@ -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',
@@ -562,7 +562,7 @@ export const DOCS_SECTION_INDEX = [
562
562
  title: 'Bring my site',
563
563
  heading: 'Waves',
564
564
  anchor: '#waves',
565
- text: '- The first wave brings in your main pages: home, then the pages in your menu, then your other top-level pages. Before any page, it gives your new site its look. With Improve it, that is the built-in theme that fits your kind of site, in your brand\'s colors and fonts. With Keep my site, it is your current site\'s look, on one of Aglyn\'s built-in themes: your buttons\' color as its main color and your links\' color beside it, the color of the small labels above your headings as its third color, your pages\' background color, the rounding of your buttons, and your own font when Google Fonts has it, or a font in the same style when it does not. Colors are kept readable, so a color too light for white words is used a shade deeper. If you already chose a theme for the new site, it is kept.\n- Your header and footer come in with the first wave, as your current site shows them: your logo, your name, or both; your menu, each dropdown as a Dropdown Menu or a Mega Menu with its entries, their icons and the line under each; and your buttons, such as Sign in or Start free, going where they go now. A large dropdown keeps its columns in the same order, side by side and as wide as yours, with each column\'s heading and words, its featured picture, its light or dark box, and the colored tile behind each icon. Every label stays on one line, and on a screen too narrow for the whole menu it becomes a menu button that opens every menu and button.\n- Your menus open the way they do now. A menu that opens when you point at it opens the same way on a computer, and clicking its name opens that page, as it does on your current site. A menu name with no page of its own opens its menu on a click. A menu that only opens on a click stays that way. In the menu on a phone, tap a menu\'s name to open or close'
565
+ text: '- The first wave brings in your main pages: home, then the pages in your menu, then your other top-level pages. Before any page, it gives your new site its look. With Improve it, that is the built-in theme that fits your kind of site, in your brand\'s colors and fonts. With Keep my site, it is your current site\'s look, on one of Aglyn\'s built-in themes: your buttons\' color as its main color and your links\' color beside it, the color of the small labels above your headings as its third color, your pages\' background color, the rounding of your buttons, and your own font when Google Fonts has it, or a font in the same style when it does not. Colors are kept readable. With Improve it, a color too light for white words is used a shade deeper. With Keep my site, your buttons keep their color and take dark words on a color too light for white ones, while links and outlined buttons use a shade that reads. If you already chose a theme for the new site, it is kept.\n- Your header and footer come in with the first wave, as your current site shows them: your logo, your name, or both; your menu, each dropdown as a Dropdown Menu or a Mega Menu with its entries, their icons and the line under each; and your buttons, such as Sign in or Start free, going where they go now. A large dropdown keeps its columns in the same order, side by side and as wide as yours, with each column\'s heading and words, its featured picture, its light or dark box, and the colored tile behind each icon. Every label stays on one line, and on a screen too narrow for the whole menu it becomes a menu button that opens every menu and button.\n- Your menus open the way they do now. A menu that opens when you point at it opens the same way on a computer, and clicking its name opens that page, as it does on your current '
566
566
  },
567
567
  {
568
568
  path: '/ai/bring-my-site',
@@ -625,7 +625,7 @@ export const DOCS_SECTION_INDEX = [
625
625
  title: 'Business profile',
626
626
  heading: 'Where the values come from',
627
627
  anchor: '#where-the-values-come-from',
628
- text: 'When a site is started with Aglyn AI, the profile is filled from your answers to the guided start, including the Year founded from More details, and from what the plan wrote about the business. Each field says where its value came from:\n- Your answers when the site was started, or Suggested by Aglyn AI: a suggestion. Edit it and it becomes yours.\n- An empty field that Aglyn AI still has a value for says so: the description in your SEO settings, or the workspace\'s default.\nWhat you type is never replaced. A later job can fill an empty field, but it never overwrites one you wrote, and a field you cleared stays clear.\nWorkspace defaults {#workspace-defaults}\nSettings → Profile has a Business profile defaults card. A site uses those values wherever its own profile is empty, so a workspace that runs many sites for one business writes them once. Only managers can change them. The year founded is set on each site\'s own card. The default Area served is used only by a site whose Areas served on Setup → SEO → Local business is empty.'
628
+ text: 'When a site is started with Aglyn AI, the profile is filled from your answers to the guided start, including the Year founded from More details, and from what the plan wrote about the business. Each field says where its value came from:\n- Your answers when the site was started, or Suggested by Aglyn AI: a suggestion. Edit it and it becomes yours.\n- An empty field that Aglyn AI still has a value for says so: the description in your SEO settings, or the workspace\'s default.\nWhat you type is never replaced. A later job can fill an empty field, but it never overwrites one you wrote, and a field you cleared stays clear.\nWorkspace defaults {#workspace-defaults}\nSettings → Profile has a Business profile defaults card. A site uses those values wherever its own profile is empty, so a workspace that runs many sites for one business writes them once. Changing them takes the Business profile permission, which workspace owners and admins hold by default. The year founded is set on each site\'s own card. The default Area served is used only by a site whose Areas served on Setup → SEO → Local business is empty.'
629
629
  },
630
630
  {
631
631
  path: '/ai/business-profile',
@@ -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 an owner or admin 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- an owner or admin 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',
@@ -1227,7 +1227,7 @@ export const DOCS_SECTION_INDEX = [
1227
1227
  title: 'Aglyn AI: the AI website builder',
1228
1228
  heading: 'Switch AI off for one site',
1229
1229
  anchor: '#switch-ai-off-for-one-site',
1230
- text: 'AI is on for every site in a workspace. A site admin can switch it off for one site on that site\'s Admin → Plugins → AI page, and the page says, beside the switch, what switching it off stops and what it leaves running.\nWith AI off for a site:\n- the assistant, Create with AI on the Pages, Templates, Layouts, Forms, Components and Media pages, the SEO and theme cards, the editor\'s Rewrite with AI, Generate a section with AI and Make a reusable component with AI controls, and the AI columns on the site\'s collaborators card are gone from that site;\n- every AI request made for the site is refused with AI is switched off for this site., including one sent from a tab that was open before the switch;\n- an AI job already queued for the site stops with the same sentence, and spends no credits. A job that stopped does not restart when AI is switched back on.\nSwitching AI off for a site does not stop the workspace\'s credits, its blocks of AI credits, allotments or overage billing. AI keeps working on the workspace\'s other sites and on workspace pages such as Billing, and an agency batch still builds the sites in it that have AI on.'
1230
+ text: 'AI is on for every site in a workspace. A member holding Manage site settings, which a site\'s admins hold by default, can switch it off for one site on that site\'s Admin → Plugins → AI page, and the page says, beside the switch, what switching it off stops and what it leaves running.\nWith AI off for a site:\n- the assistant, Create with AI on the Pages, Templates, Layouts, Forms, Components and Media pages, the SEO and theme cards, the editor\'s Rewrite with AI, Generate a section with AI and Make a reusable component with AI controls, and the AI columns on the site\'s collaborators card are gone from that site;\n- every AI request made for the site is refused with AI is switched off for this site., including one sent from a tab that was open before the switch;\n- an AI job already queued for the site stops with the same sentence, and spends no credits. A job that stopped does not restart when AI is switched back on.\nSwitching AI off for a site does not stop the workspace\'s credits, its blocks of AI credits, allotments or overage billing. AI keeps working on the workspace\'s other sites and on workspace pages such as Billing, and an agency batch still builds the sites in it that have AI on.'
1231
1231
  },
1232
1232
  {
1233
1233
  path: '/ai/overview',
@@ -1500,7 +1500,7 @@ export const DOCS_SECTION_INDEX = [
1500
1500
  title: 'Start a new site with AI',
1501
1501
  heading: 'Events from the start',
1502
1502
  anchor: '#events-from-the-start',
1503
- text: 'When your business holds dated events, such as a venue, a club, a studio with classes, a meetup, a church or a theater, and your workspace has the Event Calendar add-on, the start adds your first three upcoming events to the Events page, each with a cover photo. They are dated after the day you start, in your site\'s time zone, and a day or time you gave in your description is kept as you gave it. The page about your events, or else your home page, lists them with the Event List, in one of its planned sections.\nThe events are published, so they show on your site straight away, when you have the admin or editor role on the site. With the author role they are saved as drafts, and the job says so; someone with the editor role publishes them on the Events page. Without the add-on the start adds no events. Change or delete them on the Events page like any event.'
1503
+ text: 'When your business holds dated events, such as a venue, a club, a studio with classes, a meetup, a church or a theater, and your workspace has the Event Calendar add-on, the start adds your first three upcoming events to the Events page, each with a cover photo. They are dated after the day you start, in your site\'s time zone, and a day or time you gave in your description is kept as you gave it. The page about your events, or else your home page, lists them with the Event List, in one of its planned sections.\nThe events are published, so they show on your site straight away, when you hold the Publish site content permission on the site, which its admins and editors hold by default. Without it, as with the author role, they are saved as drafts, and the job says so; someone who holds it publishes them on the Events page. Without the add-on the start adds no events. Change or delete them on the Events page like any event.'
1504
1504
  },
1505
1505
  {
1506
1506
  path: '/ai/start-with-ai',
@@ -1822,7 +1822,7 @@ export const DOCS_SECTION_INDEX = [
1822
1822
  title: 'Edit from the live site',
1823
1823
  heading: 'Who sees it',
1824
1824
  anchor: '#who-sees-it',
1825
- text: 'The bar only appears for someone whose role on the site can edit content: Admin, Editor or Author. Workspace owners and admins are admins on every site. A Viewer doesn\'t get a read-only bar; they get no bar at all.\nNobody else gets the bar. A visitor who isn\'t signed in, or who is signed in without edit access to this site, gets the page exactly as it is.'
1825
+ text: 'The bar only appears for someone holding the Edit site content permission on the site, which the site roles Admin, Editor and Author hold by default. Workspace owners and admins are admins on every site. Someone without it, such as a Viewer, doesn\'t get a read-only bar; they get no bar at all.\nNobody else gets the bar. A visitor who isn\'t signed in, or who is signed in without edit access to this site, gets the page exactly as it is.'
1826
1826
  },
1827
1827
  {
1828
1828
  path: '/building-sites/besigner/edit-from-the-live-site',
@@ -2144,7 +2144,7 @@ export const DOCS_SECTION_INDEX = [
2144
2144
  title: 'Live co-editing & unsaved work',
2145
2145
  heading: 'Editing together',
2146
2146
  anchor: '#editing-together',
2147
- text: 'Edits are shared live, per element: change a heading while a teammate restyles the footer and you both keep your work. What lands in the document:\n- Different elements — both sets of edits apply. This is the normal case, and it just works.\n- The same element — last write wins. Co-editing shares changes; it does not merge two versions of one element.\n- A teammate\'s changes never enter your undo stack — undo rewinds only your own edits, including edits that came back to you from another of your own tabs.\nOne rough edge in undo If you try to undo a change to an element a teammate has since edited themselves, the undo will step back without visibly changing anything — Aglyn will not roll back their work on your behalf. Press undo again to keep going back through your own edits. This is uncommon, and only happens on an element two of you touched.\nAnyone with edit access to the site (a site admin or editor, or a workspace owner / admin / editor) can co-edit. Viewers see presence but their changes are refused at the door.\nLive edits are working state, not saves — the document still saves when someone presses Save, and a successful save is what makes the shared state durable.'
2147
+ text: 'Edits are shared live, per element: change a heading while a teammate restyles the footer and you both keep your work. What lands in the document:\n- Different elements — both sets of edits apply. This is the normal case, and it just works.\n- The same element — last write wins. Co-editing shares changes; it does not merge two versions of one element.\n- A teammate\'s changes never enter your undo stack — undo rewinds only your own edits, including edits that came back to you from another of your own tabs.\nOne rough edge in undo If you try to undo a change to an element a teammate has since edited themselves, the undo will step back without visibly changing anything — Aglyn will not roll back their work on your behalf. Press undo again to keep going back through your own edits. This is uncommon, and only happens on an element two of you touched.\nAnyone holding Edit site content on the site (by default a site admin, editor or author, or a workspace owner, admin or editor) can co-edit. Viewers see presence but their changes are refused at the door.\nLive edits are working state, not saves — the document still saves when someone presses Save, and a successful save is what makes the shared state durable.'
2148
2148
  },
2149
2149
  {
2150
2150
  path: '/building-sites/besigner/live-co-editing',
@@ -3033,7 +3033,7 @@ export const DOCS_SECTION_INDEX = [
3033
3033
  title: 'Connect a domain',
3034
3034
  heading: 'Disconnect',
3035
3035
  anchor: '#disconnect',
3036
- text: 'Disconnect, next to the connected domain\'s chip, releases the domain immediately — there is no confirmation step — and the Aglyn subdomain resumes serving within a minute or so. Disconnecting requires the site admin role.\nAglyn never touches your DNS: the CNAME, ALIAS, or A record at your registrar is yours, so remember to remove or repoint it yourself after disconnecting.'
3036
+ text: 'Disconnect, next to the connected domain\'s chip, releases the domain immediately — there is no confirmation step — and the Aglyn subdomain resumes serving within a minute or so. Disconnecting takes the Manage site settings permission, which a site\'s admins hold by default.\nAglyn never touches your DNS: the CNAME, ALIAS, or A record at your registrar is yours, so remember to remove or repoint it yourself after disconnecting.'
3037
3037
  },
3038
3038
  {
3039
3039
  path: '/building-sites/custom-domains/connect-a-domain',
@@ -3173,7 +3173,7 @@ export const DOCS_SECTION_INDEX = [
3173
3173
  title: 'Live chat',
3174
3174
  heading: 'Set up live chat',
3175
3175
  anchor: '#set-up-live-chat',
3176
- text: 'Connect your own Tidio or LiveChat account by its public key or license number, then choose which pages show the chat.\n1. Turn on Live chat for the site under Admin → Plugins → Live chat. It is off for every site until you turn it on.\n2. Open the site\'s Setup page and find the Live chat card.\n3. Choose your Chat service: Tidio or LiveChat.\n4. Paste the identifier from your chat service\'s install code. You can paste the whole install code and Aglyn takes the identifier out of it.\n- Tidio: the Public key, under Settings → Developer in Tidio.\n- LiveChat: the License number, in the install code under Settings → Channels → Website in LiveChat.\n5. Turn on Show the chat on this site and press Save.\nSaving refreshes your live pages, so the chat button appears within a minute. Only a site admin can change the card; everyone else on the site can see how it is set.\nTo pause the chat without losing your settings, turn off Show the chat on this site and save. Switching Live chat off under Admin → Plugins removes it from the site\'s pages too, and keeps the settings for later.'
3176
+ text: 'Connect your own Tidio or LiveChat account by its public key or license number, then choose which pages show the chat.\n1. Turn on Live chat for the site under Admin → Plugins → Live chat. It is off for every site until you turn it on.\n2. Open the site\'s Setup page and find the Live chat card.\n3. Choose your Chat service: Tidio or LiveChat.\n4. Paste the identifier from your chat service\'s install code. You can paste the whole install code and Aglyn takes the identifier out of it.\n- Tidio: the Public key, under Settings → Developer in Tidio.\n- LiveChat: the License number, in the install code under Settings → Channels → Website in LiveChat.\n5. Turn on Show the chat on this site and press Save.\nSaving refreshes your live pages, so the chat button appears within a minute. Changing the card takes the Manage site settings permission, which a site\'s admins hold by default; everyone else on the site can see how it is set.\nTo pause the chat without losing your settings, turn off Show the chat on this site and save. Switching Live chat off under Admin → Plugins removes it from the site\'s pages too, and keeps the settings for later.'
3177
3177
  },
3178
3178
  {
3179
3179
  path: '/building-sites/live-chat',
@@ -3971,7 +3971,7 @@ export const DOCS_SECTION_INDEX = [
3971
3971
  title: 'Site backup and packages',
3972
3972
  heading: '',
3973
3973
  anchor: '',
3974
- text: 'Site backup and packages\nDownload everything designable on a site as one file, a site package, or only the items you pick, and import it into the same site or another of your sites. An import compares each item in the file with what the site already holds, shows you what changes and asks how to handle each item before it writes anything, and you can undo it afterwards.\nPlan availability Pro and above. Site admins only.\nOpen Admin → Backup & template on the site.'
3974
+ text: 'Site backup and packages\nDownload everything designable on a site as one file, a site package, or only the items you pick, and import it into the same site or another of your sites. An import compares each item in the file with what the site already holds, shows you what changes and asks how to handle each item before it writes anything, and you can undo it afterwards.\nPlan availability Pro and above. Takes the Manage site settings permission, which a site\'s admins hold by default.\nOpen Admin → Backup & template on the site.'
3975
3975
  },
3976
3976
  {
3977
3977
  path: '/building-sites/site-backup-and-packages',
@@ -4034,14 +4034,14 @@ export const DOCS_SECTION_INDEX = [
4034
4034
  title: 'Design custom error pages',
4035
4035
  heading: 'The error pages',
4036
4036
  anchor: '#the-error-screens',
4037
- text: '| Status | Picker label | When it shows |\n| 404 | 404 · Not found | The URL doesn\'t match any page. |\n| 401 | 401 · Members only | A members-only page, requested by a signed-out visitor. |\n| 403 | 403 · Forbidden | Reserved for future access rules — nothing serves it yet. |\n| 503 | 503 · Maintenance | Shown on every page while maintenance mode is on, and to visitors while the site is in preview. |'
4037
+ text: '| Status | Picker label | When it shows |\n| 404 | 404 · Not found | The URL doesn\'t match any page. |\n| 401 | 401 · Members only | A members-only page, requested by a signed-out visitor. |\n| 403 | 403 · Forbidden | Reserved for future access rules — nothing serves it yet. |\n| 503 | 503 · Maintenance | Shown to visitors while maintenance mode is on or the site is in preview. |'
4038
4038
  },
4039
4039
  {
4040
4040
  path: '/building-sites/site-protection/error-screens',
4041
4041
  title: 'Design custom error pages',
4042
4042
  heading: 'Design one',
4043
4043
  anchor: '#design-one',
4044
- text: '1. Create a page for the status, in Pages, and design it in the Besigner like any other page — add your header/layout, a helpful message, and a link home.\n2. Assign it. Go to Admin → Error pages. Each status has its own picker — 404 · Not found, 401 · Members only, 403 · Forbidden, 503 · Maintenance — listing every page on the site. Choose your page in the matching picker. The Admin area is limited to site admins, so that is who assigns these.\nStep 2 is the one that\'s easy to miss: designing a page does not make it an error page on its own. Until it\'s picked in the Error pages card, the status renders the Built-in fallback page, which is what every picker is set to until you change it.'
4044
+ text: '1. Create a page for the status, in Pages, and design it in the Besigner like any other page — add your header/layout, a helpful message, and a link home.\n2. Assign it. Go to Admin → Error pages. Each status has its own picker — 404 · Not found, 401 · Members only, 403 · Forbidden, 503 · Maintenance — listing every page on the site. Choose your page in the matching picker. The Admin area takes the Manage site settings permission, which a site\'s admins hold by default, so that is who assigns these.\nStep 2 is the one that\'s easy to miss: designing a page does not make it an error page on its own. Until it\'s picked in the Error pages card, the status renders the Built-in fallback page, which is what every picker is set to until you change it.'
4045
4045
  },
4046
4046
  {
4047
4047
  path: '/building-sites/site-protection/error-screens',
@@ -4076,21 +4076,21 @@ export const DOCS_SECTION_INDEX = [
4076
4076
  title: 'Maintenance mode',
4077
4077
  heading: '',
4078
4078
  anchor: '',
4079
- text: 'Maintenance mode\nNeed to pause your live site while you make changes? Maintenance mode serves your designed 503 page to visitors until you switch it back.\nTo keep building while only your team can see the site, use Preview instead: visitors see the same 503 page, and your team sees the whole site.'
4079
+ text: 'Maintenance mode\nNeed to pause your live site while you make changes? Maintenance mode serves your designed 503 page to visitors until you switch it back. You and your team still see the whole site, with a bar across the top that says only your team can see it.\nFor a site that hasn\'t launched yet, use Preview instead: your team sees the site the same way, and visitors without a 503 page get a Coming soon notice.'
4080
4080
  },
4081
4081
  {
4082
4082
  path: '/building-sites/site-protection/maintenance-mode',
4083
4083
  title: 'Maintenance mode',
4084
4084
  heading: 'Turn it on',
4085
4085
  anchor: '#turn-it-on',
4086
- text: '1. Open Admin → Error pages for the site — the same card that assigns your error pages. The switch takes every page of the site offline for every visitor, so the Admin area is limited to site admins.\n2. Switch on Maintenance mode — show the 503 page at every address. It confirms with "Maintenance mode on — visitors see the 503 page".\n3. Visitors now see your 503 error page on every path.\n4. When you\'re done, switch it back off and the site returns.\nIf you haven\'t assigned a 503 · Maintenance page, maintenance mode still works — but visitors get Aglyn\'s plain built-in notice ("This site is undergoing maintenance. Please check back shortly.") rather than anything on-brand. Design and assign the 503 first.'
4086
+ text: '1. Open Admin → Error pages for the site — the same card that assigns your error pages. The switch takes every page of the site offline for every visitor, so the Admin area takes the Manage site settings permission, which a site\'s admins hold by default.\n2. Switch on Maintenance mode — show the 503 page at every address. It confirms with "Maintenance mode on — visitors see the 503 page".\n3. Visitors now see your 503 error page on every path.\n4. When you\'re done, switch it back off and the site returns.\nIf you haven\'t assigned a 503 · Maintenance page, maintenance mode still works — but visitors get Aglyn\'s plain built-in notice ("This site is undergoing maintenance. Please check back shortly.") rather than anything on-brand. Design and assign the 503 first.'
4087
4087
  },
4088
4088
  {
4089
4089
  path: '/building-sites/site-protection/maintenance-mode',
4090
4090
  title: 'Maintenance mode',
4091
4091
  heading: 'Search engines and feeds',
4092
4092
  anchor: '#search-engines-and-feeds',
4093
- text: 'While maintenance mode is on, every address tells search engines the site is down for a short while and to check back later. They don\'t take your 503 page for your site\'s content, so your pages aren\'t replaced by it in search results. Your site\'s search page and its collection feeds pause too, and come back when you switch maintenance mode off.\nKeep it short on a site that\'s already live. If a site stays unavailable for more than a couple of days, search engines may start dropping its pages.'
4093
+ text: 'While maintenance mode is on, every address tells search engines the site is down for a short while and to check back later. They don\'t take your 503 page for your site\'s content, so your pages aren\'t replaced by it in search results. For visitors, your site\'s search page and its collection feeds pause too, and come back when you switch maintenance mode off.\nKeep it short on a site that\'s already live. If a site stays unavailable for more than a couple of days, search engines may start dropping its pages.'
4094
4094
  },
4095
4095
  {
4096
4096
  path: '/building-sites/site-protection/maintenance-mode',
@@ -4111,21 +4111,21 @@ export const DOCS_SECTION_INDEX = [
4111
4111
  title: 'Make your site private',
4112
4112
  heading: '',
4113
4113
  anchor: '',
4114
- text: 'Make your site private\nWant to keep your site to yourself while you build it, share it with a client before launch, or keep it to a few people for good? Aglyn doesn\'t have a single "private" switch that puts every page behind one password. Instead, pick the setting that matches who should still get in:\n| Who should see the site | Use | Where | Plan |\n| Only you and your team, while you finish it | Preview | Admin → Error pages (also offered when you create a site) | Every plan |\n| No one yet. Not visitors, not search engines, not someone with the link | Maintenance mode | Admin → Error pages | Every plan |\n| Anyone with the link, but keep it off Google | Discourage search engines | Setup → SEO → Search engines | Every plan |\n| Only people you give a password to | Password protected, page by page | The page\'s Page Access card | Every plan |\n| Only people signed in to your site | Members only, page by page | The page\'s Page Access card | Pro and up |\nHiding a page from search doesn\'t stop people opening it. Only preview, maintenance mode, a page password, and members-only actually keep visitors out.'
4114
+ text: 'Make your site private\nWant to keep your site to yourself while you build it, share it with a client before launch, or keep it to a few people for good? Aglyn doesn\'t have a single "private" switch that puts every page behind one password. Instead, pick the setting that matches who should still get in:\n| Who should see the site | Use | Where | Plan |\n| Only you and your team, while you finish it | Preview | Admin → Error pages (also offered when you create a site) | Every plan |\n| Your team only, while a live site is paused. Not visitors, not search engines, not someone with the link | Maintenance mode | Admin → Error pages | Every plan |\n| Anyone with the link, but keep it off Google | Discourage search engines | Setup → SEO → Search engines | Every plan |\n| Only people you give a password to | Password protected, page by page | The page\'s Page Access card | Every plan |\n| Only people signed in to your site | Members only, page by page | The page\'s Page Access card | Pro and up |\nHiding a page from search doesn\'t stop people opening it. Only preview, maintenance mode, a page password, and members-only actually keep visitors out.'
4115
4115
  },
4116
4116
  {
4117
4117
  path: '/building-sites/site-protection/make-your-site-private',
4118
4118
  title: 'Make your site private',
4119
4119
  heading: 'Keep it to your team with Preview',
4120
4120
  anchor: '#keep-it-to-your-team-with-preview',
4121
- text: 'Preview keeps the whole site to the people building it. Visitors see your 503 page, or a plain Coming soon notice if you haven\'t designed one, at every address. You and your team see the whole site: every page, your header and footer, collections and working forms, with a bar across the top that says only your team can see it. When you\'re ready, you flip one switch and the site is public to everyone.\n1. Open Admin → Error pages for the site. Only site admins can open the Admin area.\n2. Switch on Preview — only you and your team can see the site. It confirms with "Your site is in preview — only you and your team can see it".\n3. Keep building. A banner, "This site is in preview", follows you around the site\'s console pages so it isn\'t forgotten at launch, and the site\'s card in Sites reads In preview.\n4. On launch day, switch Preview off. Make it public on the banner takes you straight to the switch. Your pages are public within about a minute.\nWho sees what\n- Visitors see your 503 · Maintenance page if you\'ve assigned one (see custom error pages), or a Coming soon notice with your site\'s name. Design the 503 page first if you want visitors to see your brand.\n- Your team sees the whole site. That is anyone who can open the site in the console: workspace owners and admins, members who look after every site, and anyone with a role on this site. Someone who is only on other sites of your workspace doesn\'t see it.\n- Aglyn support can see it too, so they can help you with it before it\'s public.\n- People who signed up on your site (its member accounts) are visitors, not your team, so they see the 503 page.\nOpen your site while it\'s in preview\nChoose Visit site on the site\'s dashboard, or Visit on its card in Sites. While the site is in preview these buttons sign you in to the s'
4121
+ text: 'Preview keeps the whole site to the people building it. Visitors see your 503 page, or a plain Coming soon notice if you haven\'t designed one, at every address. You and your team see the whole site: every page, your header and footer, collections and working forms, with a bar across the top that says only your team can see it. When you\'re ready, you flip one switch and the site is public to everyone.\n1. Open Admin → Error pages for the site. Opening the Admin area takes the Manage site settings permission, which a site\'s admins hold by default.\n2. Switch on Preview — only you and your team can see the site. It confirms with "Your site is in preview — only you and your team can see it".\n3. Keep building. A banner, "This site is in preview", follows you around the site\'s console pages so it isn\'t forgotten at launch, and the site\'s card in Sites reads In preview.\n4. On launch day, switch Preview off. Make it public on the banner takes you straight to the switch. Your pages are public within about a minute.\nWho sees what\n- Visitors see your 503 · Maintenance page if you\'ve assigned one (see custom error pages), or a Coming soon notice with your site\'s name. Design the 503 page first if you want visitors to see your brand.\n- Your team sees the whole site. That is anyone who can open the site in the console: workspace owners and admins, members who look after every site, and anyone with a role on this site. Someone who is only on other sites of your workspace doesn\'t see it.\n- Aglyn support can see it too, so they can help you with it before it\'s public.\n- People who signed up on your site (its member accounts) are visitors, not your team, so they see the 503 page.\nOpen your site while it\'s in preview\nChoose Visit site on the site\'s dashboard, or Visit on its card in Sites. '
4122
4122
  },
4123
4123
  {
4124
4124
  path: '/building-sites/site-protection/make-your-site-private',
4125
4125
  title: 'Make your site private',
4126
4126
  heading: 'Hide the whole site until launch',
4127
4127
  anchor: '#hide-the-whole-site-until-launch',
4128
- text: 'Maintenance mode is the way to make the whole site private in one step. Every address on the site shows your 503 page to every visitor, including anyone who already has a link, and pages you add later are covered too.\n1. (Optional) Design a 503 · Maintenance page in the Besigner, such as a short "Coming soon" with your logo, and assign it in Admin → Error pages. See custom error pages. Without one, visitors see Aglyn\'s plain built-in notice.\n2. In the same Admin → Error pages card, switch on Maintenance mode — show the 503 page at every address. Only site admins can open the Admin area.\n3. Keep building. You and your team still edit pages, layouts and content in the console and the Besigner as usual. Maintenance mode only changes what the published site shows.\n4. On launch day, switch maintenance mode off. Your pages are live again within about a minute.\nSearch engines are told the site is temporarily unavailable, and the 503 page is never offered to them, so nothing about the unfinished site gets indexed while maintenance mode is on. The site\'s search page and its collection feeds pause too. See Search engines and feeds.\nKeep one page open instead If you\'d rather keep a "coming soon" page open to collect email sign-ups while the rest of the site stays out of search, follow Launch a coming-soon page.'
4128
+ text: 'Maintenance mode is the way to make the whole site private in one step. Every address on the site shows your 503 page to every visitor, including anyone who already has a link, and pages you add later are covered too. You and your team still see the whole site.\n1. (Optional) Design a 503 · Maintenance page in the Besigner, such as a short "Coming soon" with your logo, and assign it in Admin → Error pages. See custom error pages. Without one, visitors see Aglyn\'s plain built-in notice.\n2. In the same Admin → Error pages card, switch on Maintenance mode — show the 503 page at every address. Opening the Admin area takes the Manage site settings permission, which a site\'s admins hold by default.\n3. Keep building. You and your team still edit pages, layouts and content in the console and the Besigner as usual. Maintenance mode only changes what the published site shows.\n4. On launch day, switch maintenance mode off. Your pages are live again within about a minute.\nSearch engines are told the site is temporarily unavailable, and the 503 page is never offered to them, so nothing about the unfinished site gets indexed while maintenance mode is on. For visitors, the site\'s search page and its collection feeds pause too. See Search engines and feeds.\nKeep one page open instead If you\'d rather keep a "coming soon" page open to collect email sign-ups while the rest of the site stays out of search, follow Launch a coming-soon page.'
4129
4129
  },
4130
4130
  {
4131
4131
  path: '/building-sites/site-protection/make-your-site-private',
@@ -4153,7 +4153,7 @@ export const DOCS_SECTION_INDEX = [
4153
4153
  title: 'Make your site private',
4154
4154
  heading: 'Ask Aglyn AI',
4155
4155
  anchor: '#ask-aglyn-ai',
4156
- text: 'You can ask Assist to make these changes for you, such as make my site private until launch, hide the site from Google, make the pricing page members only or put the site back online. Assist shows the change on a plan card, and nothing changes until you confirm it. It\'s then saved to your live site straight away, just as if you\'d used the switch yourself, and it uses no AI credits.\n- Maintenance mode can only be turned on or off by a site admin, as in the Admin area. If you\'re an editor or author, Assist makes the rest of your request and says it left maintenance mode alone.\n- Members only is set only on the Pro plan and up. On other plans, Assist says why it left the page as it was.\n- Passwords are never set by Assist, so a password never goes into the chat. Set it in the page\'s Page Access card, as in Share it behind a password.\nAsking how, such as how do I make my site private?, gets you the steps on this page instead. Building from the chat needs AI generation on your plan; see Build from Assist chat.'
4156
+ text: 'You can ask Assist to make these changes for you, such as make my site private until launch, hide the site from Google, make the pricing page members only or put the site back online. Assist shows the change on a plan card, and nothing changes until you confirm it. It\'s then saved to your live site straight away, just as if you\'d used the switch yourself, and it uses no AI credits.\n- Maintenance mode needs the Manage site settings permission to turn on or off, as in the Admin area. A site\'s admins hold it by default. Without it, Assist makes the rest of your request and says it left maintenance mode alone.\n- Members only is set only on the Pro plan and up. On other plans, Assist says why it left the page as it was.\n- Passwords are never set by Assist, so a password never goes into the chat. Set it in the page\'s Page Access card, as in Share it behind a password.\nAsking how, such as how do I make my site private?, gets you the steps on this page instead. Building from the chat needs AI generation on your plan; see Build from Assist chat.'
4157
4157
  },
4158
4158
  {
4159
4159
  path: '/building-sites/site-protection/make-your-site-private',
@@ -4181,7 +4181,7 @@ export const DOCS_SECTION_INDEX = [
4181
4181
  title: 'Site Protection & Error Pages',
4182
4182
  heading: 'Where these controls live',
4183
4183
  anchor: '#where-these-controls-live',
4184
- text: 'The three features on this page are set in two different places, and neither is the pages list:\n| What you want | Where it is |\n| A page\'s visibility (public, unlisted, password, members-only) and its page password | The Page Access card on that page\'s detail view |\n| Error pages for 404 / 401 / 403 / 503 | The Error pages section of the site\'s Admin area |\n| Maintenance mode | The same Error pages section, in Admin |\nA page\'s own visibility is set by anyone who can edit that page. The Error pages section is different: both settings there are site-wide — maintenance mode replaces every page for every visitor — so, like deleting the site, they live in Admin and are limited to site admins.'
4184
+ text: 'The three features on this page are set in two different places, and neither is the pages list:\n| What you want | Where it is |\n| A page\'s visibility (public, unlisted, password, members-only) and its page password | The Page Access card on that page\'s detail view |\n| Error pages for 404 / 401 / 403 / 503 | The Error pages section of the site\'s Admin area |\n| Maintenance mode | The same Error pages section, in Admin |\nA page\'s own visibility is set by anyone who can edit that page. The Error pages section is different: both settings there are site-wide — maintenance mode replaces every page for every visitor — so, like deleting the site, they live in Admin and take the Manage site settings permission, which a site\'s admins hold by default.'
4185
4185
  },
4186
4186
  {
4187
4187
  path: '/building-sites/site-protection/overview',
@@ -4321,7 +4321,7 @@ export const DOCS_SECTION_INDEX = [
4321
4321
  title: 'Build a blog',
4322
4322
  heading: '1. Create a collection',
4323
4323
  anchor: '#1-create-a-collection',
4324
- text: 'In Content, create a collection for your posts. Manage entries from the console.\nA new collection is not a page yet. Its listing at /{collection} goes live with the first entry you publish (or a scheduled one, once its time comes), and so do its paged and category listings and its RSS feed. Until then those addresses answer 404 and your sitemap and /llms.txt leave the collection out, so an empty section never shows up on your site or in search. Unpublish or delete every entry and the listing comes down the same way.\nDelete a collection\nDelete collection is at the bottom of Collection settings, the panel under the Collection dropdown in Collections & Entries, and acts on the collection currently picked in that dropdown. It is a site admin action: if your role on this site is editor or viewer the button is not there at all, and an org role on its own does not grant it — the check reads your role on this site. Ask a site admin, or have one raise your role in Members.\nAglyn refuses the delete while anything still depends on the collection, and the dialog tells you which of these it is before you can type anything:\n- A template page still points at it. The message names the page and which picker holds it — "Blog" is still the source for "Blog index" (list template). Set that collection\'s List page or Entry page, under Template pages, back to the built-in option first. Deleting it while a published page renders from it would leave that page with nothing to draw.\n- It still has entries. The message gives the count — "Blog" still has 12 entries. Delete them from the entries table first, one at a time; deleting a collection never removes published entries for you.\nThe dialog also names the published pages, layouts and components that link to the collection\'s listing page — any B'
4324
+ text: 'In Content, create a collection for your posts. Manage entries from the console.\nA new collection is not a page yet. Its listing at /{collection} goes live with the first entry you publish (or a scheduled one, once its time comes), and so do its paged and category listings and its RSS feed. Until then those addresses answer 404 and your sitemap and /llms.txt leave the collection out, so an empty section never shows up on your site or in search. Unpublish or delete every entry and the listing comes down the same way.\nDelete a collection\nDelete collection is at the bottom of Collection settings, the panel under the Collection dropdown in Collections & Entries, and acts on the collection currently picked in that dropdown. It takes the Manage site settings permission on this site, which the site\'s admins hold by default: without it the button is not there at all. Ask a site admin, or have one raise your role in Members.\nAglyn refuses the delete while anything still depends on the collection, and the dialog tells you which of these it is before you can type anything:\n- A template page still points at it. The message names the page and which picker holds it — "Blog" is still the source for "Blog index" (list template). Set that collection\'s List page or Entry page, under Template pages, back to the built-in option first. Deleting it while a published page renders from it would leave that page with nothing to draw.\n- It still has entries. The message gives the count — "Blog" still has 12 entries. Delete them from the entries table first, one at a time; deleting a collection never removes published entries for you.\nThe dialog also names the published pages, layouts and components that link to the collection\'s listing page — any Button, Page link, Tabs link or other link pointed'
4325
4325
  },
4326
4326
  {
4327
4327
  path: '/building-sites/site-templates/build-a-blog',
@@ -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',
@@ -5364,7 +5364,7 @@ export const DOCS_SECTION_INDEX = [
5364
5364
  title: 'Commerce',
5365
5365
  heading: 'Payment methods',
5366
5366
  anchor: '#payment-methods',
5367
- text: 'The Payment methods card, on Products → Payments, chooses what shoppers may pay with besides a card, once your Stripe account is connected on the Payments card. Cards are always on. Every other method is on unless you turn it off, except stablecoins, which you turn on. Stripe shows a method only on orders it suits: the right currency, an amount inside its limits, and a shopper in a country it serves.\n| Method | What the shopper needs | Limits |\n| Apple Pay | Safari on a Mac, iPhone or iPad with a card in Apple Wallet | Same as cards |\n| Google Pay | Chrome or an Android device with a card in Google Pay | Same as cards |\n| Link | A card or bank saved with Link | Same as cards |\n| Klarna | A US shopper paying in USD | From $10 |\n| Afterpay | A US shopper paying in USD | $1 to $4,000, one-time purchases only |\n| Affirm | A US shopper paying in USD | $50 to $30,000, one-time purchases only |\n| Cash App Pay | A US shopper with Cash App | USD only |\n| Amazon Pay | An Amazon account with a saved card | USD only |\n| Stablecoins | A crypto wallet holding USDC or another supported stablecoin | USD only, up to $10,000 |\nThe card only lists the methods the platform offers. A method missing from your card is not available for storefronts yet. Anyone who manages the store can read the card; only a site admin can change it.\nUntil Stripe is connected, each method you have on reads Connect Stripe first, and a note at the top of the card links to the Payments card above it, where you connect. You can still choose your methods in the meantime; they show at checkout once Stripe is connected and approves them.\nWhat each chip means. Buy-now-pay-later, Cash App Pay, Amazon Pay and stablecoins also need Stripe to enable them on your payout account. Saving the card asks Stripe for that. Stripe '
5367
+ text: 'The Payment methods card, on Products → Payments, chooses what shoppers may pay with besides a card, once your Stripe account is connected on the Payments card. Cards are always on. Every other method is on unless you turn it off, except stablecoins, which you turn on. Stripe shows a method only on orders it suits: the right currency, an amount inside its limits, and a shopper in a country it serves.\n| Method | What the shopper needs | Limits |\n| Apple Pay | Safari on a Mac, iPhone or iPad with a card in Apple Wallet | Same as cards |\n| Google Pay | Chrome or an Android device with a card in Google Pay | Same as cards |\n| Link | A card or bank saved with Link | Same as cards |\n| Klarna | A US shopper paying in USD | From $10 |\n| Afterpay | A US shopper paying in USD | $1 to $4,000, one-time purchases only |\n| Affirm | A US shopper paying in USD | $50 to $30,000, one-time purchases only |\n| Cash App Pay | A US shopper with Cash App | USD only |\n| Amazon Pay | An Amazon account with a saved card | USD only |\n| Stablecoins | A crypto wallet holding USDC or another supported stablecoin | USD only, up to $10,000 |\nThe card only lists the methods the platform offers. A method missing from your card is not available for storefronts yet. Anyone holding Manage orders can read the card; changing it takes Manage payment methods, which a site\'s admins hold by default.\nUntil Stripe is connected, each method you have on reads Connect Stripe first, and a note at the top of the card links to the Payments card above it, where you connect. You can still choose your methods in the meantime; they show at checkout once Stripe is connected and approves them.\nWhat each chip means. Buy-now-pay-later, Cash App Pay, Amazon Pay and stablecoins also need Stripe to enable them on your payout accoun'
5368
5368
  },
5369
5369
  {
5370
5370
  path: '/commerce-and-bookings/commerce/overview',
@@ -5455,7 +5455,7 @@ export const DOCS_SECTION_INDEX = [
5455
5455
  title: 'Pickup & local delivery',
5456
5456
  heading: 'Ask Aglyn AI',
5457
5457
  anchor: '#ask-aglyn-ai',
5458
- text: 'You can ask Aglyn Assist to set up pickup or delivery, such as offer local pickup at our Austin shop, weekdays 9 to 5 or deliver to 78701 and 78702 for $5, free over $75, weekday mornings. The plan card lists each change, and Confirm plan saves it.\n- Pickup is turned on for one of your inventory locations, found by its name, city or street. Aglyn AI never adds a location: add it first, then ask. Without a location, it turns on the store-wide Offer free local pickup choice.\n- Local delivery uses postal-code zones. Aglyn AI turns delivery on only when checkout can offer it: a country, at least one zone and at least one delivery window. Distance zones need your store placed on the map, so you set those up yourself.\n- It uses only the fees and times you give.\n- Changes work as soon as they are saved, and cost no AI credits.\n- Only an admin or editor on the site can ask Aglyn AI for these changes. An author can still make them on the card.'
5458
+ text: 'You can ask Aglyn Assist to set up pickup or delivery, such as offer local pickup at our Austin shop, weekdays 9 to 5 or deliver to 78701 and 78702 for $5, free over $75, weekday mornings. The plan card lists each change, and Confirm plan saves it.\n- Pickup is turned on for one of your inventory locations, found by its name, city or street. Aglyn AI never adds a location: add it first, then ask. Without a location, it turns on the store-wide Offer free local pickup choice.\n- Local delivery uses postal-code zones. Aglyn AI turns delivery on only when checkout can offer it: a country, at least one zone and at least one delivery window. Distance zones need your store placed on the map, so you set those up yourself.\n- It uses only the fees and times you give.\n- Changes work as soon as they are saved, and cost no AI credits.\n- Asking Aglyn AI for these changes takes the Publish site content permission, which a site\'s admins and editors hold by default. An author can still make them on the card.'
5459
5459
  },
5460
5460
  {
5461
5461
  path: '/commerce-and-bookings/commerce/pickup-and-local-delivery',
@@ -5532,7 +5532,7 @@ export const DOCS_SECTION_INDEX = [
5532
5532
  title: 'POS & reservations',
5533
5533
  heading: 'Self-service kiosk',
5534
5534
  anchor: '#self-service-kiosk',
5535
- text: 'A self-service kiosk is a tablet your customers order from themselves. They browse your products by category, choose sizes and modifiers, review the total with tax, and pay — or send the order to the counter. It belongs to one register, and its orders are register sales: the same prices, tax, automatic promotions and stock as a sale you ring up.\nThe kiosk offers your active products except subscription-only products, gift cards and digital downloads, which need more than a counter can hand over. You choose the rest: turn off Offer on the kiosk on a product, or clear one of its variants, to keep it off the kiosk (see Offer on the kiosk).\nTo pair one:\n1. Tap Pair display on the register, or beside the register under Products → Point of sale → POS devices, then choose Self-service kiosk. It shows an address and a 6-digit code that works once and expires in 10 minutes.\n2. On the tablet, open that address — your console address followed by /kiosk/commerce/pos-kiosk — and enter the code. No one signs in on the tablet. A customer display code does not pair a kiosk, and a kiosk code does not pair a display.\nWhile you pair a kiosk, the code screen also says what the kiosk still needs to take payment, each with a link to where you fix it:\n- Stripe — until your store\'s Stripe account is connected and can take charges, the kiosk can\'t take cards. Open Payments goes to Products → Payments.\n- A card reader on this register — Pay with card uses a reader assigned to the kiosk\'s register, not one set to Any register. Open POS devices goes to the card readers on Products → Point of sale. With several readers on the register, choose the kiosk\'s from its staff menu once it is paired.\n- A way to pay at all — with Kiosk: let customers pay at the counter off and no card reader ready, customer'
5535
+ text: 'A self-service kiosk is a tablet your customers order from themselves. They browse your products by category, choose sizes and modifiers, review the total with tax, and pay — or send the order to the counter. It belongs to one register, and its orders are register sales: the same prices, tax, automatic promotions and stock as a sale you ring up.\nThe kiosk offers your active products except subscription-only products, gift cards and digital downloads, which need more than a counter can hand over. You choose the rest: turn off Offer on the kiosk on a product, or clear one of its variants, to keep it off the kiosk (see Offer on the kiosk).\nWhen you have more products than the menu lists at once, it also shows Search the menu, so a customer can find any of them by name.\nTo pair one:\n1. Tap Pair display on the register, or beside the register under Products → Point of sale → POS devices, then choose Self-service kiosk. It shows an address and a 6-digit code that works once and expires in 10 minutes.\n2. On the tablet, open that address — your console address followed by /kiosk/commerce/pos-kiosk — and enter the code. No one signs in on the tablet. A customer display code does not pair a kiosk, and a kiosk code does not pair a display.\nWhile you pair a kiosk, the code screen also says what the kiosk still needs to take payment, each with a link to where you fix it:\n- Stripe — until your store\'s Stripe account is connected and can take charges, the kiosk can\'t take cards. Open Payments goes to Products → Payments.\n- A card reader on this register — Pay with card uses a reader assigned to the kiosk\'s register, not one set to Any register. Open POS devices goes to the card readers on Products → Point of sale. With several readers on the register, choose the kiosk\'s from its staff'
5536
5536
  },
5537
5537
  {
5538
5538
  path: '/commerce-and-bookings/commerce/pos-and-reservations',
@@ -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',
@@ -6099,7 +6106,7 @@ export const DOCS_SECTION_INDEX = [
6099
6106
  title: 'Sales channels',
6100
6107
  heading: 'Turn sales channels off for a site',
6101
6108
  anchor: '#turn-off',
6102
- text: 'Sales channels are on for every site in a workspace. A site admin can switch them off for one site under Admin → Plugins → Sales channels. Every feed of that site, the earlier Google address included, then stops answering; each feed\'s address, switch and the defaults are kept for when it is switched back on.'
6109
+ text: 'Sales channels are on for every site in a workspace. A member holding Manage site settings, which a site\'s admins hold by default, can switch them off for one site under Admin → Plugins → Sales channels. Every feed of that site, the earlier Google address included, then stops answering; each feed\'s address, switch and the defaults are kept for when it is switched back on.'
6103
6110
  },
6104
6111
  {
6105
6112
  path: '/commerce-and-bookings/commerce/sales-channels',
@@ -6183,7 +6190,7 @@ export const DOCS_SECTION_INDEX = [
6183
6190
  title: 'Shipping',
6184
6191
  heading: 'Ask Aglyn AI',
6185
6192
  anchor: '#ask-aglyn-ai',
6186
- text: 'You can ask Aglyn Assist to set up shipping in plain words, such as free shipping over $50, otherwise $5 flat in the US, add $15 express to Canada or stop shipping to the UK. The plan card lists each change, and Confirm plan saves it.\n- Aglyn AI saves exactly what this card saves: a zone with its countries, and a flat, free-over-subtotal, subtotal-tier or weight-tier rate in it. A zone or rate you already have is changed in place, found by its name.\n- It uses only the prices you give. A rate you do not price is not added; Aglyn AI asks instead.\n- If the change leaves some destinations with no rate, the build says so, as the Coverage line does.\n- Changes work as soon as they are saved, like a save on this card. They cost no AI credits.\n- Only an admin or editor on the site can ask Aglyn AI for these changes. An author can still make them on the card.'
6193
+ text: 'You can ask Aglyn Assist to set up shipping in plain words, such as free shipping over $50, otherwise $5 flat in the US, add $15 express to Canada or stop shipping to the UK. The plan card lists each change, and Confirm plan saves it.\n- Aglyn AI saves exactly what this card saves: a zone with its countries, and a flat, free-over-subtotal, subtotal-tier or weight-tier rate in it. A zone or rate you already have is changed in place, found by its name.\n- It uses only the prices you give. A rate you do not price is not added; Aglyn AI asks instead.\n- If the change leaves some destinations with no rate, the build says so, as the Coverage line does.\n- Changes work as soon as they are saved, like a save on this card. They cost no AI credits.\n- Asking Aglyn AI for these changes takes the Publish site content permission, which a site\'s admins and editors hold by default. An author can still make them on the card.'
6187
6194
  },
6188
6195
  {
6189
6196
  path: '/commerce-and-bookings/commerce/shipping',
@@ -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',
@@ -6547,7 +6554,7 @@ export const DOCS_SECTION_INDEX = [
6547
6554
  title: 'Waivers',
6548
6555
  heading: 'Write a waiver',
6549
6556
  anchor: '#write-a-waiver',
6550
- text: '1. Open Waivers and select New waiver.\n2. Give it a Title, like Rider release and waiver. Signers see it at the top.\n3. Write the Waiver text in your own words. Use the toolbar for headings, bold text and lists.\n4. Under Boxes every signer must tick, add the statements a signer must agree to one by one, like I have read this waiver and I understand it. Nobody can sign until every box is ticked.\n5. Choose the Adult age, from 18 to 21. Signers younger than that need a parent or guardian to sign for them (see Minors). It starts at 18.\n6. Leave A parent or guardian may sign for riders under 18 on if minors ride. The number in it follows the adult age you chose.\n7. Choose how long one signature is good for (see How long a signature lasts).\n8. Select Save, then Publish.\nA waiver takes signatures only while it is Published. Unpublish pauses it, and Retire stops it for good. Neither one touches the signatures already taken.\nYour waiver, your words Aglyn doesn\'t write or review what your waiver says. Ask your own lawyer what yours should cover and how your state treats waivers, especially ones signed for minors.\nVersions\nEvery time you save a change to the words, the boxes, the adult age, the minors setting or how long it lasts, the waiver gets a new version. Version history lists each one. Signatures already taken keep the version they signed and stay valid for the days they cover, and their signed copy shows those words, not the new ones. If a waiver changes while somebody is filling it in, they\'re asked to read the new version before they sign.'
6557
+ text: '1. Open Waivers and select New waiver.\n2. Give it a Title, like Rider release and waiver. Signers see it at the top.\n3. Write the Waiver text in your own words. Use the toolbar for headings, bold text and lists.\n4. Under Boxes every signer must tick, add the statements a signer must agree to one by one, like I have read this waiver and I understand it. Nobody can sign until every box is ticked.\n5. Choose the Adult age, from 18 to 21. Signers younger than that need a parent or guardian to sign for them (see Minors). It starts at 18.\n6. Leave A parent or guardian may sign for people under 18 on if minors ride. The number in it follows the adult age you chose.\n7. Choose how long one signature is good for (see How long a signature lasts).\n8. Select Save, then Publish.\nA waiver takes signatures only while it is Published. Unpublish pauses it, and Retire stops it for good. Neither one touches the signatures already taken.\nYour waiver, your words Aglyn doesn\'t write or review what your waiver says. Ask your own lawyer what yours should cover and how your state treats waivers, especially ones signed for minors.\nVersions\nEvery time you save a change to the words, the boxes, the adult age, the minors setting or how long it lasts, the waiver gets a new version. Version history lists each one. Signatures already taken keep the version they signed and stay valid for the days they cover, and their signed copy shows those words, not the new ones. If a waiver changes while somebody is filling it in, they\'re asked to read the new version before they sign.'
6551
6558
  },
6552
6559
  {
6553
6560
  path: '/commerce-and-bookings/commerce/waivers',
@@ -6575,14 +6582,14 @@ export const DOCS_SECTION_INDEX = [
6575
6582
  title: 'Waivers',
6576
6583
  heading: 'At check-in',
6577
6584
  anchor: '#at-check-in',
6578
- text: 'When you check people in at the register (see Check-in at the window), each customer shows their waiver for the day:\n- Waiver signed: a signature covers today.\n- Signed for 2 of 3 riders: a signature covers today, but for fewer people than the customer is checking in. Have the rest sign.\n- Waiver needed or Waiver not on file: nobody has signed for today yet.\n- Waiver not matched — check by name: no waiver was signed with the customer\'s email, and the register doesn\'t know their date of birth, so it can\'t tell whether someone signed for them under another email, such as a parent. It never guesses from a name alone.\nSelect Sign waiver to sign right there on the register\'s device, the same way as at the window. The status updates when you\'re done.\nHow a rider is matched to a waiver {#how-a-rider-is-matched}\nA customer is matched to a waiver by the email they bought with first. When no waiver was signed with that email, they are matched by their full name and date of birth together: the person who signed, or a minor a parent or guardian listed on their waiver. Capital letters and extra spaces in the name don\'t matter; the spelling and the date of birth must be the same. A name on its own is never a match, because two riders can share one.\nWhen the customer is one of your contacts and their record on this site has a Birthdate, that birth date is used, with their name, so you don\'t have to ask. A birth date another of your sites keeps is never used.\nWhen a customer shows Waiver not matched — check by name, select Find by name. Ask the rider their date of birth, enter it beside their name and select Check: it says whether a signed waiver covers them today. Below it, the signatures search opens on their name, so you can read through the waivers signed with it.\nOn the customer d'
6585
+ text: 'When you check people in at the register (see Check-in at the window), each customer shows their waiver for the day:\n- Waiver signed: a signature covers today.\n- Signed for 2 of 3 people: a signature covers today, but for fewer people than the customer is checking in. Have the rest sign.\n- Waiver needed or Waiver not on file: nobody has signed for today yet.\n- Waiver not matched — check by name: no waiver was signed with the customer\'s email, and the register doesn\'t know their date of birth, so it can\'t tell whether someone signed for them under another email, such as a parent. It never guesses from a name alone.\nSelect Sign waiver to sign right there on the register\'s device, the same way as at the window. The status updates when you\'re done.\nHow a rider is matched to a waiver {#how-a-rider-is-matched}\nA customer is matched to a waiver by the email they bought with first. When no waiver was signed with that email, they are matched by their full name and date of birth together: the person who signed, or a minor a parent or guardian listed on their waiver. Capital letters and extra spaces in the name don\'t matter; the spelling and the date of birth must be the same. A name on its own is never a match, because two riders can share one.\nWhen the customer is one of your contacts and their record on this site has a Birthdate, that birth date is used, with their name, so you don\'t have to ask. A birth date another of your sites keeps is never used.\nWhen a customer shows Waiver not matched — check by name, select Find by name. Ask the rider their date of birth, enter it beside their name and select Check: it says whether a signed waiver covers them today. Below it, the signatures search opens on their name, so you can read through the waivers signed with it.\nOn the customer d'
6579
6586
  },
6580
6587
  {
6581
6588
  path: '/commerce-and-bookings/commerce/waivers',
6582
6589
  title: 'Waivers',
6583
6590
  heading: 'Minors',
6584
6591
  anchor: '#minors',
6585
- text: 'Each waiver sets its own Adult age, from 18 to 21. It starts at 18, and every waiver written before the setting existed reads as 18. The examples here use 18.\nWhen A parent or guardian may sign for riders under 18 is on, the signer can turn on I\'m also signing for riders under 18 and add each minor\'s full name and date of birth, then say how they\'re related to them, like Parent or Legal guardian. One signature covers the adult and every minor on it.\nThe signer must be the adult age or older on the day they sign. Anyone younger can\'t sign for themselves, and a "minor" who is the adult age or older is asked to sign their own waiver. Someone whose birthday is today counts as that age today.\nChanging the adult age starts a new version. Signatures already taken stay valid for the version they signed.'
6592
+ text: 'Each waiver sets its own Adult age, from 18 to 21. It starts at 18, and every waiver written before the setting existed reads as 18. The examples here use 18.\nWhen A parent or guardian may sign for people under 18 is on, the signer can turn on I\'m also signing for people under 18 and add each minor\'s full name and date of birth, then say how they\'re related to them, like Parent or Legal guardian. One signature covers the adult and every minor on it.\nThe signer must be the adult age or older on the day they sign. Anyone younger can\'t sign for themselves, and a "minor" who is the adult age or older is asked to sign their own waiver. Someone whose birthday is today counts as that age today.\nChanging the adult age starts a new version. Signatures already taken stay valid for the version they signed.'
6586
6593
  },
6587
6594
  {
6588
6595
  path: '/commerce-and-bookings/commerce/waivers',
@@ -6603,7 +6610,7 @@ export const DOCS_SECTION_INDEX = [
6603
6610
  title: 'Waivers',
6604
6611
  heading: 'Contacts',
6605
6612
  anchor: '#contacts',
6606
- text: 'A signer who gives an email is added to your contacts, or matched to the contact you already have for them, with the signing on their timeline. Their source reads Waiver signed in your contacts list, on their record and in the contact reports.'
6613
+ text: 'A signer who gives an email is added to your contacts, or matched to the contact you already have for them, with the signing on their timeline. Their source reads Waiver signed in your contacts list, on their record and in the contact reports, and the list\'s Source filter finds everyone who came in that way.'
6607
6614
  },
6608
6615
  {
6609
6616
  path: '/commerce-and-bookings/commerce/waivers',
@@ -6617,7 +6624,7 @@ export const DOCS_SECTION_INDEX = [
6617
6624
  title: 'Waivers',
6618
6625
  heading: 'How long signed waivers are kept',
6619
6626
  anchor: '#keeping-signed-waivers',
6620
- text: 'A signed waiver is your record of what a rider agreed to. Every one is kept for your retention period, then deleted, with its drawn signature and any photo of a paper page. A signature\'s record shows Kept until and the date it will be deleted.\nThe retention period is counted from the last day the waiver covers. For a waiver signed for minors, it\'s counted from the day the youngest of them reaches the waiver\'s adult age, if that\'s later.\nWhen you erase a person from your workspace, the waivers they signed are kept for the same period, not erased:\n- its link to the person\'s contact is removed, because the contact is erased;\n- on the Signatures card its status reads Kept until and the date it will be deleted, and its record says when the person asked;\n- a waiver whose period has already run out is deleted when the erasure runs.\nTo set the period:\n1. Go to Sites → your site → Admin → Plugins and select Waivers.\n2. On the Waivers settings card, set Years to keep a signed waiver, from 1 to 30. It starts at 7.\n3. Press Save site settings.\nTo give every site in a workspace the same period, set it on the plugin\'s workspace page under Plugins. Each site follows that period unless you change it on the site\'s own page. A change applies to every waiver already signed on the site within the hour, as well as to new ones: a longer period keeps them longer, and a shorter one deletes those it has already run out on.\nAsk your lawyer Aglyn doesn\'t know how long you need to keep a signed waiver. Ask your own lawyer, especially about waivers signed for minors.'
6627
+ text: 'A signed waiver is your record of what a rider agreed to. Every one is kept for your retention period, then deleted, with its drawn signature and any photo of a paper page. A signature\'s record shows Kept until and the date it will be deleted.\nThe retention period is counted from the last day the waiver covers. For a waiver signed for minors, it\'s counted from the day the youngest of them reaches the waiver\'s adult age, if that\'s later.\nWhen you erase a person from your workspace, the waivers they signed are kept for the same period, not erased. The Erase a person card says so, with your period, before you file:\n- its link to the person\'s contact is removed, because the contact is erased;\n- on the Signatures card its status reads Kept until and the date it will be deleted, and its record says when the person asked;\n- a waiver whose period has already run out is deleted when the erasure runs.\nTo set the period:\n1. Go to Sites → your site → Admin → Plugins and select Waivers.\n2. On the Waivers settings card, set Years to keep a signed waiver, from 1 to 30. It starts at 7.\n3. Press Save site settings.\nTo give every site in a workspace the same period, set it on the plugin\'s workspace page under Plugins. Each site follows that period unless you change it on the site\'s own page. A change applies to every waiver already signed on the site within the hour, as well as to new ones: a longer period keeps them longer, and a shorter one deletes those it has already run out on.\nAsk your lawyer Aglyn doesn\'t know how long you need to keep a signed waiver. Ask your own lawyer, especially about waivers signed for minors.'
6621
6628
  },
6622
6629
  {
6623
6630
  path: '/commerce-and-bookings/commerce/waivers',
@@ -7058,7 +7065,7 @@ export const DOCS_SECTION_INDEX = [
7058
7065
  title: 'The contact record',
7059
7066
  heading: '',
7060
7067
  anchor: '',
7061
- text: 'The contact record\nEvery person in your CRM has a record: the email that identifies them, the profile your team keeps on them, where they came from, what they are filed under, and what the site recorded about them. You can add a person by hand, and edit every part of that profile from their own page.\nPlan availability The contact record is part of the CRM, included from Starter: reading a contact, adding one by hand, and every edit to one — their name, phone, job title and address, tags and notes, owner, lifecycle stage and company, custom fields, tasks, deals, files, logged calls and activities, one-to-one email and merging two records. On Free the Contacts section is shown locked, with the rest of the CRM. The people your sites capture are still kept, and workspace owners and admins can export them, or erase a person, from Settings → Privacy. See What each plan includes.'
7068
+ text: 'The contact record\nEvery person in your CRM has a record: the email that identifies them, the profile your team keeps on them, where they came from, what they are filed under, and what the site recorded about them. You can add a person by hand, and edit every part of that profile from their own page.\nPlan availability The contact record is part of the CRM, included from Starter: reading a contact, adding one by hand, and every edit to one — their name, phone, job title and address, tags and notes, owner, lifecycle stage and company, custom fields, tasks, deals, files, logged calls and activities, one-to-one email and merging two records. On Free the Contacts section is shown locked, with the rest of the CRM. The people your sites capture are still kept, and members holding Privacy requests, which workspace owners and admins hold by default, can export them, or erase a person, from Settings → Privacy. See What each plan includes.'
7062
7069
  },
7063
7070
  {
7064
7071
  path: '/content-and-data/crm/contact-record',
@@ -7114,7 +7121,7 @@ export const DOCS_SECTION_INDEX = [
7114
7121
  title: 'The contact record',
7115
7122
  heading: 'Lifecycle stages',
7116
7123
  anchor: '#lifecycle-stages',
7117
- text: 'The Stage says where a person is in your funnel. The list has a Stage column and a Stage filter; the record page lets you set it.\nEvery capture that reaches a contact sets the earliest stage that describes what happened, and never moves anyone back: a newsletter opt-in or a member sign-up makes a Subscriber, a paid booking or an order makes a Customer, and so does a deal marked won with the person on it. A converted lead arrives at Sales qualified. A form or a booking by somebody who is not yet a contact makes a lead, not a contact, so Lead is a stage you set by hand rather than one a capture sets; a customer who submits a form stays a customer. A contact you add by hand, import, or create over the API gets the stage you give it, or none, and a contact captured before this rule carries the stage its earlier captures imply.\n| Stage | Meaning |\n| Subscriber | Signed up to hear from you and nothing more yet. Set by a newsletter opt-in or a member sign-up. |\n| Lead | Showed interest — filled in a form, asked a question. Set by a form submission or a booking request. |\n| Marketing qualified | Engaged enough for marketing to hand over. |\n| Sales qualified | A real prospect somebody is working. |\n| Opportunity | There is a deal on the table. |\n| Customer | Has bought. A purchase on your site, or a deal with them marked won, sets this automatically for anyone at an earlier stage, and never moves anyone back. |\n| Evangelist | A customer who sends others your way. |\n| Other | A step of your own that none of the names fit. A sale never overwrites it. |\nWhere the person\'s lead is\nThe Relationship card shows Lead on this site when this site holds a lead for the address — the lead this contact was converted from, or one closed when the person signed up or bought. It opens the lead. A'
7124
+ text: 'The Stage says where a person is in your funnel. The list has a Stage column and a Stage filter; the record page lets you set it, with the Move contacts and deals between stages permission.\nEvery capture that reaches a contact sets the earliest stage that describes what happened, and never moves anyone back: a newsletter opt-in or a member sign-up makes a Subscriber, a paid booking or an order makes a Customer, and so does a deal marked won with the person on it. A converted lead arrives at Sales qualified. A form or a booking by somebody who is not yet a contact makes a lead, not a contact, so Lead is a stage you set by hand rather than one a capture sets; a customer who submits a form stays a customer. A contact you add by hand, import, or create over the API gets the stage you give it, or none, and a contact captured before this rule carries the stage its earlier captures imply.\n| Stage | Meaning |\n| Subscriber | Signed up to hear from you and nothing more yet. Set by a newsletter opt-in or a member sign-up. |\n| Lead | Showed interest — filled in a form, asked a question. Set by a form submission or a booking request. |\n| Marketing qualified | Engaged enough for marketing to hand over. |\n| Sales qualified | A real prospect somebody is working. |\n| Opportunity | There is a deal on the table. |\n| Customer | Has bought. A purchase on your site, or a deal with them marked won, sets this automatically for anyone at an earlier stage, and never moves anyone back. |\n| Evangelist | A customer who sends others your way. |\n| Other | A step of your own that none of the names fit. A sale never overwrites it. |\nWhere the person\'s lead is\nThe Relationship card shows Lead on this site when this site holds a lead for the address — the lead this contact was converted from, or one clos'
7118
7125
  },
7119
7126
  {
7120
7127
  path: '/content-and-data/crm/contact-record',
@@ -7275,7 +7282,7 @@ export const DOCS_SECTION_INDEX = [
7275
7282
  title: 'Deals pipeline',
7276
7283
  heading: 'Moving, winning and losing',
7277
7284
  anchor: '#moving-winning-and-losing',
7278
- text: 'Stage changes go through the server rather than being written directly, so that automations can hear them. Three events fire, and each can trigger a workflow or action — see Automations for the CRM:\n| Event | When |\n| dealStageChanged | A deal moves between open stages, or is reopened. |\n| dealWon | A deal is marked won. |\n| dealLost | A deal is marked lost. Marking a deal lost asks for a reason, which is kept on the deal. |\nEvery move also gives the deal the new stage\'s forecast category and clears its own probability, so it forecasts at the new stage\'s odds — as Salesforce re-defaults a probability when the stage changes. Edit the deal afterwards to set either again.\nEvery event carries the deal\'s id, title, amount and currency, its new and previous stage, and the owner, contact and company ids, so a workflow can notify the owner, file a task, or act on the person.\nA won deal makes its contact a customer {#a-won-deal-makes-its-contact-a-customer}\nMarking a deal won sets the linked contact\'s lifecycle stage to Customer — the same rule an order applies: a person with no stage or an earlier one becomes a customer, and nobody is ever moved back, so an Evangelist who closes another deal stays an evangelist and a stage of Other is never overwritten. It happens on the move into the won stage itself, whichever way the deal got there — the board, a card\'s menu, the deal\'s page, the bulk bar, the organization-level board, or the REST API — and there is nothing to switch on: a won deal is a customer by definition. The stage is written for the site the deal was made on, so a sibling site that also knows the person keeps its own reading of them.\nWhen the stage did move, a Contact changed stage event follows the Deal won event, so an automation that starts when somebody becomes a c'
7285
+ text: 'Moving, winning, losing and reopening a deal take the Move contacts and deals between stages permission as well as Manage data. Without it, these controls stay in view, switched off.\nStage changes go through the server rather than being written directly, so that automations can hear them. Three events fire, and each can trigger a workflow or action — see Automations for the CRM:\n| Event | When |\n| dealStageChanged | A deal moves between open stages, or is reopened. |\n| dealWon | A deal is marked won. |\n| dealLost | A deal is marked lost. Marking a deal lost asks for a reason, which is kept on the deal. |\nEvery move also gives the deal the new stage\'s forecast category and clears its own probability, so it forecasts at the new stage\'s odds — as Salesforce re-defaults a probability when the stage changes. Edit the deal afterwards to set either again.\nEvery event carries the deal\'s id, title, amount and currency, its new and previous stage, and the owner, contact and company ids, so a workflow can notify the owner, file a task, or act on the person.\nA won deal makes its contact a customer {#a-won-deal-makes-its-contact-a-customer}\nMarking a deal won sets the linked contact\'s lifecycle stage to Customer — the same rule an order applies: a person with no stage or an earlier one becomes a customer, and nobody is ever moved back, so an Evangelist who closes another deal stays an evangelist and a stage of Other is never overwritten. It happens on the move into the won stage itself, whichever way the deal got there — the board, a card\'s menu, the deal\'s page, the bulk bar, the organization-level board, or the REST API — and there is nothing to switch on: a won deal is a customer by definition. The stage is written for the site the deal was made on, so a sibling site that also kn'
7279
7286
  },
7280
7287
  {
7281
7288
  path: '/content-and-data/crm/deals',
@@ -7471,7 +7478,7 @@ export const DOCS_SECTION_INDEX = [
7471
7478
  title: 'Leads',
7472
7479
  heading: '',
7473
7480
  anchor: '',
7474
- text: 'Leads\nA lead is somebody you have heard of but not yet qualified: a visitor who booked or wrote in through a form that routes leads, a person from a list you imported, or one you added by hand. It is a record of its own — the way it is in Salesforce — and it becomes a contact only when you convert it. The Leads section of the CRM is where the team works them — decides who owns each one, keeps notes, and either converts the lead into a contact or closes it with a reason.\nLeads live under the site that captured them, so each site\'s list is its own. Open CRM → Leads in the console, or open one lead from the Inbox: its Site Members & Leads section shows members or leads, one at a time, by the Members | Leads toggle above the table. Choose Leads, and a row\'s menu (⋮) has Open in CRM. Each side is its own list with its own filters and search, so a person who left their address and later signed up appears under both. On the organization\'s Inbox the section is Leads alone, every site\'s. See Filter the Inbox tables.\nPlan availability Leads are part of the CRM, included from Starter. On Free the section is shown locked, with the rest of the CRM. Leads are still filed on Free, exactly as described below, and kept; workspace owners and admins can export every lead, or erase a person, from Settings → Privacy. See What each plan includes.'
7481
+ text: 'Leads\nA lead is somebody you have heard of but not yet qualified: a visitor who booked or wrote in through a form that routes leads, a person from a list you imported, or one you added by hand. It is a record of its own — the way it is in Salesforce — and it becomes a contact only when you convert it. The Leads section of the CRM is where the team works them — decides who owns each one, keeps notes, and either converts the lead into a contact or closes it with a reason.\nLeads live under the site that captured them, so each site\'s list is its own. Open CRM → Leads in the console, or open one lead from the Inbox: its Site Members & Leads section shows members or leads, one at a time, by the Members | Leads toggle above the table. Choose Leads, and a row\'s menu (⋮) has Open in CRM. Each side is its own list with its own filters and search, so a person who left their address and later signed up appears under both. On the organization\'s Inbox the section is Leads alone, every site\'s. See Filter the Inbox tables.\nPlan availability Leads are part of the CRM, included from Starter. On Free the section is shown locked, with the rest of the CRM. Leads are still filed on Free, exactly as described below, and kept; members holding Privacy requests, which workspace owners and admins hold by default, can export every lead, or erase a person, from Settings → Privacy. See What each plan includes.'
7475
7482
  },
7476
7483
  {
7477
7484
  path: '/content-and-data/crm/leads',
@@ -7520,7 +7527,7 @@ export const DOCS_SECTION_INDEX = [
7520
7527
  title: 'Leads',
7521
7528
  heading: 'Erasing the person',
7522
7529
  anchor: '#erasing-the-person',
7523
- text: 'The menu (⋮) in the header of the lead\'s page also carries Erase this person — the privacy erasure, for a person who asks to be forgotten. It is the same request the contact record offers, filed by the lead\'s address: the person is removed from every site in the workspace, the address is closed to capture at once, the lead shows an Erasure pending banner with its Convert button disabled, and the sweep runs with the nightly erasure job. Workspace admins only. What it removes, what it keeps and what it does not reach are listed in Deleting and erasing.'
7530
+ text: 'The menu (⋮) in the header of the lead\'s page also carries Erase this person — the privacy erasure, for a person who asks to be forgotten. It is the same request the contact record offers, filed by the lead\'s address: the person is removed from every site in the workspace, the address is closed to capture at once, the lead shows an Erasure pending banner with its Convert button disabled, and the sweep runs with the nightly erasure job. It takes the Privacy requests permission, which workspace owners and admins hold by default. What it removes, what it keeps and what it does not reach are listed in Deleting and erasing.'
7524
7531
  },
7525
7532
  {
7526
7533
  path: '/content-and-data/crm/leads',
@@ -7611,7 +7618,7 @@ export const DOCS_SECTION_INDEX = [
7611
7618
  title: 'CRM',
7612
7619
  heading: 'Who can open the CRM',
7613
7620
  anchor: '#who-can-open-the-crm',
7614
- text: 'Opening the CRM takes the workspace\'s manage data permission — owners, admins and editors by default, or a custom role granting it. What a reader then sees follows the site they have open: a record captured on one site is visible to that site, to every site declared to be one sender with it, or to the whole organization when the organization has chosen to share its data. A collaborator scoped to one site sees that site\'s people, deals and tasks and no others. The rule is the same in every section, so no section can show a record the reader could not open as a contact.\nOne sender, one CRM {#one-sender-one-crm}\nSites your organization has declared one sender share one CRM: a person they have both met is one record, with one owner, one stage, one timeline and one set of notes, and everyone who works on any of those sites sees it. A collaborator who can open only some of a group\'s sites keeps seeing only the people those sites met.\nWhen a group changes, the records move with it — combined when sites join, copied when a site leaves, with order totals following the site that clearly earned them. The contact record says exactly how, and the review before any change counts how many people it affects.'
7621
+ text: 'Opening the CRM takes the workspace\'s manage data permission — owners, admins and editors by default, or a custom role granting it. What a reader then sees follows the site they have open: a record captured on one site is visible to that site, to every site declared to be one sender with it, or to the whole organization when the organization has chosen to share its data. A collaborator scoped to one site sees that site\'s people, deals and tasks and no others. The rule is the same in every section, so no section can show a record the reader could not open as a contact.\nChanging a record takes the same manage data permission. Moving a contact or a deal between stages also takes Move contacts and deals between stages, which starts from the reader\'s role on the site: its admins and editors by default.\nOne sender, one CRM {#one-sender-one-crm}\nSites your organization has declared one sender share one CRM: a person they have both met is one record, with one owner, one stage, one timeline and one set of notes, and everyone who works on any of those sites sees it. A collaborator who can open only some of a group\'s sites keeps seeing only the people those sites met.\nWhen a group changes, the records move with it — combined when sites join, copied when a site leaves, with order totals following the site that clearly earned them. The contact record says exactly how, and the review before any change counts how many people it affects.'
7615
7622
  },
7616
7623
  {
7617
7624
  path: '/content-and-data/crm/overview',
@@ -7793,7 +7800,7 @@ export const DOCS_SECTION_INDEX = [
7793
7800
  title: 'Sequences',
7794
7801
  heading: 'Sequences',
7795
7802
  anchor: '#sequences',
7796
- text: 'A sequence is the emails, and the tasks between them, one person gets from one rep. Sequences → All sequences lists each one with its mailbox, its status, and how many people it has enrolled, and how many of them are still active, replied, bounced or opted out.\nThe list is newest first, a page at a time. The table\'s toolbar filters it. Filters narrows it by Status or Mailbox (pick one or several), by Name (a word in it, or the whole name), or by the day it was Created (on, before or after a date). Search finds a sequence by the start of any word of its name. Every filter and the search are answered by the database across all your sequences, not only the page on screen, and each filter in force shows as a chip above the table; remove a chip to drop its filter. The Filters panel edits one filter at a time, and filters on different columns add up. A combination the database cannot answer at once — a name word together with a search, for example — is named above the table rather than applied to some rows. See Filter and search a list.\nBuild a sequence {#build-a-sequence}\nSelect New sequence, name it, and choose the site whose CRM the people you enroll are contacts of and the mailbox it sends from. A sequence sends as the member who connected its mailbox, so only that member, or an organization owner or admin, can edit or activate it.\nThe Mailbox list offers the mailboxes you connected, and an owner or admin every mailbox in the organization. A disconnected mailbox is never offered. When exactly one of your own mailboxes is active, a new sequence starts on it. With none, connect one first.\nAlso send from adds more mailboxes the sequence sends from in rotation — several inboxes set up for outreach, for example, each sending its own daily cap. Each person you enroll is given o'
7803
+ text: 'A sequence is the emails, and the tasks between them, one person gets from one rep. Sequences → All sequences lists each one with its mailbox, its status, and how many people it has enrolled, and how many of them are still active, replied, bounced or opted out.\nThe list is newest first, a page at a time. The table\'s toolbar filters it. Filters narrows it by Status or Mailbox (pick one or several), by Name (a word in it, or the whole name), or by the day it was Created (on, before or after a date). Search finds a sequence by the start of any word of its name. Every filter and the search are answered by the database across all your sequences, not only the page on screen, and each filter in force shows as a chip above the table; remove a chip to drop its filter. The Filters panel edits one filter at a time, and filters on different columns add up. A combination the database cannot answer at once — a name word together with a search, for example — is named above the table rather than applied to some rows. See Filter and search a list.\nBuild a sequence {#build-a-sequence}\nSelect New sequence, name it, and choose the site whose CRM the people you enroll are contacts of and the mailbox it sends from. A sequence sends as the member who connected its mailbox, so only that member, or a member holding Manage everyone\'s Sequences, can edit or activate it.\nThe Mailbox list offers the mailboxes you connected, and a member holding that permission every mailbox in the organization. A disconnected mailbox is never offered. When exactly one of your own mailboxes is active, a new sequence starts on it. With none, connect one first.\nAlso send from adds more mailboxes the sequence sends from in rotation — several inboxes set up for outreach, for example, each sending its own daily cap. Each'
7797
7804
  },
7798
7805
  {
7799
7806
  path: '/content-and-data/crm/sequences',
@@ -7863,7 +7870,7 @@ export const DOCS_SECTION_INDEX = [
7863
7870
  title: 'CRM settings',
7864
7871
  heading: '',
7865
7872
  anchor: '',
7866
- text: 'CRM settings\nCRM → Settings holds what the CRM does on its own, for every site in your workspace. A setting here is a fact about how your business files people, not about one site, so it is stored on the workspace and applies wherever a contact is captured. The section lives in the CRM hub at …/hosts/{site}/crm/settings, last in the rail, and at the organization level at …/{organization}/crm/settings, where it also holds the Recipes card.\nOnly a workspace owner or admin can change a setting. Everyone who can open the CRM can read the page; a member who cannot change a switch sees it disabled, with a note saying why. Two cards are exceptions: the Email templates card, which every CRM editor may write to, because a template is working material, not policy; and Your sending addresses, which is each member\'s own list.'
7873
+ text: 'CRM settings\nCRM → Settings holds what the CRM does on its own, for every site in your workspace. A setting here is a fact about how your business files people, not about one site, so it is stored on the workspace and applies wherever a contact is captured. The section lives in the CRM hub at …/hosts/{site}/crm/settings, last in the rail, and at the organization level at …/{organization}/crm/settings, where it also holds the Recipes card.\nChanging a setting takes the Change CRM settings permission, which owners and admins hold by default. Everyone who can open the CRM can read the page; a member who cannot change a switch sees it disabled, with a note naming the permission. Two cards are exceptions: the Email templates card, which every CRM editor may write to, because a template is working material, not policy; and Your sending addresses, which is each member\'s own list.'
7867
7874
  },
7868
7875
  {
7869
7876
  path: '/content-and-data/crm/settings',
@@ -7905,7 +7912,7 @@ export const DOCS_SECTION_INDEX = [
7905
7912
  title: 'CRM settings',
7906
7913
  heading: 'Email capture',
7907
7914
  anchor: '#email-capture',
7908
- text: 'The Email capture card holds the workspace\'s one capture address, with Copy and Rotate address. The address looks like crm+…@in.aglyn.com. A message forwarded to it, or sent with it in BCC, is filed on the timeline of the contact or lead it was with, so a reply that reached your own mailbox lands on the record too. How a message is matched, what is kept and what is dropped is described under Captured email.\nThe address is the workspace\'s, not a site\'s: the card reads the same under every site and at the organization level, and the record\'s own site decides which timeline the message lands on. It is minted the first time somebody opens the card or the Send email dialog, and everybody who can open the CRM can copy it.\nRotate address replaces it, behind a confirmation, and only a workspace owner or admin may. The moment the new address is written the old one goes quiet: mail sent to it afterwards is dropped without a trace, so a mailbox rule or a saved shortcut that carried the old address has to be updated. Rotate when the address has leaked outside the team — anybody who holds it can file mail on your records, though only mail from or to somebody already in the CRM is ever filed.'
7915
+ text: 'The Email capture card holds the workspace\'s one capture address, with Copy and Rotate address. The address looks like crm+…@in.aglyn.com. A message forwarded to it, or sent with it in BCC, is filed on the timeline of the contact or lead it was with, so a reply that reached your own mailbox lands on the record too. How a message is matched, what is kept and what is dropped is described under Captured email.\nThe address is the workspace\'s, not a site\'s: the card reads the same under every site and at the organization level, and the record\'s own site decides which timeline the message lands on. It is minted the first time somebody opens the card or the Send email dialog, and everybody who can open the CRM can copy it.\nRotate address replaces it, behind a confirmation, and takes the Change CRM settings permission. The moment the new address is written the old one goes quiet: mail sent to it afterwards is dropped without a trace, so a mailbox rule or a saved shortcut that carried the old address has to be updated. Rotate when the address has leaked outside the team — anybody who holds it can file mail on your records, though only mail from or to somebody already in the CRM is ever filed.'
7909
7916
  },
7910
7917
  {
7911
7918
  path: '/content-and-data/crm/settings',
@@ -7933,14 +7940,14 @@ export const DOCS_SECTION_INDEX = [
7933
7940
  title: 'Share records across sites',
7934
7941
  heading: '',
7935
7942
  anchor: '',
7936
- text: 'Share records across sites\nA record in your CRM belongs to the whole workspace: every site sees the contacts, companies, deals and tasks, whichever site they came in on. The site a record came from is kept as its source, so you can still tell which brand met the person.\nAn agency that keeps each client\'s records apart can change that. A workspace owner or admin sets Default sharing for new records in the CRM\'s Settings to Only the site they came in on. Each site then sees the people it captured, a site in a consent group also sees the records of the group\'s other sites, and every other record is hidden from it, so one client\'s collaborator never sees another client\'s people. The setting covers new contacts, companies, deals and tasks, and changes nothing that already exists. It is separate from the defaults for new datasets and media files, which are set on the organization Data and Media pages.\nThe rest of this page is for a workspace that keeps its sites apart.\nWhen you run several brands and want one brand\'s team to work records another brand captured, a workspace owner or admin can share them. You can share a lead, a contact, a company or a deal:\n- By hand: one record from its page, or a selection from the Leads or Contacts list.\n- By a sharing rule: every record the rule matches, including the ones you already have and every one captured or changed later.\nYou can share with chosen sites or with All sites. All sites includes sites you add to the workspace later.'
7943
+ text: 'Share records across sites\nA record in your CRM belongs to the whole workspace: every site sees the contacts, companies, deals and tasks, whichever site they came in on. The site a record came from is kept as its source, so you can still tell which brand met the person.\nAn agency that keeps each client\'s records apart can change that. A member holding Change CRM settings (owners and admins by default) sets Default sharing for new records in the CRM\'s Settings to Only the site they came in on. Each site then sees the people it captured, a site in a consent group also sees the records of the group\'s other sites, and every other record is hidden from it, so one client\'s collaborator never sees another client\'s people. The setting covers new contacts, companies, deals and tasks, and changes nothing that already exists. It is separate from the defaults for new datasets and media files, which are set on the organization Data and Media pages.\nThe rest of this page is for a workspace that keeps its sites apart.\nWhen you run several brands and want one brand\'s team to work records another brand captured, a member holding Change CRM settings can share them. You can share a lead, a contact, a company or a deal:\n- By hand: one record from its page, or a selection from the Leads or Contacts list.\n- By a sharing rule: every record the rule matches, including the ones you already have and every one captured or changed later.\nYou can share with chosen sites or with All sites. All sites includes sites you add to the workspace later.'
7937
7944
  },
7938
7945
  {
7939
7946
  path: '/content-and-data/crm/sharing',
7940
7947
  title: 'Share records across sites',
7941
7948
  heading: 'What a shared record looks like',
7942
7949
  anchor: '#what-a-shared-record-looks-like',
7943
- text: 'On the site you shared it with, the record appears on the site\'s own CRM lists with a Shared by chip. The chip names the person who shared it, or the rule that did.\nThe Sharing card {#sharing-card}\nThe Sharing card on a lead\'s, contact\'s, company\'s or deal\'s page lists every site that can see the record and why; an owner or admin shares it with more sites from Share with sites… in the card\'s header. The card shows once the record is shared, and to an owner or admin before then:\n- Held by: the sites that captured the record. Their visibility comes from the record itself, and sharing never removes it.\n- Shared by hand: the site, who shared it and when. An owner or admin can stop sharing it in one click.\n- Shared by a rule: the rule\'s name. To stop it, edit or delete the rule in Settings.\nUnsharing removes only the visibility that the share added. If the site also holds the record (it captured the person itself), it keeps seeing it.'
7950
+ text: 'On the site you shared it with, the record appears on the site\'s own CRM lists with a Shared by chip. The chip names the person who shared it, or the rule that did.\nThe Sharing card {#sharing-card}\nThe Sharing card on a lead\'s, contact\'s, company\'s or deal\'s page lists every site that can see the record and why; a member holding Change CRM settings shares it with more sites from Share with sites… in the card\'s header. For anyone else that button is switched off, with the permission named:\n- Held by: the sites that captured the record. Their visibility comes from the record itself, and sharing never removes it.\n- Shared by hand: the site, who shared it and when. A member holding Change CRM settings can stop sharing it in one click.\n- Shared by a rule: the rule\'s name. To stop it, edit or delete the rule in Settings.\nUnsharing removes only the visibility that the share added. If the site also holds the record (it captured the person itself), it keeps seeing it.'
7944
7951
  },
7945
7952
  {
7946
7953
  path: '/content-and-data/crm/sharing',
@@ -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',
@@ -8115,7 +8122,7 @@ export const DOCS_SECTION_INDEX = [
8115
8122
  title: 'Saved views',
8116
8123
  heading: 'Segments and views',
8117
8124
  anchor: '#segments-and-views',
8118
- text: 'A segment is the older, narrower thing: saved tags and sources, usable as a campaign audience. Views keep everything a segment kept and more, and the two meet in two places:\n- Every segment is offered in the Contacts views menu. Choosing one puts its tags and sources among the list\'s filters, where you can narrow further and save the result as a view.\n- Save as segment… in the views menu keeps the tag and source filters of the current view as a segment. The other filters stay on the view.\nA contacts view can also be an email audience in its own right. When you build an audience from a rule, pick it under Saved view, beside Saved segment: the view\'s filters — owner, stage, company, tags, sources, dates, purchases and custom fields — always apply, the way a segment\'s do. Only views whose filters can be an audience are offered: a view filtered by a name or an email, or by the updated date, describes a list on a screen rather than a set of people, and is left out. A view that is deleted, or edited past what an audience can express after a rule named it, makes that audience select nobody rather than everybody.'
8125
+ text: 'A segment is the older, narrower thing: saved tags and sources, usable as a campaign audience. Views keep everything a segment kept and more, and the two meet in two places:\n- Every segment is offered in the Contacts views menu. Choosing one puts its tags and sources among the list\'s filters, where you can narrow further and save the result as a view.\n- Save as segment… in the views menu keeps the tag and source filters of the current view as a segment. The other filters stay on the view.\nA contacts view can also be an email audience in its own right. When you build an audience from a rule, pick it under Saved view, beside Saved segment: the view\'s filters — owner, stage, company, tags, sources, dates, purchases and custom fields — always apply, the way a segment\'s do. Only views whose filters can be an audience are offered: a view filtered by a name or an email, or by the updated date, describes a list on a screen rather than a set of people, and is left out. So is a view filtered by a source a plugin adds, such as Waiver signed; save that filter as a segment to send to those people. A view that is deleted, or edited past what an audience can express after a rule named it, makes that audience select nobody rather than everybody.'
8119
8126
  },
8120
8127
  {
8121
8128
  path: '/content-and-data/crm/views',
@@ -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',
@@ -8269,7 +8276,7 @@ export const DOCS_SECTION_INDEX = [
8269
8276
  title: 'Datasets & Dynamic Content',
8270
8277
  heading: 'Who a dataset is shared with',
8271
8278
  anchor: '#who-a-dataset-is-shared-with',
8272
- text: 'Datasets belong to the workspace, not to a single site, so one dataset can drive pages on every site you run. When that isn\'t what you want, the Sharing control on each dataset decides which sites can see it:\n- All sites — everyone in the workspace, on every site.\n- Selected sites… — pick the sites that share it, up to 30.\nWhere a new dataset starts depends on where you create it and on your workspace\'s Default sharing for new datasets, the setting at the top of the organization Data page (new media files have a default of their own, on the workspace Media page):\n- Created on a site\'s Data page — it follows that setting. Set to All sites, the dataset starts on All sites. Set to Only the site they were created in, it starts shared with that site alone, and its control reads Selected sites… with just that site picked.\n- Created on the organization Data page — it starts on All sites whatever the setting says, because there is no site to limit it to.\n- Installed from the Marketplace, or created through the REST API — it starts on All sites too. Both act for the whole organization, not for one site.\n- Made by Aglyn AI for a site — for example the lists a guided start builds, such as your packages or FAQs — it starts shared with that site alone, whatever the setting says, because it was made for that site. Share it with more sites from its Sharing control.\nDefault sharing for new datasets {#default-dataset-sharing}\nDefault sharing for new datasets, at the top of the organization Data page, decides what a dataset created on a site\'s Data page starts shared with: All sites, or only that site. Only workspace owners and admins can change it.\nThe setting only decides where a new dataset starts. It changes nothing that already exists, and you can widen or narrow any dataset afterwa'
8279
+ text: 'Datasets belong to the workspace, not to a single site, so one dataset can drive pages on every site you run. When that isn\'t what you want, the Sharing control on each dataset decides which sites can see it:\n- All sites — everyone in the workspace, on every site.\n- Selected sites… — pick the sites that share it, up to 30.\nWhere a new dataset starts depends on where you create it and on your workspace\'s Default sharing for new datasets, the setting at the top of the organization Data page (new media files have a default of their own, on the workspace Media page):\n- Created on a site\'s Data page — it follows that setting. Set to All sites, the dataset starts on All sites. Set to Only the site they were created in, it starts shared with that site alone, and its control reads Selected sites… with just that site picked.\n- Created on the organization Data page — it starts on All sites whatever the setting says, because there is no site to limit it to.\n- Installed from the Marketplace, or created through the REST API — it starts on All sites too. Both act for the whole organization, not for one site.\n- Made by Aglyn AI for a site — for example the lists a guided start builds, such as your packages or FAQs — it starts shared with that site alone, whatever the setting says, because it was made for that site. Share it with more sites from its Sharing control.\nDefault sharing for new datasets {#default-dataset-sharing}\nDefault sharing for new datasets, at the top of the organization Data page, decides what a dataset created on a site\'s Data page starts shared with: All sites, or only that site. Changing it takes the Organization settings permission, which workspace owners and admins hold by default; without it the control stays off.\nThe setting only decides where a new dataset st'
8273
8280
  },
8274
8281
  {
8275
8282
  path: '/content-and-data/datasets/overview',
@@ -8360,7 +8367,7 @@ export const DOCS_SECTION_INDEX = [
8360
8367
  title: 'Events Calendar',
8361
8368
  heading: 'Ask Aglyn AI',
8362
8369
  anchor: '#ask-aglyn-ai',
8363
- text: 'Aglyn AI can add events for you, such as add our autumn sourdough workshops, and a site started with AI for a business that holds events adds its first three. The events are listed on the page you name, or a page about them the request makes; if neither exists, an Events page at /events is added to your site\'s menu to list them. Each event gets a title, a start and end in your business\'s time zone, a place, an organizer and a description, and a stock photo as its cover, copied into your media library. A page section that shows them gets the Event List.\nEvents Aglyn AI adds are published, the same as Set published, when you have the admin or editor role on the site, so they show on your site straight away. With the author role they are saved as drafts, and the job says so. Edit, unpublish or delete them on the Events page like any other event. Adding events needs the Event Calendar add-on.'
8370
+ text: 'Aglyn AI can add events for you, such as add our autumn sourdough workshops, and a site started with AI for a business that holds events adds its first three. The events are listed on the page you name, or a page about them the request makes; if neither exists, an Events page at /events is added to your site\'s menu to list them. Each event gets a title, a start and end in your business\'s time zone, a place, an organizer and a description, and a stock photo as its cover, copied into your media library. A page section that shows them gets the Event List.\nEvents Aglyn AI adds are published, the same as Set published, when you hold the Publish site content permission on the site, which its admins and editors hold by default, so they show on your site straight away. Without it, as with the author role, they are saved as drafts, and the job says so. Edit, unpublish or delete them on the Events page like any other event. Adding events needs the Event Calendar add-on.'
8364
8371
  },
8365
8372
  {
8366
8373
  path: '/content-and-data/events/overview',
@@ -8451,7 +8458,7 @@ export const DOCS_SECTION_INDEX = [
8451
8458
  title: 'Forms & Lead Capture',
8452
8459
  heading: 'Switch Forms off for one site',
8453
8460
  anchor: '#switch-forms-off-for-one-site',
8454
- text: 'Forms is on for every site in a workspace. A site admin can switch it off for one site on that site\'s Admin → Plugins → Forms page. The switch asks first: it lists the published pages on the site that carry a form, because those forms stop rendering and stop accepting submissions the moment Forms is off.\nWith Forms off for a site:\n- a form on its published pages is not drawn. The rest of the page stays; where the form was, there is empty space and no error;\n- every submission sent to the site is refused with This site is not accepting form submissions, including one from a page a visitor opened before the switch;\n- publishing a form, or a page, layout or component that carries one, is refused until Forms is back on for the site. Remove the form to publish the rest of the page;\n- the Forms page leaves the site\'s navigation.\nWhat it keeps: the submissions already received, the workspace\'s form catalog and the CRM leads its forms created are untouched, and forms keep working on the workspace\'s other sites. A Marketing popup that collects an email address is a Marketing element rather than a form, so it keeps collecting while Marketing is on for the site.\nSwitch Forms back on and the forms on the site\'s published pages render and accept submissions again.'
8461
+ text: 'Forms is on for every site in a workspace. A member holding Manage site settings, which a site\'s admins hold by default, can switch it off for one site on that site\'s Admin → Plugins → Forms page. The switch asks first: it lists the published pages on the site that carry a form, because those forms stop rendering and stop accepting submissions the moment Forms is off.\nWith Forms off for a site:\n- a form on its published pages is not drawn. The rest of the page stays; where the form was, there is empty space and no error;\n- every submission sent to the site is refused with This site is not accepting form submissions, including one from a page a visitor opened before the switch;\n- publishing a form, or a page, layout or component that carries one, is refused until Forms is back on for the site. Remove the form to publish the rest of the page;\n- the Forms page leaves the site\'s navigation.\nWhat it keeps: the submissions already received, the workspace\'s form catalog and the CRM leads its forms created are untouched, and forms keep working on the workspace\'s other sites. A Marketing popup that collects an email address is a Marketing element rather than a form, so it keeps collecting while Marketing is on for the site.\nSwitch Forms back on and the forms on the site\'s published pages render and accept submissions again.'
8455
8462
  },
8456
8463
  {
8457
8464
  path: '/content-and-data/forms/overview',
@@ -8500,14 +8507,14 @@ export const DOCS_SECTION_INDEX = [
8500
8507
  title: 'Media Library & CDN',
8501
8508
  heading: 'Who an asset is shared with',
8502
8509
  anchor: '#who-an-asset-is-shared-with',
8503
- text: 'Workspace media is shared across every site by default. The Shared with control narrows that, with the same two choices as datasets — All sites or Selected sites…. You\'ll find it in three places:\n- on a single asset, in its details drawer;\n- on a selection — tick several files and use Shared with… in the toolbar;\n- on a folder, from its ⋮ menu, which offers to apply the same sharing to the files inside it and its subfolders (it names the count, so you know what you\'re about to change).\nA folder applies its sharing when you save it — files keep their own setting afterwards, so moving a file into a "Client A" folder later does not re-share it. Narrowing a file that sites are already using names those sites first and asks you to confirm. Only workspace owners and admins can change sharing.\nA new folder or file starts shared with All sites, so it appears everywhere the moment you create it — or with the site you were working in, if your workspace has been set to make new media site-scoped by default. That default is Default sharing for new media, at the top of the workspace\'s Media page, and it changes nothing that already exists. The site you were working in is the one whose Media tab you uploaded on, or the one you were editing when you opened the media picker. A folder or file created on the workspace Media page has no site to limit it to, so it starts on All sites either way. New datasets have a default of their own, Default sharing for new datasets on the organization Data page, so files can start on every site while datasets start on one, or the other way round. If the Shared with dialog ever opens on "Not shared with any site", that folder or file has no sharing stored at all: it is hidden from every site, and any file inside it turns up under No folder there. Pick a'
8510
+ text: 'Workspace media is shared across every site by default. The Shared with control narrows that, with the same two choices as datasets — All sites or Selected sites…. You\'ll find it in three places:\n- on a single asset, in its details drawer;\n- on a selection — tick several files and use Shared with… in the toolbar;\n- on a folder, from its ⋮ menu, which offers to apply the same sharing to the files inside it and its subfolders (it names the count, so you know what you\'re about to change).\nA folder applies its sharing when you save it — files keep their own setting afterwards, so moving a file into a "Client A" folder later does not re-share it. Narrowing a file that sites are already using names those sites first and asks you to confirm. Changing sharing takes the Edit the workspace media library permission, which workspace owners, admins and editors hold by default, and access to every site in the workspace: someone added to particular sites can\'t change it.\nA new folder or file starts shared with All sites, so it appears everywhere the moment you create it — or with the site you were working in, if your workspace has been set to make new media site-scoped by default. That default is Default sharing for new media, at the top of the workspace\'s Media page, and it changes nothing that already exists. The site you were working in is the one whose Media tab you uploaded on, or the one you were editing when you opened the media picker. A folder or file created on the workspace Media page has no site to limit it to, so it starts on All sites either way. New datasets have a default of their own, Default sharing for new datasets on the organization Data page, so files can start on every site while datasets start on one, or the other way round. If the Shared with dialog ever opens'
8504
8511
  },
8505
8512
  {
8506
8513
  path: '/content-and-data/media/overview',
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',
@@ -8801,7 +8808,7 @@ export const DOCS_SECTION_INDEX = [
8801
8808
  title: 'Build your first plugin',
8802
8809
  heading: '6. Install, enable, load',
8803
8810
  anchor: '#6-install-enable-load',
8804
- text: 'A workspace admin installs from the marketplace: the install pins your exact {version, sha256}, enables the plugin on the org switchboard, and it loads on the next visit — sandboxed by default, or into the app realm once staff have signed the version (trust: \'realm\'). Upgrades are explicit re-pins; your published artifacts are immutable, so nobody\'s pinned install can change underneath them.'
8811
+ text: 'A member holding Install plugins installs from the marketplace: the install pins your exact {version, sha256}, enables the plugin on the org switchboard, and it loads on the next visit — sandboxed by default, or into the app realm once staff have signed the version (trust: \'realm\'). Upgrades are explicit re-pins; your published artifacts are immutable, so nobody\'s pinned install can change underneath them.'
8805
8812
  },
8806
8813
  {
8807
8814
  path: '/developers/plugins/guides/first-plugin',
@@ -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',
@@ -9074,7 +9081,7 @@ export const DOCS_SECTION_INDEX = [
9074
9081
  title: 'Plugins & Marketplace',
9075
9082
  heading: 'How plugins run',
9076
9083
  anchor: '#how-plugins-run',
9077
- text: '- Each plugin loads into a sandboxed PluginFrame host runtime, isolated by origin.\n- A manifest + sandbox bridge protocol defines what a plugin can do.\n- A host-mediated network bridge lets plugins make network calls without direct access to your environment.\n- See Sandbox security model for what that isolation actually enforces — including the per-plugin network policy — if you\'re writing one.\n- Your workspace decides which plugins are enabled at all, and a site admin can narrow that further per site from the site\'s Admin → Plugins page. A plugin disabled for a site disappears from that site\'s navigation, editor, published pages, and API — other sites in the workspace are unaffected, and a site can never enable a plugin the workspace has switched off.\n- The site\'s Admin → Plugins page lists both kinds in two groups — what ships with the platform, and what the workspace installed from the marketplace — because which one a row is is the first thing you need to know before switching it. A marketplace plugin gets the same per-site switch as a built-in one.\n- Most plugins are on for a site unless it turns them off. User Accounts reads the other way: a site has it only once the site turns it on, because it is the one that decides whether the site serves /signin, /signup and /recover — and a sign-in page on a marketing site is worse than a missing one. A new site is created with it turned on; a site created before that has it off until it asks. See Member accounts for what the switch does.\n- AI has a site switch and no workspace switch. It is on for every workspace, because the AI add-on, credits, allotments and overage billing belong to the workspace rather than to any site. A site can switch AI off for itself on its Admin → Plugins page: that hides AI on the site, refuses e'
9084
+ text: '- Each plugin loads into a sandboxed PluginFrame host runtime, isolated by origin.\n- A manifest + sandbox bridge protocol defines what a plugin can do.\n- A host-mediated network bridge lets plugins make network calls without direct access to your environment.\n- See Sandbox security model for what that isolation actually enforces — including the per-plugin network policy — if you\'re writing one.\n- Your workspace decides which plugins are enabled at all, and a member holding Manage site settings can narrow that further per site from the site\'s Admin → Plugins page. A plugin disabled for a site disappears from that site\'s navigation, editor, published pages, and API — other sites in the workspace are unaffected, and a site can never enable a plugin the workspace has switched off.\n- The site\'s Admin → Plugins page lists both kinds in two groups — what ships with the platform, and what the workspace installed from the marketplace — because which one a row is is the first thing you need to know before switching it. A marketplace plugin gets the same per-site switch as a built-in one.\n- Most plugins are on for a site unless it turns them off. User Accounts reads the other way: a site has it only once the site turns it on, because it is the one that decides whether the site serves /signin, /signup and /recover — and a sign-in page on a marketing site is worse than a missing one. A new site is created with it turned on; a site created before that has it off until it asks. See Member accounts for what the switch does.\n- AI has a site switch and no workspace switch. It is on for every workspace, because the AI add-on, credits, allotments and overage billing belong to the workspace rather than to any site. A site can switch AI off for itself on its Admin → Plugins page: that hides '
9078
9085
  },
9079
9086
  {
9080
9087
  path: '/developers/plugins/overview',
@@ -9165,7 +9172,7 @@ export const DOCS_SECTION_INDEX = [
9165
9172
  title: 'Publisher handbook',
9166
9173
  heading: 'Before your first publish',
9167
9174
  anchor: '#before-your-first-publish',
9168
- text: '1. Publisher profile (Marketplace → Profile) — your handle and display name appear on every listing. Publishing is organization-owned: the listing belongs to your organization, not your personal account.\n2. Publisher agreement — every save in the marketplace asks you to tick I agree to the Marketplace Publisher Agreement above its button first. See The publisher agreement.\n3. Plan: publishing requires a Pro plan.\n4. Payouts (paid listings only): complete Stripe Connect onboarding from Marketplace → Payouts. The platform fee is 20% (30% on free plans).\nSet up your public profile {#public-profile}\nThe Public profile card on Marketplace → Profile is your publisher identity: set a handle, display name, bio and logo, then Save profile before you publish. They are shown on everything your organization publishes to the marketplace, and on your publisher page. The same card takes optional support contacts — a support email and URL — and links to your website, GitHub, X and LinkedIn, so buyers know where to ask for help.'
9175
+ text: '1. Publisher profile (Marketplace → Profile) — your handle and display name appear on every listing. Publishing is organization-owned: the listing belongs to your organization, not your personal account.\n2. Publisher agreement — every save in the marketplace asks you to tick I agree to the Marketplace Publisher Agreement above its button first. See The publisher agreement.\n3. Plan: publishing requires a Pro plan.\n4. Payouts (paid listings only): complete Stripe Connect onboarding from Marketplace → Payouts. The platform fee is 20% (30% on free plans).\nSet up your public profile {#public-profile}\nThe Public profile card on Marketplace → Profile is your publisher identity: set a handle, display name, bio and logo, then Save profile before you publish. They are shown on everything your organization publishes to the marketplace, and on your publisher page. The same card takes optional support contacts — a support email and URL — and links to your website, GitHub, X and LinkedIn, so buyers know where to ask for help.\nSaving the profile needs the Edit the publisher profile permission, which the workspace\'s owners and admins hold by default. Without it, Save profile stays off and the card names the permission to ask an organization admin for. See Marketplace publisher permissions.'
9169
9176
  },
9170
9177
  {
9171
9178
  path: '/developers/plugins/publishing/publisher-handbook',
@@ -9207,7 +9214,7 @@ export const DOCS_SECTION_INDEX = [
9207
9214
  title: 'Publisher handbook',
9208
9215
  heading: 'Authoring your listing',
9209
9216
  anchor: '#authoring-your-listing',
9210
- text: 'Your listing IS your storefront — it renders on the detail page every buyer sees. Editable at publish time or any time after, no republish needed: open Edit listing on your own listing\'s detail page (the whole page becomes the editor), or use the Edit action on Marketplace → Listings.\n| Field | Guidance |\n| Name | The display name on every browse card and at the top of the detail page; ≤80 chars. A typo here is fixable without republishing — leaving it blank keeps the current name rather than clearing it. |\n| Description | The one-line summary under the name on browse cards; ≤500 chars. |\n| Body (About) | The main docs: what it does, setup, what it adds, data & permissions. Rich-text editor with headings, bold/italic, links, and inline images; ≤20k chars. |\n| Preview image | The hero shown on browse cards and at the top of the detail page — pick it from your media library. |\n| Logo | Square; pick from the media library or paste an https URL. |\n| Screenshots | Up to 6, from the media library or https URLs; the detail page shows a gallery with click-to-zoom. |\n| Categories | Up to 3 from the fixed taxonomy. |\n| License | Short label (e.g. MIT) — listings without one get flagged in review. |\n| Homepage / repository | Public links build trust; reviewers check them. The repository is asked for at publish and required — editing it here changes the listing, not what past versions declared. |\nEdit a listing {#edit-listing}\nSelect Edit listing on your own listing\'s detail page and the page becomes the editor for what buyers see: name, summary, rich-text body and media. Tick the publisher agreement box above Save listing and save, and the listing changes at once — no new version, and no new review, because review is about the bundle\'s bytes rather than the words around them.\nYour'
9217
+ text: 'Your listing IS your storefront — it renders on the detail page every buyer sees. Editable at publish time or any time after, no republish needed: open Edit listing on your own listing\'s detail page (the whole page becomes the editor), or use the Edit action on Marketplace → Listings.\n| Field | Guidance |\n| Name | The display name on every browse card and at the top of the detail page; ≤80 chars. A typo here is fixable without republishing — leaving it blank keeps the current name rather than clearing it. |\n| Description | The one-line summary under the name on browse cards; ≤500 chars. |\n| Body (About) | The main docs: what it does, setup, what it adds, data & permissions. Rich-text editor with headings, bold/italic, links, and inline images; ≤20k chars. |\n| Preview image | The hero shown on browse cards and at the top of the detail page — pick it from your media library. |\n| Logo | Square; pick from the media library or paste an https URL. |\n| Screenshots | Up to 6, from the media library or https URLs; the detail page shows a gallery with click-to-zoom. |\n| Categories | Up to 3 from the fixed taxonomy. |\n| License | Short label (e.g. MIT) — listings without one get flagged in review. |\n| Homepage / repository | Public links build trust; reviewers check them. The repository is asked for at publish and required — editing it here changes the listing, not what past versions declared. |\nEdit a listing {#edit-listing}\nSelect Edit listing on your own listing\'s detail page and the page becomes the editor for what buyers see: name, summary, rich-text body and media. Tick the publisher agreement box above Save listing and save, and the listing changes at once — no new version, and no new review, because review is about the bundle\'s bytes rather than the words around them.\nEdit'
9211
9218
  },
9212
9219
  {
9213
9220
  path: '/developers/plugins/publishing/publisher-handbook',
@@ -9228,14 +9235,14 @@ export const DOCS_SECTION_INDEX = [
9228
9235
  title: 'Publisher handbook',
9229
9236
  heading: 'How installs work (the buyer side)',
9230
9237
  anchor: '#how-installs-work-the-buyer-side',
9231
- text: 'Browse is a catalog — cards link to the detail page, which is the only place an install happens. The buyer picks targets (all sites, selected sites, or org-wide for plugins), confirms a dialog that names exactly where the install lands, and the pin is written: your exact {version, sha256} pinned to the site or org, the plugin enabled for the workspace, loaded on their next visit. Buyers can uninstall from the listing\'s own detail page (Uninstall, or Uninstall org-wide for an org-scope pin) as well as from Marketplace → Installed — removing the pin and disabling it. Data your plugin created stays, so reinstalls resume cleanly. Paid listings require purchase before install; you see sales in your publisher ledger.\nThe detail page shows two install figures side by side: installs is the cumulative all-time total and only ever grows, while active counts the organizations and sites that currently hold a pin — it goes down when someone uninstalls. A big gap between the two is churn worth investigating.\nThe Install card {#install-card}\nThe Install card on a listing\'s detail page is where an install happens: choose where it lands — all sites, selected sites, or the whole organization for a plugin — then confirm. A paid listing asks for the purchase first, paid on that card with the workspace\'s card on file, and the same card offers Uninstall (or Uninstall org-wide) once it is installed.\nInstalled from the marketplace {#installed-from-the-marketplace}\nInstalled from the marketplace, on the workspace\'s Plugins page, lists every marketplace item this workspace has installed — org-wide, or the sites it is on — with the version it is pinned to and whether an update is out. Open one to manage that installation; browse the marketplace to add one.\nLicenses {#licenses}\nA purchase licenses'
9238
+ text: 'Browse is a catalog — cards link to the detail page, which is the only place an install happens. The buyer picks targets (all sites, selected sites, or org-wide for plugins), confirms a dialog that names exactly where the install lands, and the pin is written: your exact {version, sha256} pinned to the site or org, the plugin enabled for the workspace, loaded on their next visit. Buyers can uninstall from the listing\'s own detail page (Uninstall, or Uninstall org-wide for an org-scope pin) as well as from Marketplace → Installed — removing the pin and disabling it. Data your plugin created stays, so reinstalls resume cleanly. Paid listings require purchase before install; you see sales in your publisher ledger.\nThe detail page shows two install figures side by side: installs is the cumulative all-time total and only ever grows, while active counts the organizations and sites that currently hold a pin — it goes down when someone uninstalls. A big gap between the two is churn worth investigating.\nYour own listings {#your-own-listings}\nEveryone in the workspace that publishes a listing installs it free on that workspace\'s own sites, whatever the listing is: a plugin, component, theme, site template, layout, dataset schema, email template or email starter. A site starter works the same way: a new site in your workspace starts from it free. That includes a private listing, and for plugins and site starters a version still in review, so you can try your work before anyone else can.\nFree covers your own sites only. Installing your listing on a site in another workspace, a client\'s for example, works as it does for any buyer: that workspace needs a license for it, and a paid listing asks for the purchase first. Nobody in the publishing workspace can buy its own listings, for an'
9232
9239
  },
9233
9240
  {
9234
9241
  path: '/developers/plugins/publishing/publisher-handbook',
9235
9242
  title: 'Publisher handbook',
9236
9243
  heading: 'Getting paid',
9237
9244
  anchor: '#getting-paid',
9238
- text: 'One-time prices in whole USD: $0 (free), or $3 to $1000. Purchases flow through the platform\'s Stripe; your share (80%, or 70% on free plans) pays out via your Connect account. The Marketplace → Sales tab tracks every sale.\nYour share is calculated on the pre-tax price. Buyers also pay sales tax on top of it, which Aglyn collects and remits under its marketplace-provider registration — that money is never yours and is not part of your payout. The Sales tab reports net paid out, the amount that reached your Stripe account, with what buyers paid, the tax and the platform fee shown beside it.\nRefunds and lost chargebacks are excluded from that total: your share is pulled back from your Connect account, and the amount returned is listed separately.\nSet up payouts {#set-up-payouts}\nThe Payouts card on Marketplace → Payouts connects your organization\'s Stripe account so paid listings can pay you: select Set up payouts and finish Stripe\'s onboarding. The card then says where you stand — payouts enabled, setup still to finish in Stripe, or an account to reconnect — and links to your payouts in Stripe. The platform fee is 20% per sale, 30% on the Free plan.\nPurchases and the platform fee {#purchases-and-fees}\nEvery paid purchase records what the buyer paid and the platform fee taken from it, and Aglyn staff see recent purchases on their marketplace overview with the fee from each sale. Your share is what is left once that fee is taken, before sales tax.\nWhen a refund cannot be pulled back {#refund-reversals}\nWhen a sale is refunded, your share is pulled back from your Connect account; if Stripe refuses that reversal, you keep the share and the platform absorbs the refund until it is recovered. Aglyn staff track each one, with the amount owed, until it is.\nThe $3 minimum on paid '
9245
+ text: 'One-time prices in whole USD: $0 (free), or $3 to $1000. Purchases flow through the platform\'s Stripe; your share (80%, or 70% on free plans) pays out via your Connect account. The Marketplace → Sales tab tracks every sale.\nYour share is calculated on the pre-tax price. Buyers also pay sales tax on top of it, which Aglyn collects and remits under its marketplace-provider registration — that money is never yours and is not part of your payout. The Sales tab reports net paid out, the amount that reached your Stripe account, with what buyers paid, the tax and the platform fee shown beside it.\nRefunds and lost chargebacks are excluded from that total: your share is pulled back from your Connect account, and the amount returned is listed separately.\nSet up payouts {#set-up-payouts}\nThe Payouts card on Marketplace → Payouts connects your organization\'s Stripe account so paid listings can pay you: select Set up payouts and finish Stripe\'s onboarding. The card then says where you stand — payouts enabled, setup still to finish in Stripe, or an account to reconnect — and links to your payouts in Stripe. The platform fee is 20% per sale, 30% on the Free plan.\nSetting up payouts needs the Manage marketplace payouts permission, which the workspace\'s owners and admins hold by default. Without it the card still says where payouts stand, its button stays off, and it names the permission to ask an organization admin for. See Marketplace publisher permissions.\nPurchases and the platform fee {#purchases-and-fees}\nEvery paid purchase records what the buyer paid and the platform fee taken from it, and Aglyn staff see recent purchases on their marketplace overview with the fee from each sale. Your share is what is left once that fee is taken, before sales tax.\nWhen a refund cannot be pulled '
9239
9246
  },
9240
9247
  {
9241
9248
  path: '/developers/plugins/reference/extension-points',
@@ -9340,14 +9347,14 @@ export const DOCS_SECTION_INDEX = [
9340
9347
  title: 'Plugin configuration',
9341
9348
  heading: 'The three layers',
9342
9349
  anchor: '#layers',
9343
- text: '| Layer | Where it lives | Who sets it |\n| Schema defaults | Your code | You, the plugin author |\n| Workspace value | orgs/{orgId}/pluginSettings/{pluginId} | An org manager, in Plugins & add-ons |\n| Site override | hosts/{hostId}/pluginSettings/{pluginId} | A site admin, in that site\'s plugin settings |\nEach layer narrows the one before it, per key. A workspace sets a value once and every site it enabled the plugin on follows it; a site that needs a different answer overrides that one field and keeps inheriting the rest. One booking horizon across a chain, with the flagship branch taking bookings further out, is the shape this exists for.\nOnly the keys the site document actually holds are overrides. The site document is not a full copy of the config — it is a sparse patch.'
9350
+ text: '| Layer | Where it lives | Who sets it |\n| Schema defaults | Your code | You, the plugin author |\n| Workspace value | orgs/{orgId}/pluginSettings/{pluginId} | A member holding Organization settings, in Plugins & add-ons |\n| Site override | hosts/{hostId}/pluginSettings/{pluginId} | A member holding Manage site settings, in that site\'s plugin settings |\nEach layer narrows the one before it, per key. A workspace sets a value once and every site it enabled the plugin on follows it; a site that needs a different answer overrides that one field and keeps inheriting the rest. One booking horizon across a chain, with the flagship branch taking bookings further out, is the shape this exists for.\nOnly the keys the site document actually holds are overrides. The site document is not a full copy of the config — it is a sparse patch.'
9344
9351
  },
9345
9352
  {
9346
9353
  path: '/developers/plugins/reference/plugin-config',
9347
9354
  title: 'Plugin configuration',
9348
9355
  heading: 'Declare a schema',
9349
9356
  anchor: '#declare',
9350
- text: 'There is no manifest field for this. A schema is registered in code, at module scope, from a file imported by both your client barrel and your /server entry — so whichever surface loads first, the schema is there.\nRegistration is idempotent and keyed by pluginId; registering again replaces the schema.\nField types {#field-types}\n| type | Editor | Coercion |\n| string | Text field | Anything that is not a string falls back. An empty string is a valid value and is kept. |\n| number | Number field | Must be a finite number, then clamped to min / max — a value outside the range is pulled to the bound, not rejected. |\n| boolean | Switch | Must be an actual boolean. "true" is not one. |\n| select | Dropdown | Must match one of options[].value. |\nlabel is required and description is optional help text under the field.\nvalidate is a cross-field hook run against the merged values before a save. Return an error string to block the save, or null to allow it.\nValues are not trusted The settings documents are client-writable by org managers and site admins, so every read coerces defensively. A value of the wrong type falls back rather than reaching your code — and keys your schema does not declare are dropped entirely, so a field left behind by an older version of your plugin cannot resurface as config.'
9357
+ text: 'There is no manifest field for this. A schema is registered in code, at module scope, from a file imported by both your client barrel and your /server entry — so whichever surface loads first, the schema is there.\nRegistration is idempotent and keyed by pluginId; registering again replaces the schema.\nField types {#field-types}\n| type | Editor | Coercion |\n| string | Text field | Anything that is not a string falls back. An empty string is a valid value and is kept. |\n| number | Number field | Must be a finite number, then clamped to min / max — a value outside the range is pulled to the bound, not rejected. |\n| boolean | Switch | Must be an actual boolean. "true" is not one. |\n| select | Dropdown | Must match one of options[].value. |\nlabel is required and description is optional help text under the field.\nvalidate is a cross-field hook run against the merged values before a save. Return an error string to block the save, or null to allow it.\nValues are not trusted The settings documents are client-writable by members holding those permissions, so every read coerces defensively. A value of the wrong type falls back rather than reaching your code — and keys your schema does not declare are dropped entirely, so a field left behind by an older version of your plugin cannot resurface as config.'
9351
9358
  },
9352
9359
  {
9353
9360
  path: '/developers/plugins/reference/plugin-config',
@@ -9368,7 +9375,7 @@ export const DOCS_SECTION_INDEX = [
9368
9375
  title: 'Plugin configuration',
9369
9376
  heading: 'What the console renders',
9370
9377
  anchor: '#console-ui',
9371
- text: 'The Plugins & add-ons hub builds a form from your schema, so a plugin gets a settings UI without writing one. At site scope the same form marks each field Set for this site or Inherited, and offers a control to drop the override.\nWho may write which document is enforced by security rules, not by the form: the workspace document takes an org manager, the site document takes a site admin. Writes to either are frozen while the organization is suspended or the site\'s writes are frozen.\nNever put a secret in plugin config There is no secret field type and no redaction. Both documents are read client-side — the workspace document by any member of the organization — so anything stored here should be assumed visible to everyone in the workspace and present in the browser. API keys, tokens and signing secrets belong in the environment; see Manifests & environment.'
9378
+ text: 'The Plugins & add-ons hub builds a form from your schema, so a plugin gets a settings UI without writing one. At site scope the same form marks each field Set for this site or Inherited, and offers a control to drop the override.\nWho may write which document is enforced by security rules, not by the form: the workspace document takes Organization settings, the site document takes Manage site settings. Writes to either are frozen while the organization is suspended or the site\'s writes are frozen.\nNever put a secret in plugin config There is no secret field type and no redaction. Both documents are read client-side — the workspace document by any member of the organization — so anything stored here should be assumed visible to everyone in the workspace and present in the browser. API keys, tokens and signing secrets belong in the environment; see Manifests & environment.'
9372
9379
  },
9373
9380
  {
9374
9381
  path: '/developers/plugins/reference/plugin-config',
@@ -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',
@@ -9608,6 +9622,13 @@ export const DOCS_SECTION_INDEX = [
9608
9622
  anchor: '#before-a-closure--plugin-closure-notices',
9609
9623
  text: 'When a workspace is deleted or an account is closed, a plugin finishes its share through plugin-org-erasure and plugin-user-erasure. If that share changes something the person paid for or relies on — an order canceled and refunded, a booking released — say so BEFORE they confirm: register a notice source, and the console\'s Delete organization card and Close your account? dialog print your notices above the confirm.\n| API | Semantics |\n| registerClosureNoticeSource(source, { pluginId? }) | One source per plugin; registering again replaces it. |\n| readClosureNotices(subject) | Every source\'s notices, warnings first, each with its pluginId. Never throws: a source that threw, or answered a notice with no words, no severity or no items, is listed in unavailable, and the screens say some details could not be checked. With nothing registered, it runs the app\'s boot step once and asks again. |\n| GET /api/closure-notices?subject=workspace&orgId=… or ?subject=account | The console\'s route the screens call: the workspace\'s owner (or staff), or the signed-in person for their own account. |\nA notice is information, never a gate: nothing it answers holds a closure back.'
9610
9624
  },
9625
+ {
9626
+ path: '/developers/plugins/reference/plugin-manager-api',
9627
+ title: 'Plugin-manager API reference',
9628
+ heading: 'Before a person erasure — `plugin-person-erasure-notes`',
9629
+ anchor: '#before-a-person-erasure--plugin-person-erasure-notes',
9630
+ text: 'A plugin decides through plugin-person-erasure what it deletes and what it keeps when a person is erased. If it keeps a record with the person still on it, say so BEFORE anyone files: register a note source, and the console\'s Erase a person card prints your sentence.\nA source answers for the workspace, because the card opens before an address is typed: answer nothing when the workspace holds nothing of the kind, and word the sentence so it\'s true of someone with no such record.\n| API | Semantics |\n| registerPersonErasureNoteSource(source, { pluginId? }) | One source per plugin; registering again replaces it. |\n| readPersonErasureNotes({ orgId }) | Every source\'s notes, each with its pluginId. Never throws: a source that threw, or answered a note with no words, is listed in unavailable, and the card says some details could not be checked. With nothing registered, it runs the app\'s boot step once and asks again. |\n| GET /api/person-erasure-notes?orgId=… | The console\'s route the card calls: asks "Privacy requests" (org.privacy) over the whole workspace, as filing does. |\nA note is information, never a gate: nothing it answers holds an erasure back.'
9631
+ },
9611
9632
  {
9612
9633
  path: '/developers/plugins/reference/plugin-manager-api',
9613
9634
  title: 'Plugin-manager API reference',
@@ -9641,7 +9662,7 @@ export const DOCS_SECTION_INDEX = [
9641
9662
  title: 'Plugin-manager API reference',
9642
9663
  heading: 'Contact capture — `plugin-contact-capture` (`/server`)',
9643
9664
  anchor: '#contact-capture--plugin-contact-capture-server',
9644
- text: 'A silo that meets a person — a form submission, a member sign-up, an order, a booking — hands them to whichever plugin keeps people, instead of importing its writer.\n| API | Semantics |\n| registerPluginContactCaptureWriter(writer, { pluginId? }) | A slot: a workspace keeps one set of people, so a second plugin\'s writer throws naming both and the incumbent keeps serving. |\n| capturePluginContact(request) | { ok: true, record: \'contact\', contactId, created } or { ok: true, record: \'lead\', leadId, created } — created: false is a returning visit — or { ok: false, reason, error }, or null when no plugin keeps people. null and a refusal are different answers: null is a workspace with no record system, where nothing has gone wrong. |\n| registerPluginContactSource({ source, label, openLabel?, recordKind? }, { pluginId? }) | One source word has one owner. openLabel is what a link from a timeline entry says, and a door with nothing to open declares none. recordKind is the kind plugin-record-routes addresses the silo\'s own document by. |\n| pluginContactCaptureWriter() / listPluginContactSources() / pluginContactSource(source) | The writer with its owner, every declared door, and one by its word. |\n| labelContactSource(source, fallback?) | How a contact\'s source word reads on screen: the core\'s own label, else the label its plugin declared, else fallback (or the word itself). A plugin cannot relabel a core source. It answers from what this process registered, so declare a door from your declarations entry when the console\'s browser should label it. |\nA refusal is returned, never thrown. Each of these silos has already accepted the submission or taken the money, so a throw would cost it the thing it was recording. reason is invalid-email, band, erased or error, and error is customer'
9665
+ text: 'A silo that meets a person — a form submission, a member sign-up, an order, a booking — hands them to whichever plugin keeps people, instead of importing its writer.\n| API | Semantics |\n| registerPluginContactCaptureWriter(writer, { pluginId? }) | A slot: a workspace keeps one set of people, so a second plugin\'s writer throws naming both and the incumbent keeps serving. |\n| capturePluginContact(request) | { ok: true, record: \'contact\', contactId, created } or { ok: true, record: \'lead\', leadId, created } — created: false is a returning visit — or { ok: false, reason, error }, or null when no plugin keeps people. null and a refusal are different answers: null is a workspace with no record system, where nothing has gone wrong. |\n| registerPluginContactSource({ source, label, openLabel?, recordKind? }, { pluginId? }) | One source word has one owner. openLabel is what a link from a timeline entry says, and a door with nothing to open declares none. recordKind is the kind plugin-record-routes addresses the silo\'s own document by. |\n| pluginContactCaptureWriter() / listPluginContactSources() / pluginContactSource(source) | The writer with its owner, every declared door, and one by its word. |\n| labelContactSource(source, fallback?) | How a contact\'s source word reads on screen: the core\'s own label, else the label its plugin declared, else fallback (or the word itself). A plugin cannot relabel a core source. It answers from what this process registered, so declare a door from your declarations entry when the console\'s browser should label it. |\n| listContactSourceOptions() / isKnownContactSource(source) | Every source a filter can offer, as { value, label }: the core\'s, then each declared door, labeled as labelContactSource labels it. A declared door is a choice in the CRM\'s '
9645
9666
  },
9646
9667
  {
9647
9668
  path: '/developers/plugins/reference/plugin-manager-api',
@@ -10523,7 +10544,7 @@ export const DOCS_SECTION_INDEX = [
10523
10544
  title: 'The console tour',
10524
10545
  heading: 'Primary navigation',
10525
10546
  anchor: '#primary-navigation',
10526
- text: 'The tabs across the top of a site are its sections. Some are always present; the rest are contributed by the plugins your workspace has enabled — so two sites, or the same site before and after you enable a plugin, can show different tabs. Don\'t be surprised by a tab strip that doesn\'t match a screenshot exactly.\nThese four are where a new site\'s work happens:\n| Section | What\'s there |\n| Dashboard | The site at a glance — analytics and recent-signup summaries, and the ten most recent activity entries. |\n| Pages | The page hierarchy — create, reorder (drag-and-drop), and open pages. This is where you build; start at Publish your first page. |\n| Media | The media library — folders, images, video, and files. |\n| Setup | Basic details, your business details and profile, SEO, tracking, theme, and emails. Each section has its own address, so you can bookmark or share the exact one. |\nAlongside them, and always present: Layouts and Components (the shared frames and reusable pieces pages are assembled from — see Pages & Layouts), Templates (saved starting points), Content (collections and blog entries), Users (the people who sign in to the site you\'re building, not your own team), and Analytics. Admin appears only if you\'re an owner or admin of the site; it holds per-site plugin settings, the custom domain, the site\'s security lists, the full activity log, and the danger zone.\nSections that come and go Tabs such as Data, Products, Logic, Automation, Inbox, Bookings, Events, Redirects, Marketing and Marketplace are contributed by plugins and appear only where that plugin is enabled for your workspace (they\'re inserted after Analytics). If a section these docs describe isn\'t in your tab strip, that\'s usually why — enable the plugin under Organization → Plugins.\nBilling is not a '
10547
+ text: 'The tabs across the top of a site are its sections. Some are always present; the rest are contributed by the plugins your workspace has enabled — so two sites, or the same site before and after you enable a plugin, can show different tabs. Don\'t be surprised by a tab strip that doesn\'t match a screenshot exactly.\nThese four are where a new site\'s work happens:\n| Section | What\'s there |\n| Dashboard | The site at a glance — analytics and recent-signup summaries, and the ten most recent activity entries. |\n| Pages | The page hierarchy — create, reorder (drag-and-drop), and open pages. This is where you build; start at Publish your first page. |\n| Media | The media library — folders, images, video, and files. |\n| Setup | Basic details, your business details and profile, SEO, tracking, theme, and emails. Each section has its own address, so you can bookmark or share the exact one. |\nAlongside them, and always present: Layouts and Components (the shared frames and reusable pieces pages are assembled from — see Pages & Layouts), Templates (saved starting points), Content (collections and blog entries), Users (the people who sign in to the site you\'re building, not your own team), and Analytics. Admin appears only if you hold the Manage site settings permission on the site, which the site\'s admins hold by default, and workspace owners and admins are admins of every site. It holds per-site plugin settings, the custom domain, the site\'s security lists, the full activity log, and the danger zone.\nSections that come and go Tabs such as Data, Products, Logic, Automation, Inbox, Bookings, Events, Redirects, Marketing and Marketplace are contributed by plugins and appear only where that plugin is enabled for your workspace (they\'re inserted after Analytics). If a section these docs d'
10527
10548
  },
10528
10549
  {
10529
10550
  path: '/getting-started/console-tour',
@@ -10537,7 +10558,7 @@ export const DOCS_SECTION_INDEX = [
10537
10558
  title: 'The console tour',
10538
10559
  heading: 'The Sites list',
10539
10560
  anchor: '#the-sites-list',
10540
- text: 'All Sites is the front door of a workspace: one card per site, for the workspace currently selected in the switcher, with the sites you pinned first and the rest in name order. A site you can reach in another organization isn\'t missing — it\'s behind the workspace switcher.\nEach card carries:\n- The site\'s display name as the title, with its hostname underneath as the subheader — the custom domain when the site has one, otherwise its name.aglyn.app address. Both are also listed inside the card, as Aglyn Domain and Custom Domain.\n- A status pill (below).\n- A pin, beside the pill. Pinned sites lead the list in the order you pinned them, and the site switcher in the top bar lists them first too. You can pin up to five sites in each workspace; pinning a sixth asks which one it replaces. Your pins are yours alone, and they follow you to every device you sign in on.\n- Visit, which opens the live site in a new tab, and Manage, which opens that site\'s dashboard in the console.\nAbove the cards are a Search box and a Filters button — the same controls a table\'s toolbar has, over the cards. Search finds a site by the start of any word of its name, its slug (the name in name.aglyn.app) or its custom domain: harbor, bakery and shop.harbor all find Harbor Bakery at shop.harbor-bakery.com. Filters narrows the cards by Custom domain (Connected or None) and by the day a site was Created — is, after, on or after, before or on or before a day. Each filter in force shows as a chip above the cards; remove a chip to drop it. A filter on the created date lists the cards newest first instead of by name. While a search or a filter is in force, pinned sites don\'t jump to the top: they sit where the list puts them, with their pin showing.\nThe search and the filters are answered by the query that re'
10561
+ text: 'All Sites is the front door of a workspace: one card per site, for the workspace currently selected in the switcher, with the sites you pinned first and the rest in name order. A site you can reach in another organization isn\'t missing — it\'s behind the workspace switcher.\nEach card carries:\n- The site\'s display name as the title, with its hostname underneath as the subheader — the custom domain when the site has one, otherwise its name.aglyn.app address. Both are also listed inside the card, as Aglyn Domain and Custom Domain.\n- A status pill (below).\n- A pin, beside the pill. Pinned sites lead the list in the order you pinned them, and the site switcher in the top bar lists them first too. Pin as many sites as you like. Your pins are yours alone, and they follow you to every device you sign in on.\n- Visit, which opens the live site in a new tab, and Manage, which opens that site\'s dashboard in the console.\nAbove the cards are a Search box and a Filters button — the same controls a table\'s toolbar has, over the cards. Search finds a site by the start of any word of its name, its slug (the name in name.aglyn.app) or its custom domain: harbor, bakery and shop.harbor all find Harbor Bakery at shop.harbor-bakery.com. Filters narrows the cards by Custom domain (Connected or None) and by the day a site was Created — is, after, on or after, before or on or before a day. Each filter in force shows as a chip above the cards; remove a chip to drop it. A filter on the created date lists the cards newest first instead of by name. While a search or a filter is in force, pinned sites don\'t jump to the top: they sit where the list puts them, with their pin showing.\nThe search and the filters are answered by the query that reads the cards, across every site you have in the workspace, n'
10541
10562
  },
10542
10563
  {
10543
10564
  path: '/getting-started/console-tour',
@@ -10600,7 +10621,7 @@ export const DOCS_SECTION_INDEX = [
10600
10621
  title: 'Create a site',
10601
10622
  heading: 'Site Admin',
10602
10623
  anchor: '#site-admin',
10603
- text: 'Site Admin holds the controls only a site\'s owners and admins should touch, kept apart from Setup so a collaborator never trips over them. Open it from the site navigation; its sections are:\n- General — the site\'s basic details.\n- Plugins — which of the workspace\'s plugins run on this site. See Plugins on one site.\n- Custom Domain — connect your own domain.\n- Security — who can reach the site.\n- Error pages — the pages shown when something goes wrong.\n- Activity — the full log of changes made to the site.\n- Backup & template — download a backup or import a package.\n- Danger zone — deleting the site.\nWho can open Site Admin {#who-can-open-site-admin}\nOnly a site\'s admins can open Site Admin; anyone else who follows a link to it is told so instead of seeing the sections. To get in, ask a site admin or a workspace owner to raise your role on this site — see Teams & roles.'
10624
+ text: 'Site Admin holds the controls that take the Manage site settings permission, kept apart from Setup so a collaborator never trips over them. Open it from the site navigation; its sections are:\n- General — the site\'s basic details.\n- Plugins — which of the workspace\'s plugins run on this site. See Plugins on one site.\n- Custom Domain — connect your own domain.\n- Security — who can reach the site.\n- Error pages — the pages shown when something goes wrong.\n- Activity — the full log of changes made to the site.\n- Backup & template — download a backup or import a package.\n- Danger zone — deleting the site.\nWho can open Site Admin {#who-can-open-site-admin}\nOpening Site Admin takes the Manage site settings permission on the site, which the site\'s admins hold by default, and workspace owners and admins are admins of every site. Anyone else who follows a link to it is told so instead of seeing the sections. To get in, ask a site admin or a workspace owner to raise your role on this site or grant you the permission — see Site permissions.'
10604
10625
  },
10605
10626
  {
10606
10627
  path: '/getting-started/create-a-site',
@@ -10817,7 +10838,7 @@ export const DOCS_SECTION_INDEX = [
10817
10838
  title: 'Commerce end to end',
10818
10839
  heading: '5. Run orders from the console',
10819
10840
  anchor: '#5-run-orders-from-the-console',
10820
- 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.'
10821
10842
  },
10822
10843
  {
10823
10844
  path: '/guides/commerce-end-to-end',
@@ -10971,7 +10992,7 @@ export const DOCS_SECTION_INDEX = [
10971
10992
  title: 'Install your first marketplace item',
10972
10993
  heading: 'Manage your plugins',
10973
10994
  anchor: '#manage-plugins',
10974
- text: 'Plugins, in the organization navigation, is where you switch plugins on and off for the whole workspace — the ones you installed from the Marketplace, listed first, and Aglyn\'s own built-in plugins below them. Open any plugin to see where it runs and change its settings.\nFind the Plugins section {#find-plugins}\nPlugins is its own section in the organization navigation, next to Marketplace. Organization → Settings → Plugins used to hold the switches; it now only points you to the section, where enabling, configuring and managing marketplace installs all live.\nBuilt-in plugins {#built-in-plugins}\nThe Built in card lists the plugins that ship with Aglyn, each with its own switch. Switching one off removes it from every site in the workspace — its navigation, the editor, published pages and the API — and switching it back on restores it.\n- Only workspace owners and admins can flip a switch.\n- A few cannot be switched off at all, because sites are built out of them.\n- AI and Forms have no workspace switch: they stay on for the workspace, and a site switches them off for itself — see A plugin on one site.\n- Switching off a plugin that another one depends on asks first, and names what else will go with it.\nA plugin\'s page {#a-plugins-page}\nOpen a plugin from the Plugins section to manage it for the workspace. Its page shows Where it runs, the plugin\'s own settings — saved once for the workspace and followed by every site — its Dependencies, and, for a marketplace plugin, the version you are pinned to and what it is allowed to reach. View listing opens a marketplace plugin\'s listing.\nWhere a plugin runs {#where-a-plugin-runs}\nThe Where it runs card on a plugin\'s page answers which of your sites have it. A built-in plugin has a single switch: on, it runs on every site in the wor'
10995
+ text: 'Plugins, in the organization navigation, is where you switch plugins on and off for the whole workspace — the ones you installed from the Marketplace, listed first, and Aglyn\'s own built-in plugins below them. Open any plugin to see where it runs and change its settings.\nFind the Plugins section {#find-plugins}\nPlugins is its own section in the organization navigation, next to Marketplace. Organization → Settings → Plugins used to hold the switches; it now only points you to the section, where enabling, configuring and managing marketplace installs all live.\nBuilt-in plugins {#built-in-plugins}\nThe Built in card lists the plugins that ship with Aglyn, each with its own switch. Switching one off removes it from every site in the workspace — its navigation, the editor, published pages and the API — and switching it back on restores it.\n- Flipping a switch needs the Organization settings permission, which the workspace\'s owners and admins hold by default. Without it the switches stay off, and a plugin\'s page names the permission to ask an organization admin for.\n- A few cannot be switched off at all, because sites are built out of them.\n- AI and Forms have no workspace switch: they stay on for the workspace, and a site switches them off for itself — see A plugin on one site.\n- Switching off a plugin that another one depends on asks first, and names what else will go with it.\nA plugin\'s page {#a-plugins-page}\nOpen a plugin from the Plugins section to manage it for the workspace. Its page shows Where it runs, the plugin\'s own settings — saved once for the workspace and followed by every site — its Dependencies, and, for a marketplace plugin, the version you are pinned to and what it is allowed to reach. View listing opens a marketplace plugin\'s listing.\nWhere a plugin runs {'
10975
10996
  },
10976
10997
  {
10977
10998
  path: '/guides/install-your-first-plugin',
@@ -11335,7 +11356,7 @@ export const DOCS_SECTION_INDEX = [
11335
11356
  title: 'Your first API call',
11336
11357
  heading: '',
11337
11358
  anchor: '',
11338
- 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.'
11339
11360
  },
11340
11361
  {
11341
11362
  path: '/guides/your-first-api-call',
@@ -11972,7 +11993,7 @@ export const DOCS_SECTION_INDEX = [
11972
11993
  title: 'Email platforms (Mailchimp, Klaviyo, Omnisend)',
11973
11994
  heading: 'Connect a platform',
11974
11995
  anchor: '#connect',
11975
- 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.'
11976
11997
  },
11977
11998
  {
11978
11999
  path: '/marketing-and-automation/email-campaigns/email-platforms',
@@ -12357,7 +12378,7 @@ export const DOCS_SECTION_INDEX = [
12357
12378
  title: 'Org automations',
12358
12379
  heading: 'Every site\'s own automations',
12359
12380
  anchor: '#every-sites-own-automations',
12360
- 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.'
12361
12382
  },
12362
12383
  {
12363
12384
  path: '/marketing-and-automation/workflows-and-actions/org-automations',
@@ -12602,7 +12623,7 @@ export const DOCS_SECTION_INDEX = [
12602
12623
  title: 'Downgrading, canceling & your data',
12603
12624
  heading: 'Deleting a single site',
12604
12625
  anchor: '#deleting-a-single-site',
12605
- text: 'To remove just one site (not the whole organization), open the site\'s Admin → Danger zone and use Delete site. A site admin types the site name to confirm, and it\'s deleted immediately — its pages, media, and settings are permanently removed and its address stops resolving. Unlike an organization deletion there\'s no hold, so export a backup first (Setup → Backup & restore) if you might want it back. Your other sites and the organization are unaffected.\nDeleting a site also deletes what is the site\'s own:\n- Datasets shared with this site only, with all their records. The Delete site card lists them, with how many records each holds, before you confirm. A dataset the site shares with other sites stays, and the site is removed from its sharing. A dataset shared with All sites isn\'t affected.\n- The site\'s AI jobs, AI insights and Assist conversations.\nTo keep a dataset, share it with another site, or with All sites, from its Sharing control on the Data page before you delete the site.\nA site in a consent group can\'t be deleted while it\'s in the group, because the group\'s other sites honor the unsubscribes it holds. Remove it from the group first, which copies those opt-outs to the sites that stay, then delete it. The same applies while a consent group change that includes the site is still finishing.'
12626
+ text: 'To remove just one site (not the whole organization), open the site\'s Admin → Danger zone and use Delete site. It takes the Manage site settings permission on the site and Delete sites, which workspace owners and admins hold by default. You type the site name to confirm, and it\'s deleted immediately — its pages, media, and settings are permanently removed and its address stops resolving. Unlike an organization deletion there\'s no hold, so export a backup first (Setup → Backup & restore) if you might want it back. Your other sites and the organization are unaffected.\nDeleting a site also deletes what is the site\'s own:\n- Datasets shared with this site only, with all their records. The Delete site card lists them, with how many records each holds, before you confirm. A dataset the site shares with other sites stays, and the site is removed from its sharing. A dataset shared with All sites isn\'t affected.\n- The site\'s AI jobs, AI insights and Assist conversations.\nTo keep a dataset, share it with another site, or with All sites, from its Sharing control on the Data page before you delete the site.\nA site in a consent group can\'t be deleted while it\'s in the group, because the group\'s other sites honor the unsubscribes it holds. Remove it from the group first, which copies those opt-outs to the sites that stay, then delete it. The same applies while a consent group change that includes the site is still finishing.'
12606
12627
  },
12607
12628
  {
12608
12629
  path: '/workspace-and-billing/billing-and-plans/downgrading-and-canceling',
@@ -12714,7 +12735,7 @@ export const DOCS_SECTION_INDEX = [
12714
12735
  title: 'Import and export',
12715
12736
  heading: '',
12716
12737
  anchor: '',
12717
- 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.'
12718
12739
  },
12719
12740
  {
12720
12741
  path: '/workspace-and-billing/import-and-export',
@@ -12973,14 +12994,14 @@ export const DOCS_SECTION_INDEX = [
12973
12994
  title: 'Signing In & Sessions',
12974
12995
  heading: 'Downloading your data',
12975
12996
  anchor: '#downloading-your-data',
12976
- 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'
12977
12998
  },
12978
12999
  {
12979
13000
  path: '/workspace-and-billing/signing-in-and-sessions',
12980
13001
  title: 'Signing In & Sessions',
12981
13002
  heading: 'Privacy requests',
12982
13003
  anchor: '#privacy-requests',
12983
- text: 'Settings → Privacy is where a workspace answers the people its sites hold: someone who asks for the data you keep about them, or asks to be forgotten. The section is shown to members with the Privacy requests permission — workspace owners and admins by default, and anyone a custom role grants it — and it is on every plan, Free included. These are obligations rather than features, so they sit outside the CRM and do not wait for a plan that includes it.\nExporting contacts and leads\nExport contacts exports every contact the workspace holds, and Export leads every lead its sites captured. Each opens the same export dialog as the CRM\'s Export…: choose the fields (custom fields included) and the format — CSV, JSON or NDJSON — and the file covers every record, whether or not your plan includes the CRM. Exporting needs the Manage data permission, which owners and admins hold. If fewer rows arrive than the server promised, because a connection dropped, nothing is saved and you are told so; try again.\nErasing a person\nErase a person is the privacy erasure, for someone who asks to be forgotten under the GDPR, the CCPA or any similar law. Type the person\'s email address, type it again to confirm, and choose Erase permanently. It cannot be undone.\n- It is filed by address, across the workspace. It reaches every site of the workspace, whether or not any page shows the person.\n- Capture stops at once. From the moment the request is filed, your sites stop capturing the address, and no campaign is sent to it.\n- The nightly erasure job completes it. Before you choose, the card lists what the job removes, what it keeps with the person taken off, and what it does not reach:\n| | |\n| Removed across the workspace | The contact record on every site — profile, notes, tags, timeline and custom f'
13004
+ text: 'Settings → Privacy is where a workspace answers the people its sites hold: someone who asks for the data you keep about them, or asks to be forgotten. The section is shown to members with the Privacy requests permission — workspace owners and admins by default, and anyone a custom role grants it — and it is on every plan, Free included. These are obligations rather than features, so they sit outside the CRM and do not wait for a plan that includes it.\nExporting contacts and leads\nExport contacts exports every contact the workspace holds, and Export leads every lead its sites captured. Each opens the same export dialog as the CRM\'s Export…: choose the fields (custom fields included) and the format — CSV, JSON or NDJSON — and the file covers every record, whether or not your plan includes the CRM. Exporting needs the Manage data permission, which owners, admins and editors hold by default. If fewer rows arrive than the server promised, because a connection dropped, nothing is saved and you are told so; try again.\nErasing a person\nErase a person is the privacy erasure, for someone who asks to be forgotten under the GDPR, the CCPA or any similar law. Type the person\'s email address, type it again to confirm, and choose Erase permanently. It cannot be undone.\n- It is filed by address, across the workspace. It reaches every site of the workspace, whether or not any page shows the person.\n- Capture stops at once. From the moment the request is filed, your sites stop capturing the address, and no campaign is sent to it.\n- The nightly erasure job completes it. Before you choose, the card lists what the job removes, what it keeps with the person taken off, and what it does not reach:\n| | |\n| Removed across the workspace | The contact record on every site — profile, notes, tags, t'
12984
13005
  },
12985
13006
  {
12986
13007
  path: '/workspace-and-billing/signing-in-and-sessions',
@@ -13127,7 +13148,7 @@ export const DOCS_SECTION_INDEX = [
13127
13148
  title: 'Invite teammates',
13128
13149
  heading: 'A member\'s page',
13129
13150
  anchor: '#member-page',
13130
- text: 'Open anyone from the Team page to see their own page: their role and site access, a Password card for helping them back in, what has been changed about them, everything they have done in the organization, and their AI usage and allotment.\nRole and site access {#member-access}\nThe Member card sets this person\'s organization role and job title and, for an editor or viewer, which sites they can reach. Roles are Admin, Editor and Viewer. Admins reach every site; for an editor or viewer, turn off Access to all sites and choose Editor, Viewer or No access on each site, so they see only those. Save applies the change; Remove from organization takes them off the team and frees their seat.\nEditing a member needs the admin role. The owner\'s role is not edited here — ownership moves under Settings → Transfer ownership.\nOne member\'s activity {#member-activity}\nActivity by this member lists everything this person has done in the organization — on its sites as well as at organization level — newest first. Above it, Changes to this member lists what others changed about them, such as role and access edits. Both need the Activity & audit log permission, the same as the organization\'s activity log.\nChanges to this member {#member-changes}\nChanges to this member lists what other people changed about this person, such as role and site-access edits, newest first, with who made each change and when. It reads the same entries as the organization\'s activity log, narrowed to the ones whose target is this member.'
13151
+ text: 'Open anyone from the Team page to see their own page: their role and site access, a Password card for helping them back in, what has been changed about them, everything they have done in the organization, and their AI usage and allotment.\nRole and site access {#member-access}\nThe Member card sets this person\'s organization role and job title and, for an editor or viewer, which sites they can reach. Roles are Admin, Editor and Viewer. Admins reach every site; for an editor or viewer, turn off Access to all sites and choose Editor, Viewer or No access on each site, so they see only those. Save applies the change; Remove from organization takes them off the team and frees their seat.\nEditing a member needs the Manage members permission, which owners and admins hold by default. The owner\'s role is not edited here — ownership moves under Settings → Transfer ownership.\nOne member\'s activity {#member-activity}\nActivity by this member lists everything this person has done in the organization — on its sites as well as at organization level — newest first. Above it, Changes to this member lists what others changed about them, such as role and access edits. Both need the Activity & audit log permission, the same as the organization\'s activity log.\nChanges to this member {#member-changes}\nChanges to this member lists what other people changed about this person, such as role and site-access edits, newest first, with who made each change and when. It reads the same entries as the organization\'s activity log, narrowed to the ones whose target is this member.'
13131
13152
  },
13132
13153
  {
13133
13154
  path: '/workspace-and-billing/teams-and-roles/invite-teammates',
@@ -13197,7 +13218,7 @@ export const DOCS_SECTION_INDEX = [
13197
13218
  title: 'Members-only areas',
13198
13219
  heading: 'Manage your members',
13199
13220
  anchor: '#manage-your-members',
13200
- text: 'The site\'s Users page lists everyone who signed up on your published site — paged, newest first. The search box finds a member by the start of any word of their name or email address, and Filters in the table\'s toolbar narrows the list by email, name, join date or Status (Active or Suspended). They add up — except that a Name contains filter and a search can\'t stand together, and the list says which it set aside — across every member rather than the page on screen, because the query that reads the list answers them all. The member guide names each filter\'s operators. See Filter and search a list. Click a member to open their detail drawer:\n- Profile — email, display name, join date, and saved addresses.\n- Order history — the member\'s payment records, newest first: order number, status, total, and date, plus the Stripe payment reference and any refunded amount. Order history is visible to site admins and editors.\n- Subscriptions — active and past storefront subscriptions with their renewal date.\n- Lifetime purchases — everything the member actually paid: charged order totals minus refunds (pending and canceled orders don\'t count).\nSuspend or reactivate a member\nFrom the drawer you can suspend a member (with a confirmation). A suspended member:\n- can no longer sign in on your published site — they see a clear "account suspended" message;\n- is signed out the next time their account page loads;\n- keeps all orders, subscriptions, and history — nothing is deleted.\nReactivate restores access with the member\'s existing password. The member list shows each account\'s Active/Suspended status at a glance.'
13221
+ text: 'The site\'s Users page lists everyone who signed up on your published site — paged, newest first. The search box finds a member by the start of any word of their name or email address, and Filters in the table\'s toolbar narrows the list by email, name, join date or Status (Active or Suspended). They add up — except that a Name contains filter and a search can\'t stand together, and the list says which it set aside — across every member rather than the page on screen, because the query that reads the list answers them all. The member guide names each filter\'s operators. See Filter and search a list. Click a member to open their detail drawer:\n- Profile — email, display name, join date, and saved addresses.\n- Order history — the member\'s payment records, newest first: order number, status, total, and date, plus the Stripe payment reference and any refunded amount. Order history takes the See orders and webhooks permission, which a site\'s admins and editors hold by default.\n- Subscriptions — active and past storefront subscriptions with their renewal date.\n- Lifetime purchases — everything the member actually paid: charged order totals minus refunds (pending and canceled orders don\'t count).\nSuspend or reactivate a member\nFrom the drawer you can suspend a member (with a confirmation). A suspended member:\n- can no longer sign in on your published site — they see a clear "account suspended" message;\n- is signed out the next time their account page loads;\n- keeps all orders, subscriptions, and history — nothing is deleted.\nReactivate restores access with the member\'s existing password. The member list shows each account\'s Active/Suspended status at a glance.'
13201
13222
  },
13202
13223
  {
13203
13224
  path: '/workspace-and-billing/teams-and-roles/members-only',
@@ -13274,7 +13295,7 @@ export const DOCS_SECTION_INDEX = [
13274
13295
  title: 'White-label',
13275
13296
  heading: 'Where the settings are',
13276
13297
  anchor: '#where',
13277
- 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.'
13278
13299
  },
13279
13300
  {
13280
13301
  path: '/workspace-and-billing/white-label',
@@ -13309,7 +13330,7 @@ export const DOCS_SECTION_INDEX = [
13309
13330
  title: 'White-label',
13310
13331
  heading: 'Not the same as renaming a self-hosted platform',
13311
13332
  anchor: '#platform-brand',
13312
- text: 'These two get confused constantly, and they are unrelated mechanisms:\n| | White-label brand | Platform brand |\n| Who sets it | An organization admin, in the console | Whoever runs the deployment, in its environment |\n| Scope | That one organization | The entire installation, every organization on it |\n| How | The card on this page | NEXTPUBLICPLATFORMBRANDNAME and friends |\n| Gated on | The whiteLabel entitlement | Nothing — it is deployment configuration |\n| Takes effect | On save | On the next image build, not a restart |\nIf you are running Aglyn yourself and want the product to stop calling itself Aglyn for everybody, that is the platform brand, not this card — see Self-hosting. The two compose: on a self-hosted installation, an organization without the whiteLabel entitlement falls back to the operator\'s platform brand rather than to Aglyn\'s.'
13333
+ text: 'These two get confused constantly, and they are unrelated mechanisms:\n| | White-label brand | Platform brand |\n| Who sets it | A member holding Organization settings, in the console | Whoever runs the deployment, in its environment |\n| Scope | That one organization | The entire installation, every organization on it |\n| How | The card on this page | NEXTPUBLICPLATFORMBRANDNAME and friends |\n| Gated on | The whiteLabel entitlement | Nothing — it is deployment configuration |\n| Takes effect | On save | On the next image build, not a restart |\nIf you are running Aglyn yourself and want the product to stop calling itself Aglyn for everybody, that is the platform brand, not this card — see Self-hosting. The two compose: on a self-hosted installation, an organization without the whiteLabel entitlement falls back to the operator\'s platform brand rather than to Aglyn\'s.'
13313
13334
  },
13314
13335
  {
13315
13336
  path: '/workspace-and-billing/white-label',