@aglyn/aglyn 1.10.0 → 1.12.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.
- package/package.json +11 -11
- package/src/lib/app-utils/account-preferences.d.ts +15 -13
- package/src/lib/app-utils/account-preferences.js +20 -20
- package/src/lib/app-utils/account-preferences.js.map +1 -1
- package/src/lib/app-utils/crm.d.ts +3 -1
- package/src/lib/app-utils/crm.js +6 -3
- package/src/lib/app-utils/crm.js.map +1 -1
- package/src/lib/app-utils/docs-help-sections.generated.js +3 -3
- package/src/lib/app-utils/docs-help-sections.generated.js.map +1 -1
- package/src/lib/app-utils/docs-help.generated.d.ts +2 -2
- package/src/lib/app-utils/docs-help.generated.js +2 -0
- package/src/lib/app-utils/docs-help.generated.js.map +1 -1
- package/src/lib/app-utils/docs-index.generated.js +76 -69
- package/src/lib/app-utils/docs-index.generated.js.map +1 -1
- package/src/lib/app-utils/full-use-cost.d.ts +28 -11
- package/src/lib/app-utils/full-use-cost.js +31 -15
- package/src/lib/app-utils/full-use-cost.js.map +1 -1
- package/src/lib/app-utils/markdown-lite.js +8 -1
- package/src/lib/app-utils/markdown-lite.js.map +1 -1
- package/src/lib/app-utils/org-role-grants.d.ts +6 -0
- package/src/lib/app-utils/org-role-grants.js +3 -1
- package/src/lib/app-utils/org-role-grants.js.map +1 -1
- package/src/lib/app-utils/person-erasure.d.ts +8 -0
- package/src/lib/app-utils/person-erasure.js +6 -0
- package/src/lib/app-utils/person-erasure.js.map +1 -1
- package/src/lib/app-utils/plan-entitlements.d.ts +27 -1
- package/src/lib/app-utils/plan-entitlements.js +44 -3
- package/src/lib/app-utils/plan-entitlements.js.map +1 -1
- package/src/lib/app-utils/site-preview.d.ts +6 -2
- package/src/lib/app-utils/site-preview.js +5 -3
- package/src/lib/app-utils/site-preview.js.map +1 -1
- package/src/lib/app-utils/site-unavailable.d.ts +4 -7
- package/src/lib/app-utils/site-unavailable.js +4 -8
- package/src/lib/app-utils/site-unavailable.js.map +1 -1
- package/src/lib/app-utils/upgrade-proposal.d.ts +17 -3
- package/src/lib/app-utils/upgrade-proposal.js +28 -6
- package/src/lib/app-utils/upgrade-proposal.js.map +1 -1
- package/src/lib/foundation/definitions/org-billing.types.d.ts +22 -0
- package/src/lib/foundation/definitions/org-billing.types.js +2 -2
- package/src/lib/foundation/definitions/org-billing.types.js.map +1 -1
- package/src/lib/foundation/definitions/platform.types.d.ts +1 -1
- package/src/lib/foundation/definitions/platform.types.js.map +1 -1
- package/src/lib/foundation/definitions/write-deny-coverage.util.d.ts +1 -1
- package/src/lib/foundation/definitions/write-deny-coverage.util.js +1 -1
- package/src/lib/foundation/definitions/write-deny-coverage.util.js.map +1 -1
- package/src/lib/plugin-manager/first-party-plugins.generated.js +1 -1
- package/src/lib/plugin-manager/first-party-plugins.generated.js.map +1 -1
- package/src/lib/plugin-manager/plugin-contact-capture.d.ts +18 -0
- package/src/lib/plugin-manager/plugin-contact-capture.js +26 -0
- package/src/lib/plugin-manager/plugin-contact-capture.js.map +1 -1
- package/src/lib/plugin-manager/plugin-person-erasure-notes.d.ts +61 -0
- package/src/lib/plugin-manager/plugin-person-erasure-notes.js +114 -0
- package/src/lib/plugin-manager/plugin-person-erasure-notes.js.map +1 -0
- package/src/lib/plugin-manager/plugin-site-starters.d.ts +7 -0
- package/src/lib/plugin-manager/plugin-site-starters.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
|
|
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',
|
|
@@ -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,
|
|
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.
|
|
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
|
|
803
|
+
text: 'On every paid plan, Create with AI runs on the AI credits your plan includes each month; nothing else needs to be bought. Blocks of AI credits add more on top when you need them, and a member holding Manage billing adds them in Billing.\nA Free workspace\'s buttons work from the 300 AI credits it gets each month.\nIf Create with AI is switched off for your workspace, the button is still there and opens a short window saying what it would make:\n- a member holding Manage billing sees Add Aglyn AI, which opens Billing to choose a tier, or Not now;\n- anyone else is asked to have a workspace owner or admin choose one.'
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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.
|
|
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.
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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.
|
|
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|
|
|
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.
|
|
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.
|
|
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
|
|
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
|
|
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
|
|
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',
|
|
@@ -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
|
|
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-
|
|
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
|
|
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',
|
|
@@ -5805,7 +5805,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
5805
5805
|
title: 'Quotes',
|
|
5806
5806
|
heading: 'Totals and tax',
|
|
5807
5807
|
anchor: '#totals-and-tax',
|
|
5808
|
-
text: 'The totals add up the items (included items count nothing), take off the discount, then add shipping and tax. Tax follows your store\'s tax settings:\n- Manual rates: the rate for the quote\'s ship-to state and country, or for your store\'s address when the quote has no ship-to country. The discount comes off before tax, and shipping is not taxed. A product marked tax-exempt is left out.\n- A connected tax service (Tax services) prices the quote when you save it, and the quote shows its figure.\n- Stripe Tax: the quote says Tax is added at payment, because Stripe works out the tax when the customer pays.\n- No sales tax: no tax is added.\nIf your store hasn\'t chosen how it handles sales tax, the quote shows no tax and
|
|
5808
|
+
text: 'The totals add up the items (included items count nothing), take off the discount, then add shipping and tax. Tax follows your store\'s tax settings:\n- Manual rates: the rate for the quote\'s ship-to state and country, or for your store\'s address when the quote has no ship-to country. The discount comes off before tax, and shipping is not taxed. A product marked tax-exempt is left out.\n- A connected tax service (Tax services) prices the quote when you save it, and the quote shows its figure.\n- Stripe Tax: the quote says Tax is added at payment, because Stripe works out the tax when the customer pays.\n- No sales tax: no tax is added.\nIf your store hasn\'t chosen how it handles sales tax, the quote shows no tax, and your customer can\'t pay it online until you choose in Taxes. A quote you saved before then takes your choice when your customer opens it and pays, with no need to save it again: Don\'t collect sales tax, Stripe Tax (automatic), or manual rates with Prices include tax turned on. On manual rates with Prices include tax off, save the quote again so its tax is worked out, by your tax service where one is connected.'
|
|
5809
5809
|
},
|
|
5810
5810
|
{
|
|
5811
5811
|
path: '/commerce-and-bookings/commerce/quotes-and-proofs',
|
|
@@ -5889,7 +5889,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
5889
5889
|
title: 'Quotes',
|
|
5890
5890
|
heading: 'How your customer pays',
|
|
5891
5891
|
anchor: '#paying',
|
|
5892
|
-
text: 'Pay charges the quote as you saved it, priced from its items, discount, shipping and tax. Your customer pays on the page itself, or on a Stripe payment page that brings them back to the quote afterward. Their email is filled in from the quote. When the quote charges shipping, they\'re asked where it ships, starting from the quote\'s ship-to. Under Stripe Tax, the tax is worked out from that address when they pay.\nIf you edit the quote while your customer has it open, Pay asks them to reload the page first, so nobody pays for a version they haven\'t seen. Editing a quote, deleting it or replacing its link also closes any payment your customer had started for it.\nPaying needs a connected Stripe account and a decision about sales tax. Until your store has both, Pay
|
|
5892
|
+
text: 'Pay charges the quote as you saved it, priced from its items, discount, shipping and tax. Your customer pays on the page itself, or on a Stripe payment page that brings them back to the quote afterward. Their email is filled in from the quote. When the quote charges shipping, they\'re asked where it ships, starting from the quote\'s ship-to. Under Stripe Tax, the tax is worked out from that address when they pay.\nIf you edit the quote while your customer has it open, Pay asks them to reload the page first, so nobody pays for a version they haven\'t seen. Editing a quote, deleting it or replacing its link also closes any payment your customer had started for it.\nPaying needs a connected Stripe account and a decision about sales tax. Until your store has both, the quote page has no Pay button. When Stripe isn\'t ready, the page says your business can\'t take payments online right now and asks the customer to contact you to pay; otherwise it asks them to contact you to pay.\nYou hear about it first, in the console. While Stripe or the sales tax choice stands in the way, a quote\'s editor, its Pay link section, the Send quote form and the Send invoice form say Customers can\'t pay this quote online yet (the Send invoice form says invoice) and name what\'s missing, each with a button to fix it: Open Payments to connect Stripe, Open Taxes to choose how your store handles sales tax, or a reminder to save the quote again. You can still copy the pay link and email the quote, if you take the payment another way. Send invoice sends without Stripe too, but waits until the quote\'s sales tax is settled.'
|
|
5893
5893
|
},
|
|
5894
5894
|
{
|
|
5895
5895
|
path: '/commerce-and-bookings/commerce/quotes-and-proofs',
|
|
@@ -6099,7 +6099,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
6099
6099
|
title: 'Sales channels',
|
|
6100
6100
|
heading: 'Turn sales channels off for a site',
|
|
6101
6101
|
anchor: '#turn-off',
|
|
6102
|
-
text: 'Sales channels are on for every site in a workspace. A site
|
|
6102
|
+
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
6103
|
},
|
|
6104
6104
|
{
|
|
6105
6105
|
path: '/commerce-and-bookings/commerce/sales-channels',
|
|
@@ -6183,7 +6183,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
6183
6183
|
title: 'Shipping',
|
|
6184
6184
|
heading: 'Ask Aglyn AI',
|
|
6185
6185
|
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-
|
|
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- 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
6187
|
},
|
|
6188
6188
|
{
|
|
6189
6189
|
path: '/commerce-and-bookings/commerce/shipping',
|
|
@@ -6547,7 +6547,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
6547
6547
|
title: 'Waivers',
|
|
6548
6548
|
heading: 'Write a waiver',
|
|
6549
6549
|
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
|
|
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 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
6551
|
},
|
|
6552
6552
|
{
|
|
6553
6553
|
path: '/commerce-and-bookings/commerce/waivers',
|
|
@@ -6575,14 +6575,14 @@ export const DOCS_SECTION_INDEX = [
|
|
|
6575
6575
|
title: 'Waivers',
|
|
6576
6576
|
heading: 'At check-in',
|
|
6577
6577
|
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
|
|
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 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
6579
|
},
|
|
6580
6580
|
{
|
|
6581
6581
|
path: '/commerce-and-bookings/commerce/waivers',
|
|
6582
6582
|
title: 'Waivers',
|
|
6583
6583
|
heading: 'Minors',
|
|
6584
6584
|
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
|
|
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 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
6586
|
},
|
|
6587
6587
|
{
|
|
6588
6588
|
path: '/commerce-and-bookings/commerce/waivers',
|
|
@@ -6603,7 +6603,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
6603
6603
|
title: 'Waivers',
|
|
6604
6604
|
heading: 'Contacts',
|
|
6605
6605
|
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.'
|
|
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, and the list\'s Source filter finds everyone who came in that way.'
|
|
6607
6607
|
},
|
|
6608
6608
|
{
|
|
6609
6609
|
path: '/commerce-and-bookings/commerce/waivers',
|
|
@@ -6617,7 +6617,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
6617
6617
|
title: 'Waivers',
|
|
6618
6618
|
heading: 'How long signed waivers are kept',
|
|
6619
6619
|
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.'
|
|
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. 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
6621
|
},
|
|
6622
6622
|
{
|
|
6623
6623
|
path: '/commerce-and-bookings/commerce/waivers',
|
|
@@ -7058,7 +7058,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
7058
7058
|
title: 'The contact record',
|
|
7059
7059
|
heading: '',
|
|
7060
7060
|
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.'
|
|
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 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
7062
|
},
|
|
7063
7063
|
{
|
|
7064
7064
|
path: '/content-and-data/crm/contact-record',
|
|
@@ -7114,7 +7114,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
7114
7114
|
title: 'The contact record',
|
|
7115
7115
|
heading: 'Lifecycle stages',
|
|
7116
7116
|
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
|
|
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, 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
7118
|
},
|
|
7119
7119
|
{
|
|
7120
7120
|
path: '/content-and-data/crm/contact-record',
|
|
@@ -7275,7 +7275,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
7275
7275
|
title: 'Deals pipeline',
|
|
7276
7276
|
heading: 'Moving, winning and losing',
|
|
7277
7277
|
anchor: '#moving-winning-and-losing',
|
|
7278
|
-
text: '
|
|
7278
|
+
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
7279
|
},
|
|
7280
7280
|
{
|
|
7281
7281
|
path: '/content-and-data/crm/deals',
|
|
@@ -7471,7 +7471,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
7471
7471
|
title: 'Leads',
|
|
7472
7472
|
heading: '',
|
|
7473
7473
|
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.'
|
|
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; 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
7475
|
},
|
|
7476
7476
|
{
|
|
7477
7477
|
path: '/content-and-data/crm/leads',
|
|
@@ -7520,7 +7520,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
7520
7520
|
title: 'Leads',
|
|
7521
7521
|
heading: 'Erasing the person',
|
|
7522
7522
|
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.
|
|
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. 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
7524
|
},
|
|
7525
7525
|
{
|
|
7526
7526
|
path: '/content-and-data/crm/leads',
|
|
@@ -7611,7 +7611,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
7611
7611
|
title: 'CRM',
|
|
7612
7612
|
heading: 'Who can open the CRM',
|
|
7613
7613
|
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.'
|
|
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.\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
7615
|
},
|
|
7616
7616
|
{
|
|
7617
7617
|
path: '/content-and-data/crm/overview',
|
|
@@ -7793,7 +7793,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
7793
7793
|
title: 'Sequences',
|
|
7794
7794
|
heading: 'Sequences',
|
|
7795
7795
|
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
|
|
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 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
7797
|
},
|
|
7798
7798
|
{
|
|
7799
7799
|
path: '/content-and-data/crm/sequences',
|
|
@@ -7863,7 +7863,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
7863
7863
|
title: 'CRM settings',
|
|
7864
7864
|
heading: '',
|
|
7865
7865
|
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.\
|
|
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.\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
7867
|
},
|
|
7868
7868
|
{
|
|
7869
7869
|
path: '/content-and-data/crm/settings',
|
|
@@ -7905,7 +7905,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
7905
7905
|
title: 'CRM settings',
|
|
7906
7906
|
heading: 'Email capture',
|
|
7907
7907
|
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
|
|
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 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
7909
|
},
|
|
7910
7910
|
{
|
|
7911
7911
|
path: '/content-and-data/crm/settings',
|
|
@@ -7933,14 +7933,14 @@ export const DOCS_SECTION_INDEX = [
|
|
|
7933
7933
|
title: 'Share records across sites',
|
|
7934
7934
|
heading: '',
|
|
7935
7935
|
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
|
|
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 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
7937
|
},
|
|
7938
7938
|
{
|
|
7939
7939
|
path: '/content-and-data/crm/sharing',
|
|
7940
7940
|
title: 'Share records across sites',
|
|
7941
7941
|
heading: 'What a shared record looks like',
|
|
7942
7942
|
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;
|
|
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; 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
7944
|
},
|
|
7945
7945
|
{
|
|
7946
7946
|
path: '/content-and-data/crm/sharing',
|
|
@@ -8115,7 +8115,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
8115
8115
|
title: 'Saved views',
|
|
8116
8116
|
heading: 'Segments and views',
|
|
8117
8117
|
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.'
|
|
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. 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
8119
|
},
|
|
8120
8120
|
{
|
|
8121
8121
|
path: '/content-and-data/crm/views',
|
|
@@ -8269,7 +8269,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
8269
8269
|
title: 'Datasets & Dynamic Content',
|
|
8270
8270
|
heading: 'Who a dataset is shared with',
|
|
8271
8271
|
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.
|
|
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. 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
8273
|
},
|
|
8274
8274
|
{
|
|
8275
8275
|
path: '/content-and-data/datasets/overview',
|
|
@@ -8360,7 +8360,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
8360
8360
|
title: 'Events Calendar',
|
|
8361
8361
|
heading: 'Ask Aglyn AI',
|
|
8362
8362
|
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
|
|
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 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
8364
|
},
|
|
8365
8365
|
{
|
|
8366
8366
|
path: '/content-and-data/events/overview',
|
|
@@ -8451,7 +8451,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
8451
8451
|
title: 'Forms & Lead Capture',
|
|
8452
8452
|
heading: 'Switch Forms off for one site',
|
|
8453
8453
|
anchor: '#switch-forms-off-for-one-site',
|
|
8454
|
-
text: 'Forms is on for every site in a workspace. A site
|
|
8454
|
+
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
8455
|
},
|
|
8456
8456
|
{
|
|
8457
8457
|
path: '/content-and-data/forms/overview',
|
|
@@ -8500,7 +8500,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
8500
8500
|
title: 'Media Library & CDN',
|
|
8501
8501
|
heading: 'Who an asset is shared with',
|
|
8502
8502
|
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.
|
|
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. 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
8504
|
},
|
|
8505
8505
|
{
|
|
8506
8506
|
path: '/content-and-data/media/overview',
|
|
@@ -8801,7 +8801,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
8801
8801
|
title: 'Build your first plugin',
|
|
8802
8802
|
heading: '6. Install, enable, load',
|
|
8803
8803
|
anchor: '#6-install-enable-load',
|
|
8804
|
-
text: 'A
|
|
8804
|
+
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
8805
|
},
|
|
8806
8806
|
{
|
|
8807
8807
|
path: '/developers/plugins/guides/first-plugin',
|
|
@@ -9074,7 +9074,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
9074
9074
|
title: 'Plugins & Marketplace',
|
|
9075
9075
|
heading: 'How plugins run',
|
|
9076
9076
|
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
|
|
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 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
9078
|
},
|
|
9079
9079
|
{
|
|
9080
9080
|
path: '/developers/plugins/overview',
|
|
@@ -9165,7 +9165,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
9165
9165
|
title: 'Publisher handbook',
|
|
9166
9166
|
heading: 'Before your first publish',
|
|
9167
9167
|
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.'
|
|
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.\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
9169
|
},
|
|
9170
9170
|
{
|
|
9171
9171
|
path: '/developers/plugins/publishing/publisher-handbook',
|
|
@@ -9207,7 +9207,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
9207
9207
|
title: 'Publisher handbook',
|
|
9208
9208
|
heading: 'Authoring your listing',
|
|
9209
9209
|
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.\
|
|
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.\nEdit'
|
|
9211
9211
|
},
|
|
9212
9212
|
{
|
|
9213
9213
|
path: '/developers/plugins/publishing/publisher-handbook',
|
|
@@ -9228,14 +9228,14 @@ export const DOCS_SECTION_INDEX = [
|
|
|
9228
9228
|
title: 'Publisher handbook',
|
|
9229
9229
|
heading: 'How installs work (the buyer side)',
|
|
9230
9230
|
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.\
|
|
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.\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
9232
|
},
|
|
9233
9233
|
{
|
|
9234
9234
|
path: '/developers/plugins/publishing/publisher-handbook',
|
|
9235
9235
|
title: 'Publisher handbook',
|
|
9236
9236
|
heading: 'Getting paid',
|
|
9237
9237
|
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
|
|
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.\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
9239
|
},
|
|
9240
9240
|
{
|
|
9241
9241
|
path: '/developers/plugins/reference/extension-points',
|
|
@@ -9340,14 +9340,14 @@ export const DOCS_SECTION_INDEX = [
|
|
|
9340
9340
|
title: 'Plugin configuration',
|
|
9341
9341
|
heading: 'The three layers',
|
|
9342
9342
|
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} |
|
|
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} | 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
9344
|
},
|
|
9345
9345
|
{
|
|
9346
9346
|
path: '/developers/plugins/reference/plugin-config',
|
|
9347
9347
|
title: 'Plugin configuration',
|
|
9348
9348
|
heading: 'Declare a schema',
|
|
9349
9349
|
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
|
|
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 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
9351
|
},
|
|
9352
9352
|
{
|
|
9353
9353
|
path: '/developers/plugins/reference/plugin-config',
|
|
@@ -9368,7 +9368,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
9368
9368
|
title: 'Plugin configuration',
|
|
9369
9369
|
heading: 'What the console renders',
|
|
9370
9370
|
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
|
|
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 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
9372
|
},
|
|
9373
9373
|
{
|
|
9374
9374
|
path: '/developers/plugins/reference/plugin-config',
|
|
@@ -9608,6 +9608,13 @@ export const DOCS_SECTION_INDEX = [
|
|
|
9608
9608
|
anchor: '#before-a-closure--plugin-closure-notices',
|
|
9609
9609
|
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
9610
|
},
|
|
9611
|
+
{
|
|
9612
|
+
path: '/developers/plugins/reference/plugin-manager-api',
|
|
9613
|
+
title: 'Plugin-manager API reference',
|
|
9614
|
+
heading: 'Before a person erasure — `plugin-person-erasure-notes`',
|
|
9615
|
+
anchor: '#before-a-person-erasure--plugin-person-erasure-notes',
|
|
9616
|
+
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.'
|
|
9617
|
+
},
|
|
9611
9618
|
{
|
|
9612
9619
|
path: '/developers/plugins/reference/plugin-manager-api',
|
|
9613
9620
|
title: 'Plugin-manager API reference',
|
|
@@ -9641,7 +9648,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
9641
9648
|
title: 'Plugin-manager API reference',
|
|
9642
9649
|
heading: 'Contact capture — `plugin-contact-capture` (`/server`)',
|
|
9643
9650
|
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. |\
|
|
9651
|
+
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
9652
|
},
|
|
9646
9653
|
{
|
|
9647
9654
|
path: '/developers/plugins/reference/plugin-manager-api',
|
|
@@ -10523,7 +10530,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
10523
10530
|
title: 'The console tour',
|
|
10524
10531
|
heading: 'Primary navigation',
|
|
10525
10532
|
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\'
|
|
10533
|
+
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
10534
|
},
|
|
10528
10535
|
{
|
|
10529
10536
|
path: '/getting-started/console-tour',
|
|
@@ -10537,7 +10544,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
10537
10544
|
title: 'The console tour',
|
|
10538
10545
|
heading: 'The Sites list',
|
|
10539
10546
|
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.
|
|
10547
|
+
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
10548
|
},
|
|
10542
10549
|
{
|
|
10543
10550
|
path: '/getting-started/console-tour',
|
|
@@ -10600,7 +10607,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
10600
10607
|
title: 'Create a site',
|
|
10601
10608
|
heading: 'Site Admin',
|
|
10602
10609
|
anchor: '#site-admin',
|
|
10603
|
-
text: 'Site Admin holds the controls
|
|
10610
|
+
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
10611
|
},
|
|
10605
10612
|
{
|
|
10606
10613
|
path: '/getting-started/create-a-site',
|
|
@@ -10971,7 +10978,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
10971
10978
|
title: 'Install your first marketplace item',
|
|
10972
10979
|
heading: 'Manage your plugins',
|
|
10973
10980
|
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-
|
|
10981
|
+
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
10982
|
},
|
|
10976
10983
|
{
|
|
10977
10984
|
path: '/guides/install-your-first-plugin',
|
|
@@ -12602,7 +12609,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
12602
12609
|
title: 'Downgrading, canceling & your data',
|
|
12603
12610
|
heading: 'Deleting a single site',
|
|
12604
12611
|
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.
|
|
12612
|
+
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
12613
|
},
|
|
12607
12614
|
{
|
|
12608
12615
|
path: '/workspace-and-billing/billing-and-plans/downgrading-and-canceling',
|
|
@@ -12980,7 +12987,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
12980
12987
|
title: 'Signing In & Sessions',
|
|
12981
12988
|
heading: 'Privacy requests',
|
|
12982
12989
|
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
|
|
12990
|
+
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
12991
|
},
|
|
12985
12992
|
{
|
|
12986
12993
|
path: '/workspace-and-billing/signing-in-and-sessions',
|
|
@@ -13127,7 +13134,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
13127
13134
|
title: 'Invite teammates',
|
|
13128
13135
|
heading: 'A member\'s page',
|
|
13129
13136
|
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
|
|
13137
|
+
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
13138
|
},
|
|
13132
13139
|
{
|
|
13133
13140
|
path: '/workspace-and-billing/teams-and-roles/invite-teammates',
|
|
@@ -13197,7 +13204,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
13197
13204
|
title: 'Members-only areas',
|
|
13198
13205
|
heading: 'Manage your members',
|
|
13199
13206
|
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
|
|
13207
|
+
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
13208
|
},
|
|
13202
13209
|
{
|
|
13203
13210
|
path: '/workspace-and-billing/teams-and-roles/members-only',
|
|
@@ -13309,7 +13316,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
13309
13316
|
title: 'White-label',
|
|
13310
13317
|
heading: 'Not the same as renaming a self-hosted platform',
|
|
13311
13318
|
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 |
|
|
13319
|
+
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
13320
|
},
|
|
13314
13321
|
{
|
|
13315
13322
|
path: '/workspace-and-billing/white-label',
|