@aglyn/aglyn 1.7.0 → 1.9.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/ai-credit-blocks.d.ts +124 -0
- package/src/lib/app-utils/ai-credit-blocks.js +122 -0
- package/src/lib/app-utils/ai-credit-blocks.js.map +1 -0
- package/src/lib/app-utils/bundle-intent.d.ts +17 -51
- package/src/lib/app-utils/bundle-intent.js +30 -74
- package/src/lib/app-utils/bundle-intent.js.map +1 -1
- package/src/lib/app-utils/contacts.d.ts +4 -1
- package/src/lib/app-utils/contacts.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 +1 -1
- package/src/lib/app-utils/docs-help.generated.js +1 -1
- package/src/lib/app-utils/docs-help.generated.js.map +1 -1
- package/src/lib/app-utils/docs-index.generated.js +97 -97
- package/src/lib/app-utils/docs-index.generated.js.map +1 -1
- package/src/lib/app-utils/error-beacon.d.ts +25 -1
- package/src/lib/app-utils/error-beacon.js +55 -4
- package/src/lib/app-utils/error-beacon.js.map +1 -1
- package/src/lib/app-utils/foreign-script.d.ts +1 -1
- package/src/lib/app-utils/foreign-script.js +1 -1
- package/src/lib/app-utils/foreign-script.js.map +1 -1
- package/src/lib/app-utils/margin-utilization.js +6 -5
- package/src/lib/app-utils/margin-utilization.js.map +1 -1
- package/src/lib/app-utils/onboarding-deep-link.d.ts +10 -11
- package/src/lib/app-utils/onboarding-deep-link.js +37 -32
- package/src/lib/app-utils/onboarding-deep-link.js.map +1 -1
- package/src/lib/app-utils/operator-alerts.js +17 -0
- package/src/lib/app-utils/operator-alerts.js.map +1 -1
- package/src/lib/app-utils/plan-entitlements.d.ts +142 -150
- package/src/lib/app-utils/plan-entitlements.js +202 -201
- package/src/lib/app-utils/plan-entitlements.js.map +1 -1
- package/src/lib/app-utils/release-flags.d.ts +6 -4
- package/src/lib/app-utils/release-flags.js +8 -9
- package/src/lib/app-utils/release-flags.js.map +1 -1
- package/src/lib/app-utils/server.d.ts +1 -0
- package/src/lib/app-utils/server.js +3 -0
- package/src/lib/app-utils/server.js.map +1 -1
- package/src/lib/app-utils/site-interactions.d.ts +1 -1
- package/src/lib/app-utils/site-interactions.js +2 -2
- package/src/lib/app-utils/site-interactions.js.map +1 -1
- package/src/lib/app-utils/transactional-email-ceiling.d.ts +119 -0
- package/src/lib/app-utils/transactional-email-ceiling.js +134 -0
- package/src/lib/app-utils/transactional-email-ceiling.js.map +1 -0
- package/src/lib/app-utils/upgrade-proposal.d.ts +17 -7
- package/src/lib/app-utils/upgrade-proposal.js +20 -13
- package/src/lib/app-utils/upgrade-proposal.js.map +1 -1
- package/src/lib/foundation/definitions/org-billing.types.d.ts +4 -29
- package/src/lib/foundation/definitions/org-billing.types.js.map +1 -1
- package/src/lib/foundation/definitions/organization.types.d.ts +1 -3
- package/src/lib/foundation/definitions/organization.types.js.map +1 -1
- package/src/lib/foundation/index.d.ts +1 -1
- package/src/lib/foundation/index.js.map +1 -1
- package/src/lib/plugin-manager/first-party-plugins.generated.d.ts +0 -6
- package/src/lib/plugin-manager/first-party-plugins.generated.js +9 -55
- package/src/lib/plugin-manager/first-party-plugins.generated.js.map +1 -1
- package/src/lib/plugin-manager/plugin-usage-axes.d.ts +14 -0
- package/src/lib/plugin-manager/plugin-usage-axes.js.map +1 -1
- package/src/lib/plugin-manager/video-embed-provider.d.ts +29 -0
- package/src/lib/plugin-manager/video-embed-provider.js +26 -7
- package/src/lib/plugin-manager/video-embed-provider.js.map +1 -1
- package/src/lib/plugin-manager/video-embed-providers.generated.d.ts +11 -0
- package/src/lib/plugin-manager/video-embed-providers.generated.js +161 -0
- package/src/lib/plugin-manager/video-embed-providers.generated.js.map +1 -0
|
@@ -58,7 +58,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
58
58
|
title: 'A/B tests by AI: write variants, read the result',
|
|
59
59
|
heading: 'Who can use it',
|
|
60
60
|
anchor: '#who-can-use-it',
|
|
61
|
-
text: 'A/B testing is a plan feature of its own: it starts at the
|
|
61
|
+
text: 'A/B testing is a plan feature of its own: it starts at the Pro plan and is not included below it. Where a workspace does not have it, the Experiments card offers an upgrade note in place of the editor and the list — so there is no experiment to open, and neither AI card has anywhere to appear.\nAbove that, both cards need what every generative surface needs: AI generation open on your workspace and the Generate with AI permission on your role — see Custom roles & permissions. Where either is missing the card is simply absent rather than shown and disabled, so an experiment editor looks as it always did.\nBoth cards draw on your workspace\'s AI credits like any other AI request, and the same allotments and caps apply.'
|
|
62
62
|
},
|
|
63
63
|
{
|
|
64
64
|
path: '/ai/ab-tests-with-ai',
|
|
@@ -142,7 +142,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
142
142
|
title: 'AI allotments, usage and model choice',
|
|
143
143
|
heading: 'Allotments',
|
|
144
144
|
anchor: '#allotments',
|
|
145
|
-
text: 'An allotment is a number of credits a month, counted from the first of the month (UTC). It can be set on:\n- A team member — it counts what they draw on every site.\n- A site collaborator, on one site — it counts what they draw on that site.\n- A whole site — it counts what everyone draws on that site, together. An agency can give each client site its own share, so one site running out never touches another.\nWhen more than one applies to a request — a collaborator\'s own allotment and their site\'s — each one is checked, and the tightest is the one you see.\nHard or soft {#hard-or-soft}\n- Hard stops AI requests once the allotment is used for the month. The message says who can raise it.\n- Soft keeps requests working, and notifies the person and the workspace\'s owners and admins — in the console and by email — when the month passes 75%, 80% and 90%, and again at 100%: each step once a month, and only the highest one reached.\nAn allotment is checked against what was drawn before a request, the same way the workspace\'s own credits are, so a request that starts under the line can finish a little past it. The next request is the one a hard allotment stops.\nThe workspace\'s credits still come first {#the-pool-comes-first}\nAn allotment is a share of the pool, never an addition to it. The workspace\'s own limits — its included credits, a stop at the included band, an overage ceiling — are checked first. An allotment larger than the pool is allowed; the pool simply stops first.\nLimiting models {#limiting-models}\nAn allotment can also carry a list of models. The person or site then runs only on those models, including when Auto chooses. On
|
|
145
|
+
text: 'An allotment is a number of credits a month, counted from the first of the month (UTC). It can be set on:\n- A team member — it counts what they draw on every site.\n- A site collaborator, on one site — it counts what they draw on that site.\n- A whole site — it counts what everyone draws on that site, together. An agency can give each client site its own share, so one site running out never touches another.\nWhen more than one applies to a request — a collaborator\'s own allotment and their site\'s — each one is checked, and the tightest is the one you see.\nHard or soft {#hard-or-soft}\n- Hard stops AI requests once the allotment is used for the month. The message says who can raise it.\n- Soft keeps requests working, and notifies the person and the workspace\'s owners and admins — in the console and by email — when the month passes 75%, 80% and 90%, and again at 100%: each step once a month, and only the highest one reached.\nAn allotment is checked against what was drawn before a request, the same way the workspace\'s own credits are, so a request that starts under the line can finish a little past it. The next request is the one a hard allotment stops.\nThe workspace\'s credits still come first {#the-pool-comes-first}\nAn allotment is a share of the pool, never an addition to it. The workspace\'s own limits — its included credits, a stop at the included band, an overage ceiling — are checked first. An allotment larger than the pool is allowed; the pool simply stops first.\nLimiting models {#limiting-models}\nAn allotment can also carry a list of models. The person or site then runs only on those models, including when Auto chooses. On the Custom plan, the organization can restrict the models everyone uses the same way.'
|
|
146
146
|
},
|
|
147
147
|
{
|
|
148
148
|
path: '/ai/ai-allotments',
|
|
@@ -184,7 +184,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
184
184
|
title: 'AI credits',
|
|
185
185
|
heading: 'Credits each month',
|
|
186
186
|
anchor: '#monthly-credits',
|
|
187
|
-
text: 'Each plan includes credits every month, and they pay for all of Aglyn AI: answers, copy, and building pages, forms, emails, products and the rest.
|
|
187
|
+
text: 'Each plan includes credits every month, and they pay for all of Aglyn AI: answers, copy, and building pages, forms, emails, products and the rest. Blocks of AI credits add more on top:\n| Plan | Included each month |\n| Free | 300 |\n| Starter | 750 |\n| Pro | 2,750 |\n| Custom | Set in your agreement |\nThe pool resets on the first of each month (UTC). Credits you did not use do not carry over.\nOn a paid plan, credits past the pool are billed per 1,000 at your plan\'s rate, unless you turn on the stop at the included band in Billing. See Billing & Plans.'
|
|
188
188
|
},
|
|
189
189
|
{
|
|
190
190
|
path: '/ai/ai-credits',
|
|
@@ -196,9 +196,9 @@ export const DOCS_SECTION_INDEX = [
|
|
|
196
196
|
{
|
|
197
197
|
path: '/ai/ai-credits',
|
|
198
198
|
title: 'AI credits',
|
|
199
|
-
heading: '
|
|
199
|
+
heading: 'More AI credits',
|
|
200
200
|
anchor: '#the-aglyn-ai-add-on',
|
|
201
|
-
text: 'Need more than your plan includes?
|
|
201
|
+
text: 'Need more than your plan includes? The AI credits add-on adds credits to the same pool every month, on top of what your plan includes, in blocks of 5,000 credits. Choose how many blocks you want, up to 30 (150,000 extra credits a month). Any paid plan can add blocks, and changing your plan keeps them.\nBlocks are bought for the whole workspace. Free cannot add them, and on Custom more AI is part of your agreement. The price of a block is on aglyn.com/pricing and in Billing before you confirm. Adding blocks is charged now, for the rest of the period; removing blocks takes effect at the end of the period you have paid for. See Add-ons.\nUntil November 2026 extra credits were sold as six named tiers (Spark, Boost, Plus, Max, Ultra and Studio). Those tiers are retired; blocks replace them.'
|
|
202
202
|
},
|
|
203
203
|
{
|
|
204
204
|
path: '/ai/ai-credits',
|
|
@@ -240,7 +240,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
240
240
|
title: 'AI credits',
|
|
241
241
|
heading: 'See your credits',
|
|
242
242
|
anchor: '#see-your-credits',
|
|
243
|
-
text: '- Billing → Usage → AI credits shows the credits drawn this month against the pool, and how many of them your
|
|
243
|
+
text: '- Billing → Usage → AI credits shows the credits drawn this month against the pool, and how many of them your blocks add. A workspace whose plan includes no AI credits sees that said here instead, with See plans linking to Billing.\n- Who is generating what, on the same page, lists each member\'s credits by month. See Billing & Plans.\n- The usage line in the assistant and the AI dialogs shows your own credits, the workspace\'s and your last request. See Your usage while you work.\n- A site\'s AI jobs page shows what each job used. See AI jobs and activity.\nTo give one member or one site its own monthly share, see AI allotments.'
|
|
244
244
|
},
|
|
245
245
|
{
|
|
246
246
|
path: '/ai/ai-credits',
|
|
@@ -548,35 +548,35 @@ export const DOCS_SECTION_INDEX = [
|
|
|
548
548
|
title: 'Bring my site',
|
|
549
549
|
heading: 'Read my site',
|
|
550
550
|
anchor: '#read-my-site',
|
|
551
|
-
text: 'Choose Read my site. Aglyn then:\n- creates your new site, with nothing on it and nothing published;\n- reads your current site as AglynBot, starting with its robots.txt file and its sitemap, then your home page, then every other page, and only on your own domain. Your current site is not changed.\nAglyn reads up to 400 pages. A link to a file, such as a download or a PDF, is not a page, so it is never read as one and never counts toward that number.\nReading uses no AI credits.\nWhat is read. For each page Aglyn reads its words and how your site lays them out: its sections and their background colors, its columns, its cards and the icons on them, its numbered steps, figures, questions and answers, quotes, logo strips, plan cards with their badge, price and button, plan rows, tables and tabs, its pictures where they sit, your forms with their fields and their button, and which links your site shows as buttons. From your home page it also reads your menu, with each dropdown and its entries, the buttons beside it, and your footer\'s columns, profiles and copyright line, plus your site\'s fonts and colors. Your new pages are built from this, with every word as you wrote it.\nYour home page comes first. If AglynBot cannot read your home page, nothing is planned and no AI credits are used. The import waits and says why:\n- AglynBot was turned away means your site\'s bot protection or firewall refused it. See When your site turns AglynBot away.\n- Your home page could not be read means your home page answered with an error or did not answer. Check that your site is up, then choose Check again.\nCheck again reads your site again, and uses no AI credits either.\nWhen it is done, Your site is read shows:\n- what was
|
|
551
|
+
text: 'Choose Read my site. Aglyn then:\n- creates your new site, with nothing on it and nothing published;\n- reads your current site as AglynBot, starting with its robots.txt file and its sitemap, then your home page, then every other page, and only on your own domain. Your current site is not changed.\nAglyn reads up to 400 pages. A link to a file, such as a download or a PDF, is not a page, so it is never read as one and never counts toward that number.\nReading uses no AI credits.\nWhat is read. For each page Aglyn reads its words and how your site lays them out: its sections and their background colors, its columns, its cards and the icons on them, its numbered steps, figures, questions and answers, quotes, logo strips, plan cards with their badge, price and button, plan rows, tables and tabs, its pictures where they sit, its videos (a film on your page, with its poster, title and description), your forms with their fields and their button, and which links your site shows as buttons. From your home page it also reads your menu, with each dropdown and its entries, the buttons beside it, and your footer\'s columns, profiles and copyright line, plus your site\'s fonts and colors. Your new pages are built from this, with every word as you wrote it.\nYour home page comes first. If AglynBot cannot read your home page, nothing is planned and no AI credits are used. The import waits and says why:\n- AglynBot was turned away means your site\'s bot protection or firewall refused it. See When your site turns AglynBot away.\n- Your home page could not be read means your home page answered with an error or did not answer. Check that your site is up, then choose Check again.\nCheck again reads your site again, and uses no AI credits either.\nWhen it is done, Your site is read shows:\n- what was fou'
|
|
552
552
|
},
|
|
553
553
|
{
|
|
554
554
|
path: '/ai/bring-my-site',
|
|
555
555
|
title: 'Bring my site',
|
|
556
556
|
heading: 'Waves',
|
|
557
557
|
anchor: '#waves',
|
|
558
|
-
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 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, your pages\' background color, the rounding of your buttons, and your own font when Google Fonts has it, or a font in the same style when it does not. Colors are kept readable, so a color too light for white words is used a shade deeper. If you already chose a theme for the new site, it is kept.\n- Your header and footer come in with the first wave, as your current site shows them: your logo, your name, or both; your menu, each dropdown as a Dropdown Menu or a Mega Menu with its entries, their icons and the line under each; and your buttons, such as Sign in or Start free, going where they go now.
|
|
558
|
+
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 your current site\'s look, on one of Aglyn\'s built-in themes: your buttons\' color as its main color and your links\' color beside it, the color of the small labels above your headings as its third color, your pages\' background color, the rounding of your buttons, and your own font when Google Fonts has it, or a font in the same style when it does not. Colors are kept readable, so a color too light for white words is used a shade deeper. If you already chose a theme for the new site, it is kept.\n- Your header and footer come in with the first wave, as your current site shows them: your logo, your name, or both; your menu, each dropdown as a Dropdown Menu or a Mega Menu with its entries, their icons and the line under each; and your buttons, such as Sign in or Start free, going where they go now. A large dropdown keeps its columns in the same order, side by side and as wide as yours, with each column\'s heading and words, its featured picture, its light or dark box, and the colored tile behind each icon. Every label stays on one line, and on a screen too narrow for the whole menu it becomes a menu button that opens every menu and button.\n- Your menus open the way they do now. A menu that opens when you point at it opens the same way on a computer, and clicking its name opens that page, as it does on your current site. A menu name with no page of its own opens its menu on a click. A menu that only opens on a click stays that way. In the menu on a phone, tap a menu\'s name to open or close it; every entry and every word of its panel is there. Each menu\'s panel starts hidden until it is shown: select it in the Besigner to work on'
|
|
559
559
|
},
|
|
560
560
|
{
|
|
561
561
|
path: '/ai/bring-my-site',
|
|
562
562
|
title: 'Bring my site',
|
|
563
563
|
heading: 'Review a wave',
|
|
564
564
|
anchor: '#review-a-wave',
|
|
565
|
-
text: 'When a wave is in, its page says so, for example Main pages is in your site\'s preview, and shows:\n- every page of the wave, with Open draft, its old and new address, and Old page to compare it with the page on your current site;\n- how many of the page\'s photos came in, for example 3 of 5 photos, with how many were already in your media library and how many could not be brought in;\n- a page that could not be brought in, with the reason;\n- a page whose form was rebuilt, with the form\'s name;\n- how many AI credits the wave used.\nIf your site started in preview, each wave\'s pages are published into the preview as the wave comes in. You, your team and Aglyn support can open the site and see them at their addresses, home at your site\'s address. Visitors still see Coming soon. To make the site public, switch Preview off in Admin → Error pages, or choose Make it public on the banner that says your site is in preview.\nIf your site is not in preview, every page is a draft: nothing is published until you publish it.\nOpen your draft pages opens the site\'s Pages list. When you are ready for more, choose the next wave\'s Start button. Nothing starts the next wave except you, unless you chose Start every remaining wave.\nCancel stops the import. The pages already brought in stay where they are: in the preview, or as drafts. Under Every wave, a wave that was running reads stopped, and a wave that had not started reads not started.'
|
|
565
|
+
text: 'When a wave is in, its page says so, for example Main pages is in your site\'s preview, and shows:\n- every page of the wave, with Open draft, its old and new address, and Old page to compare it with the page on your current site;\n- how many of the page\'s photos came in, for example 3 of 5 photos, with how many were already in your media library and how many could not be brought in;\n- a page that could not be brought in, with the reason;\n- a page whose form was rebuilt, with the form\'s name;\n- a page with a video your old site serves itself, which plays from your old site\'s address, and a page with a video that was left out because it had no poster picture;\n- how many AI credits the wave used.\nIf your site started in preview, each wave\'s pages are published into the preview as the wave comes in. You, your team and Aglyn support can open the site and see them at their addresses, home at your site\'s address. Visitors still see Coming soon. To make the site public, switch Preview off in Admin → Error pages, or choose Make it public on the banner that says your site is in preview.\nIf your site is not in preview, every page is a draft: nothing is published until you publish it.\nOpen your draft pages, or Open your pages when your site is in preview, opens the site\'s Pages list. When you are ready for more, choose the next wave\'s Start button. Nothing starts the next wave except you, unless you chose Start every remaining wave.\nCancel stops the import. The pages already brought in stay where they are: in the preview, or as drafts. Under Every wave, a wave that was running reads stopped, and a wave that had not started reads not started.'
|
|
566
566
|
},
|
|
567
567
|
{
|
|
568
568
|
path: '/ai/bring-my-site',
|
|
569
569
|
title: 'Bring my site',
|
|
570
|
-
heading: 'Photos',
|
|
570
|
+
heading: 'Photos and videos',
|
|
571
571
|
anchor: '#photos',
|
|
572
|
-
text: 'A page\'s photos are copied into your new site\'s media library and placed on that page: on a page copied as it is, each one where your page shows it. The same photo is stored only once, however many pages show it.\nYour logo is copied once, for your header. If it is a drawing (an SVG file), it is saved as a picture. Your home page\'s share image, the one shown when your site is linked, becomes your new site\'s share image unless you already chose one.'
|
|
572
|
+
text: 'A page\'s photos are copied into your new site\'s media library and placed on that page: on a page copied as it is, each one where your page shows it. The same photo is stored only once, however many pages show it.\nA video on your page is placed with the Video element, where your page shows it, and plays from where it plays now:\n- A video on Wistia, YouTube or Vimeo plays in that host\'s player, which loads only when a visitor presses play.\n- A video your old site serves itself plays from your old site\'s address. Its page\'s row says so. To move it, pick the video from your media library on its Video element. So it can play on your new site, the address it plays from is added to Approved media hosts in Admin → Security. Every host on that list can see the IP address of each visitor whose browser plays the video from it.\nIts poster picture, the still a visitor presses, is copied into your media library like any photo, and its title, description, date and running time come with it when your page gives them. A button on your page that plays the video, such as Watch the film, plays it on the new page too. A video on another host is shown as its poster picture, linking to where it plays. A video your page shows without a poster picture is left out, and its page\'s row says so: add it with the Video element and pick a poster for it. A video that plays by itself behind a section\'s words is shown as its poster picture there.\nYour logo is copied once, for your header. If it is a drawing (an SVG file), it is saved as a picture. Your home page\'s share image, the one shown when your site is linked, becomes your new site\'s share image unless you already chose one.'
|
|
573
573
|
},
|
|
574
574
|
{
|
|
575
575
|
path: '/ai/bring-my-site',
|
|
576
576
|
title: 'Bring my site',
|
|
577
577
|
heading: 'What is never brought in',
|
|
578
578
|
anchor: '#never-brought-in',
|
|
579
|
-
text: '- Sign-in pages. A page that asks for a password is left out, and so is a page AglynBot is asked not to read by robots.txt.\n- Code. Scripts and embedded
|
|
579
|
+
text: '- Sign-in pages. A page that asks for a password is left out, and so is a page AglynBot is asked not to read by robots.txt.\n- Code. Scripts are never brought in. An embedded video is placed as a video, and any other embedded frame is left out.\n- Forms that ask for a password or a card number. These are left out. Every other form on your page is rebuilt as a form of your new site, with the same fields, required marks and button, where your page had it. What visitors send lands in your Inbox, a form that asks for an email also asks for marketing consent, and rebuilding a form uses no AI credits. A form your new site already has is placed instead of a second copy. If your plan has no room for another form, the page comes in without it and its row says so. A form can\'t take a file here, so a file upload field is left out and the page\'s row names it.\n- Other websites. Only pages on your own domain are read. A page that sends visitors to another website is left out.'
|
|
580
580
|
},
|
|
581
581
|
{
|
|
582
582
|
path: '/ai/bring-my-site',
|
|
@@ -793,7 +793,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
793
793
|
title: 'Create with AI on every list',
|
|
794
794
|
heading: 'On every plan',
|
|
795
795
|
anchor: '#without-the-add-on',
|
|
796
|
-
text: 'On every paid plan, Create with AI runs on the AI credits your plan includes each month; nothing else needs to be bought.
|
|
796
|
+
text: 'On every paid plan, Create with AI runs on the AI credits your plan includes each month; nothing else needs to be bought. Blocks of AI credits add more on top when you need them, and an owner or admin adds them in Billing.\nA Free workspace\'s buttons work from the 300 AI credits it gets each month.\nIf Create with AI is switched off for your workspace, the button is still there and opens a short window saying what it would make:\n- an owner or admin sees Add Aglyn AI, which opens Billing to choose a tier, or Not now;\n- anyone else is asked to have a workspace owner or admin choose one.'
|
|
797
797
|
},
|
|
798
798
|
{
|
|
799
799
|
path: '/ai/create-with-ai',
|
|
@@ -1197,16 +1197,16 @@ export const DOCS_SECTION_INDEX = [
|
|
|
1197
1197
|
{
|
|
1198
1198
|
path: '/ai/overview',
|
|
1199
1199
|
title: 'Aglyn AI: the AI website builder',
|
|
1200
|
-
heading: 'Plans and
|
|
1200
|
+
heading: 'Plans and AI credits',
|
|
1201
1201
|
anchor: '#the-add-on',
|
|
1202
|
-
text: 'Aglyn AI comes with every plan. Each plan includes AI credits every month, and they pay for everything above: the assistant\'s answers and building for you, on every site in the workspace, for every member who has the permission to generate.\n-
|
|
1202
|
+
text: 'Aglyn AI comes with every plan. Each plan includes AI credits every month, and they pay for everything above: the assistant\'s answers and building for you, on every site in the workspace, for every member who has the permission to generate.\n- The AI credits add-on adds more credits on top of your plan\'s, in blocks of 5,000 a month, bought for the workspace, not per seat and not per site. Any paid plan can add up to 30 blocks.\n- Custom workspaces carry their AI in their agreement.\n- Free workspaces cannot add blocks. A Free workspace gets a small monthly allowance of credits instead, enough to try generating, and it stops at that allowance rather than billing you.\nWhat a block costs is on aglyn.com/pricing and in Billing before you confirm — see AI credits and Add-ons.'
|
|
1203
1203
|
},
|
|
1204
1204
|
{
|
|
1205
1205
|
path: '/ai/overview',
|
|
1206
1206
|
title: 'Aglyn AI: the AI website builder',
|
|
1207
1207
|
heading: 'Credits and caps',
|
|
1208
1208
|
anchor: '#credits-and-caps',
|
|
1209
|
-
text: 'Everything AI does — an answer from the assistant, a rewrite, a generated section, a whole site — is metered in AI credits from one workspace pool. There is no second meter per feature.\nWhat a request costs is not fixed: a rewrite of one headline is small, a site scaffold is large, and a job tells you its estimate before you confirm it. The shape of the limits is the part worth knowing:\n- An included band each month, from your plan plus
|
|
1209
|
+
text: 'Everything AI does — an answer from the assistant, a rewrite, a generated section, a whole site — is metered in AI credits from one workspace pool. There is no second meter per feature.\nWhat a request costs is not fixed: a rewrite of one headline is small, a site scaffold is large, and a job tells you its estimate before you confirm it. The shape of the limits is the part worth knowing:\n- An included band each month, from your plan plus any blocks you add, reset monthly.\n- Past the band, a paid workspace keeps working and the extra credits bill on the monthly invoice at your plan\'s rate. A switch under Billing → Usage stops AI at the included band instead; it is off unless you choose it.\n- A ceiling you set, so overage can never pass a figure you are comfortable with.\n- Alerts on the way there, to the workspace\'s owners and admins.\n- Allotments, which give one member, one site collaborator or one whole site its own monthly share of the pool, hard or soft — see AI allotments, usage and model choice. An agency can give each client site its own share so one site running out never touches another.\n- A short-term rate limit per person, which smooths bursts rather than capping your month. If you see "Too many AI requests", wait a moment and try again.\nA request that fails before the model answers does not spend credits. An answer that was generated and then refused for breaking a building rule does — the rules page says which, and why.\nWhat each plan includes, what typical jobs cost and when credits are given back are on AI credits. The billing figures behind all of that are on Billing & Plans, and your own usage is on Billing → Usage.'
|
|
1210
1210
|
},
|
|
1211
1211
|
{
|
|
1212
1212
|
path: '/ai/overview',
|
|
@@ -1220,7 +1220,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
1220
1220
|
title: 'Aglyn AI: the AI website builder',
|
|
1221
1221
|
heading: 'Switch AI off for one site',
|
|
1222
1222
|
anchor: '#switch-ai-off-for-one-site',
|
|
1223
|
-
text: 'AI is on for every site in a workspace. A site admin can switch it off for one site on that site\'s Admin → Plugins → AI page, and the page says, beside the switch, what switching it off stops and what it leaves running.\nWith AI off for a site:\n- the assistant, Create with AI on the Pages, Templates, Layouts, Forms, Components and Media pages, the SEO and theme cards, the editor\'s Rewrite with AI, Generate a section with AI and Make a reusable component with AI controls, and the AI columns on the site\'s collaborators card are gone from that site;\n- every AI request made for the site is refused with AI is switched off for this site., including one sent from a tab that was open before the switch;\n- an AI job already queued for the site stops with the same sentence, and spends no credits. A job that stopped does not restart when AI is switched back on.\nSwitching AI off for a site does not stop the workspace\'s AI
|
|
1223
|
+
text: 'AI is on for every site in a workspace. A site admin can switch it off for one site on that site\'s Admin → Plugins → AI page, and the page says, beside the switch, what switching it off stops and what it leaves running.\nWith AI off for a site:\n- the assistant, Create with AI on the Pages, Templates, Layouts, Forms, Components and Media pages, the SEO and theme cards, the editor\'s Rewrite with AI, Generate a section with AI and Make a reusable component with AI controls, and the AI columns on the site\'s collaborators card are gone from that site;\n- every AI request made for the site is refused with AI is switched off for this site., including one sent from a tab that was open before the switch;\n- an AI job already queued for the site stops with the same sentence, and spends no credits. A job that stopped does not restart when AI is switched back on.\nSwitching AI off for a site does not stop the workspace\'s credits, its blocks of AI credits, allotments or overage billing. AI keeps working on the workspace\'s other sites and on workspace pages such as Billing, and an agency batch still builds the sites in it that have AI on.'
|
|
1224
1224
|
},
|
|
1225
1225
|
{
|
|
1226
1226
|
path: '/ai/overview',
|
|
@@ -1983,7 +1983,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
1983
1983
|
title: 'Interactions & custom HTML',
|
|
1984
1984
|
heading: 'Plan availability',
|
|
1985
1985
|
anchor: '#plan-availability',
|
|
1986
|
-
text: 'Interactions come in two tiers, and the field editor labels the steps that need a higher plan:\n- Basic interactions — every plan, including Free. Opening and closing menus and drawers, showing and hiding elements, toggling classes, scrolling to an element, playing a video, sticky nav, navigation, and site alerts are pure client-side DOM behavior with no server cost. They run everywhere and are never metered — a hover-to-open menu is not a paid feature.\n- The automations engine — Pro+, metered. Steps that reach the server or a data pipeline — overlays, analytics events, custom JS
|
|
1986
|
+
text: 'Interactions come in two tiers, and the field editor labels the steps that need a higher plan:\n- Basic interactions — every plan, including Free. Opening and closing menus and drawers, showing and hiding elements, toggling classes, scrolling to an element, playing a video, sticky nav, navigation, and site alerts are pure client-side DOM behavior with no server cost. They run everywhere and are never metered — a hover-to-open menu is not a paid feature.\n- The automations engine — Pro+, metered. Steps that reach the server or a data pipeline — overlays, analytics events, custom JS, and the server steps (workflows, email, datasets, campaigns) — require the actions entitlement and count against your monthly action runs.\nOn a plan without the automations entitlement, an interaction that mixes tiers still runs its basic steps live; the Pro+ steps are simply skipped until you upgrade. See workflows & actions for the full step catalog and metering.'
|
|
1987
1987
|
},
|
|
1988
1988
|
{
|
|
1989
1989
|
path: '/building-sites/besigner/interactions-and-custom-html',
|
|
@@ -2004,7 +2004,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
2004
2004
|
title: 'Interactions & custom HTML',
|
|
2005
2005
|
heading: 'Play a video',
|
|
2006
2006
|
anchor: '#play-video-step',
|
|
2007
|
-
text: 'When clicked → Play a video does exactly what pressing a Video element\'s poster does, from a button anywhere on the page. Pick the Video as the target.\n- With Open in a lightbox on, the lightbox opens and the film plays.\n- With it off, the film plays in place of the poster.\nNothing is loaded from the video\'s host until the action runs, and a Wistia video follows the same consent rules as a press on its poster. To be sure the film is in view as it starts, put Scroll to element, picking the same Video, before it.'
|
|
2007
|
+
text: 'When clicked → Play a video does exactly what pressing a Video element\'s poster does, from a button anywhere on the page. Pick the Video as the target.\n- With Open in a lightbox on, the lightbox opens and the film plays.\n- With it off, the film plays in place of the poster.\nNothing is loaded from the video\'s host until the action runs, and a Wistia, YouTube or Vimeo video follows the same consent rules as a press on its poster. To be sure the film is in view as it starts, put Scroll to element, picking the same Video, before it.'
|
|
2008
2008
|
},
|
|
2009
2009
|
{
|
|
2010
2010
|
path: '/building-sites/besigner/interactions-and-custom-html',
|
|
@@ -2739,7 +2739,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
2739
2739
|
title: 'Video',
|
|
2740
2740
|
heading: 'Choosing the film',
|
|
2741
2741
|
anchor: '#video-source',
|
|
2742
|
-
text: 'Set a Video source with Browse media. A video from your media library arrives with a poster frame, its running time and its dimensions already filled in — you only need Poster image to override the frame the library picked.\nVideo uploads are paused New video files cannot be uploaded to the media library for now. The Video element can still use any video that is already in your library, or a video hosted on Wistia.\nPicking a video from the media library copies its dimensions onto the element, which reserves the right-shaped box before anything loads and stops the rest of the page shifting when it does. It fills in the duration too, so the only SEO fields left to write are the title, the description and the date.'
|
|
2742
|
+
text: 'Set a Video source with Browse media. A video from your media library arrives with a poster frame, its running time and its dimensions already filled in — you only need Poster image to override the frame the library picked.\nVideo uploads are paused New video files cannot be uploaded to the media library for now. The Video element can still use any video that is already in your library, or a video hosted on Wistia, YouTube or Vimeo.\nPicking a video from the media library copies its dimensions onto the element, which reserves the right-shaped box before anything loads and stops the rest of the page shifting when it does. It fills in the duration too, so the only SEO fields left to write are the title, the description and the date.'
|
|
2743
2743
|
},
|
|
2744
2744
|
{
|
|
2745
2745
|
path: '/building-sites/besigner/video',
|
|
@@ -2765,9 +2765,9 @@ export const DOCS_SECTION_INDEX = [
|
|
|
2765
2765
|
{
|
|
2766
2766
|
path: '/building-sites/besigner/video',
|
|
2767
2767
|
title: 'Video',
|
|
2768
|
-
heading: 'A video hosted on Wistia',
|
|
2768
|
+
heading: 'A video hosted on Wistia, YouTube or Vimeo',
|
|
2769
2769
|
anchor: '#video-wistia',
|
|
2770
|
-
text: 'Paste
|
|
2770
|
+
text: 'Paste the video\'s link into Video source. Each host\'s usual links work:\n- Wistia: the address of the video\'s page in your Wistia account, or its embed link.\n- YouTube: the video\'s page, a Short, a live video, its embed link, or the youtu.be link from Share.\n- Vimeo: the video\'s page, the same video in a channel, group or showcase, or its embed link. An unlisted Vimeo video does not play this way: its link carries a private part the player needs, so make the video public on Vimeo first.\nA link to a channel, a playlist or a search names no single video, so the element treats it as an ordinary link and plays nothing.\nThen pick a Poster image from your media library. The poster becomes a play button, and the host\'s player loads only when a visitor presses it, so someone who never presses play never contacts the host, unless you turn on Load the player with the page (below). The player opens in the lightbox when Open in a lightbox is on, and in place of the poster when it is off. Without a poster the element asks for one instead of loading the player.\nEach host\'s player brings its own controls. In the lightbox, Esc closes it until you move into the player; from inside the player, Shift+Tab reaches the close button. Type the running time into Duration (seconds), because a hosted video\'s link does not carry it.\nHow each host\'s player treats your visitors:\n- Wistia records a viewing only for a visitor whose analytics consent your site has on record, and plays with its tracking off for everyone else.\n- YouTube always plays in its privacy-enhanced player (youtube-nocookie.com), for every visitor.\n- Vimeo always plays with its do-not-track option on, for every visitor.\nTurn on Load the player with the page for a page whose main content is this one video, such as the entry page of '
|
|
2771
2771
|
},
|
|
2772
2772
|
{
|
|
2773
2773
|
path: '/building-sites/besigner/video',
|
|
@@ -3257,7 +3257,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
3257
3257
|
title: 'Add a locale',
|
|
3258
3258
|
heading: '',
|
|
3259
3259
|
anchor: '',
|
|
3260
|
-
text: 'Add a locale\nPublish your site in another language by adding a locale variant.\nPlan availability
|
|
3260
|
+
text: 'Add a locale\nPublish your site in another language by adding a locale variant.\nPlan availability Pro and up. This is multilingual v1.'
|
|
3261
3261
|
},
|
|
3262
3262
|
{
|
|
3263
3263
|
path: '/building-sites/multilingual/add-a-locale',
|
|
@@ -3285,7 +3285,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
3285
3285
|
title: 'Add a language switcher',
|
|
3286
3286
|
heading: '',
|
|
3287
3287
|
anchor: '',
|
|
3288
|
-
text: 'Add a language switcher\nOnce you\'ve added a locale, give visitors a language switcher so they can pick their language.\nPlan availability
|
|
3288
|
+
text: 'Add a language switcher\nOnce you\'ve added a locale, give visitors a language switcher so they can pick their language.\nPlan availability Pro and up.'
|
|
3289
3289
|
},
|
|
3290
3290
|
{
|
|
3291
3291
|
path: '/building-sites/multilingual/language-switcher',
|
|
@@ -3313,7 +3313,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
3313
3313
|
title: 'Multilingual',
|
|
3314
3314
|
heading: '',
|
|
3315
3315
|
anchor: '',
|
|
3316
|
-
text: 'Multilingual\nReach a wider audience by publishing your site in more than one language.\nPlan availability
|
|
3316
|
+
text: 'Multilingual\nReach a wider audience by publishing your site in more than one language.\nPlan availability Pro and up. Multilingual is on Pro and Custom. Every plan can set the one language its site is written in: enter a single code (for example es) in Languages and save. A second language needs Pro.'
|
|
3317
3317
|
},
|
|
3318
3318
|
{
|
|
3319
3319
|
path: '/building-sites/multilingual/overview',
|
|
@@ -3362,7 +3362,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
3362
3362
|
title: 'Translate with Weglot',
|
|
3363
3363
|
heading: '',
|
|
3364
3364
|
anchor: '',
|
|
3365
|
-
text: 'Translate with Weglot\nIf you already use Weglot, Aglyn can load it on your published pages with your own Weglot account. Weglot translates each page in the visitor\'s browser, and a language switcher lets visitors pick their language.\nPlan availability
|
|
3365
|
+
text: 'Translate with Weglot\nIf you already use Weglot, Aglyn can load it on your published pages with your own Weglot account. Weglot translates each page in the visitor\'s browser, and a language switcher lets visitors pick their language.\nPlan availability Pro and up, the same plans as Multilingual. On other plans, nothing is added to your pages.\nYou need your own Weglot account. Weglot\'s plan decides how many words and languages you can translate, and Weglot bills you for it. Aglyn charges nothing extra.'
|
|
3366
3366
|
},
|
|
3367
3367
|
{
|
|
3368
3368
|
path: '/building-sites/multilingual/weglot',
|
|
@@ -3824,7 +3824,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
3824
3824
|
title: 'Versions & scheduled publishing',
|
|
3825
3825
|
heading: 'Plan requirements',
|
|
3826
3826
|
anchor: '#plan-requirements',
|
|
3827
|
-
text: 'On a plan without a feature its buttons stay on screen, disabled, with a note naming the plan that includes it and an Upgrade button to the plans on Billing:\n- Creating versions requires Pro or above — on a lower tier New version is disabled and the Versions dialog says "Included from Pro".\n- Scheduled publishing requires
|
|
3827
|
+
text: 'On a plan without a feature its buttons stay on screen, disabled, with a note naming the plan that includes it and an Upgrade button to the plans on Billing:\n- Creating versions requires Pro or above — on a lower tier New version is disabled and the Versions dialog says "Included from Pro".\n- Scheduled publishing requires Pro or above — on a lower plan every Schedule button is disabled and says "Scheduled publishing is included from Pro."\n- A version is snapshotted from the saved document, so the editor asks you to save the canvas first rather than silently capturing (or losing) unsaved edits.'
|
|
3828
3828
|
},
|
|
3829
3829
|
{
|
|
3830
3830
|
path: '/building-sites/screens-and-layouts/versions-and-publishing',
|
|
@@ -4104,7 +4104,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
4104
4104
|
title: 'Make your site private',
|
|
4105
4105
|
heading: '',
|
|
4106
4106
|
anchor: '',
|
|
4107
|
-
text: 'Make your site private\nWant to keep your site to yourself while you build it, share it with a client before launch, or keep it to a few people for good? Aglyn doesn\'t have a single "private" switch that puts every page behind one password. Instead, pick the setting that matches who should still get in:\n| Who should see the site | Use | Where | Plan |\n| Only you and your team, while you finish it | Preview | Admin → Error pages (also offered when you create a site) | Every plan |\n| No one yet. Not visitors, not search engines, not someone with the link | Maintenance mode | Admin → Error pages | Every plan |\n| Anyone with the link, but keep it off Google | Discourage search engines | Setup → SEO → Search engines | Every plan |\n| Only people you give a password to | Password protected, page by page | The page\'s Page Access card | Every plan |\n| Only people signed in to your site | Members only, page by page | The page\'s Page Access card |
|
|
4107
|
+
text: 'Make your site private\nWant to keep your site to yourself while you build it, share it with a client before launch, or keep it to a few people for good? Aglyn doesn\'t have a single "private" switch that puts every page behind one password. Instead, pick the setting that matches who should still get in:\n| Who should see the site | Use | Where | Plan |\n| Only you and your team, while you finish it | Preview | Admin → Error pages (also offered when you create a site) | Every plan |\n| No one yet. Not visitors, not search engines, not someone with the link | Maintenance mode | Admin → Error pages | Every plan |\n| Anyone with the link, but keep it off Google | Discourage search engines | Setup → SEO → Search engines | Every plan |\n| Only people you give a password to | Password protected, page by page | The page\'s Page Access card | Every plan |\n| Only people signed in to your site | Members only, page by page | The page\'s Page Access card | Pro and up |\nHiding a page from search doesn\'t stop people opening it. Only preview, maintenance mode, a page password, and members-only actually keep visitors out.'
|
|
4108
4108
|
},
|
|
4109
4109
|
{
|
|
4110
4110
|
path: '/building-sites/site-protection/make-your-site-private',
|
|
@@ -4139,14 +4139,14 @@ export const DOCS_SECTION_INDEX = [
|
|
|
4139
4139
|
title: 'Make your site private',
|
|
4140
4140
|
heading: 'Only signed-in members',
|
|
4141
4141
|
anchor: '#only-signed-in-members',
|
|
4142
|
-
text: 'On
|
|
4142
|
+
text: 'On Pro and up, set a page\'s Visibility to Members only in the same Page Access card. Visitors must sign in to your site to view it, and stay signed in as they move between members-only pages. You\'ll need the site\'s sign-in and sign-up pages turned on first. See Members-only areas.\nKeep in mind:\n- Like passwords, this is set page by page. New pages start as Public, so set each new page as you add it.\n- Anyone who reaches your sign-up page can create a member account. Members-only keeps out people who aren\'t signed in; it doesn\'t hand-pick who joins. To remove someone, suspend them from the site\'s Users page.'
|
|
4143
4143
|
},
|
|
4144
4144
|
{
|
|
4145
4145
|
path: '/building-sites/site-protection/make-your-site-private',
|
|
4146
4146
|
title: 'Make your site private',
|
|
4147
4147
|
heading: 'Ask Aglyn AI',
|
|
4148
4148
|
anchor: '#ask-aglyn-ai',
|
|
4149
|
-
text: 'You can ask Assist to make these changes for you, such as make my site private until launch, hide the site from Google, make the pricing page members only or put the site back online. Assist shows the change on a plan card, and nothing changes until you confirm it. It\'s then saved to your live site straight away, just as if you\'d used the switch yourself, and it uses no AI credits.\n- Maintenance mode can only be turned on or off by a site admin, as in the Admin area. If you\'re an editor or author, Assist makes the rest of your request and says it left maintenance mode alone.\n- Members only is set only on the
|
|
4149
|
+
text: 'You can ask Assist to make these changes for you, such as make my site private until launch, hide the site from Google, make the pricing page members only or put the site back online. Assist shows the change on a plan card, and nothing changes until you confirm it. It\'s then saved to your live site straight away, just as if you\'d used the switch yourself, and it uses no AI credits.\n- Maintenance mode can only be turned on or off by a site admin, as in the Admin area. If you\'re an editor or author, Assist makes the rest of your request and says it left maintenance mode alone.\n- Members only is set only on the Pro plan and up. On other plans, Assist says why it left the page as it was.\n- Passwords are never set by Assist, so a password never goes into the chat. Set it in the page\'s Page Access card, as in Share it behind a password.\nAsking how, such as how do I make my site private?, gets you the steps on this page instead. Building from the chat needs AI generation on your plan; see Build from Assist chat.'
|
|
4150
4150
|
},
|
|
4151
4151
|
{
|
|
4152
4152
|
path: '/building-sites/site-protection/make-your-site-private',
|
|
@@ -4342,7 +4342,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
4342
4342
|
title: 'Build a blog',
|
|
4343
4343
|
heading: 'Build a video collection',
|
|
4344
4344
|
anchor: '#video-collection',
|
|
4345
|
-
text: 'Give every film a page of its own: a collection whose entries are articles with the film where a post\'s cover image would sit. Search engines list a video from a page that is about that video, and an entry page is exactly that.\nGive each entry its film. In the entry editor, Featured video takes a film from your media library, a video link, or a Wistia link. Picking a library film that has a captured frame also fills an empty Cover image with that frame; a cover you already chose is kept.\nSay how long it runs. Video length (seconds), under the featured video, is the film\'s running time, which a video search result can show beside it. Choosing a film from your media library fills it in from the file. For a video link or a Wistia link, type it yourself: 754 for a film that runs 12 minutes 34 seconds. Leave it blank if you don\'t know it; the page is still listed without one.\nPlace the player on the entry template. Add a Video element where the cover would go and set its fields to the entry\'s tokens, typed or picked with the field\'s {x} button under Entry:\n| Video field | Token |\n| Video source | {{entry.coverVideo}} |\n| Poster image | {{entry.coverImage}} |\n| Video title | {{entry.title}} |\n| Video description | {{entry.excerpt}} |\n| Publication date | {{entry.publishedAt}} |\n| Duration (seconds) | {{entry.coverVideoDuration}} |\nUse {{entry.publishedAt}} for the date, not {{entry.date}}: the date token is written for readers, like 8/9/2026, which a search engine cannot read as a date. See the fields a search result reads.\nKeep list cards to a picture. In the list template\'s Collection Entries card, show each film as an Image bound to {{entry.coverImage}}. Don\'t put a Video element in a card: a list with a player in every card is one page
|
|
4345
|
+
text: 'Give every film a page of its own: a collection whose entries are articles with the film where a post\'s cover image would sit. Search engines list a video from a page that is about that video, and an entry page is exactly that.\nGive each entry its film. In the entry editor, Featured video takes a film from your media library, a video link, or a Wistia, YouTube or Vimeo link. Picking a library film that has a captured frame also fills an empty Cover image with that frame; a cover you already chose is kept.\nSay how long it runs. Video length (seconds), under the featured video, is the film\'s running time, which a video search result can show beside it. Choosing a film from your media library fills it in from the file. For a video link or a Wistia, YouTube or Vimeo link, type it yourself: 754 for a film that runs 12 minutes 34 seconds. Leave it blank if you don\'t know it; the page is still listed without one.\nPlace the player on the entry template. Add a Video element where the cover would go and set its fields to the entry\'s tokens, typed or picked with the field\'s {x} button under Entry:\n| Video field | Token |\n| Video source | {{entry.coverVideo}} |\n| Poster image | {{entry.coverImage}} |\n| Video title | {{entry.title}} |\n| Video description | {{entry.excerpt}} |\n| Publication date | {{entry.publishedAt}} |\n| Duration (seconds) | {{entry.coverVideoDuration}} |\nUse {{entry.publishedAt}} for the date, not {{entry.date}}: the date token is written for readers, like 8/9/2026, which a search engine cannot read as a date. See the fields a search result reads.\nKeep list cards to a picture. In the list template\'s Collection Entries card, show each film as an Image bound to {{entry.coverImage}}. Don\'t put a Video element in a card: a list with a player in every card is one page '
|
|
4346
4346
|
},
|
|
4347
4347
|
{
|
|
4348
4348
|
path: '/building-sites/site-templates/build-a-blog',
|
|
@@ -4741,7 +4741,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
4741
4741
|
title: 'Bookings & Scheduling',
|
|
4742
4742
|
heading: 'Payments and fees',
|
|
4743
4743
|
anchor: '#payments-and-fees',
|
|
4744
|
-
text: 'Money for a paid booking goes to you, not to Aglyn. The charge is created on your connected Stripe account, and Aglyn takes its platform fee out of it as the Stripe Connect application fee — the same way a storefront sale works.\n- A booking is priced as a service, which bills at your plan\'s digital transaction rate: 5% on Starter, 3% on Pro,
|
|
4744
|
+
text: 'Money for a paid booking goes to you, not to Aglyn. The charge is created on your connected Stripe account, and Aglyn takes its platform fee out of it as the Stripe Connect application fee — the same way a storefront sale works.\n- A booking is priced as a service, which bills at your plan\'s digital transaction rate: 5% on Starter, 3% on Pro, and 0% on Custom. It is the same rate as digital products — bookings are not charged separately or additionally.\n- The fee is taken on the service price only. Stripe\'s own processing fee is separate and comes out of your account as usual.\n- Your current rate is shown on the Payments card of the Products hub, and the full ladder is on the plans page.\nService tax\nPaid bookings charge no tax by default, and that stays true for every site that does not change it.\nA service is not goods: the sales-tax rate configured for your store is a goods rate, and whether a service is taxable is a different question with frequently the opposite answer. So Aglyn does not apply your store\'s sales rate to an appointment. Instead, Service tax, on the Taxes card (Products → Taxes), is where you set your own rate for it.\nWhen you set one, Aglyn adds it to the booking charge as its own receipt line using the label you choose, and records the amount and the regime on the booking. It is always your own rate — Stripe Tax is never asked to compute it, because it has no service tax code for this and would apply a goods rate to an appointment.\nThe platform fee is charged on the service price, never on the tax.\nAglyn does not provide tax advice Aglyn applies the rate you enter and records what was charged. It does not determine whether service tax applies to you, at what rate, or where it should be paid. Confirm your obligations with a qualified tax professional.'
|
|
4745
4745
|
},
|
|
4746
4746
|
{
|
|
4747
4747
|
path: '/commerce-and-bookings/bookings/overview',
|
|
@@ -4797,7 +4797,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
4797
4797
|
title: 'Product catalog',
|
|
4798
4798
|
heading: 'Billing modes and subscriptions',
|
|
4799
4799
|
anchor: '#billing-modes-and-subscriptions',
|
|
4800
|
-
text: 'Each product\'s Billing setting picks how buyers pay:\n- One-time purchase (default) — a normal order.\n- Monthly / Yearly subscription — buyers subscribe instead of buying once; the product page prices as $X/mo or $X/yr, the buy button reads Subscribe, and an optional free trial (in days) can precede the first charge. An active subscription is what members-only content checks.\n- Both — buyer chooses — the product page shows a one-time / subscribe toggle (same price either way, at the interval you pick) and defaults to one-time. The choice is validated server-side against the product: a one-time sale here is a plain order, while the subscribe choice creates a recurring subscription exactly like a subscription-only product.\nSelling subscriptions (including the subscribe side of Both) requires a plan with
|
|
4800
|
+
text: 'Each product\'s Billing setting picks how buyers pay:\n- One-time purchase (default) — a normal order.\n- Monthly / Yearly subscription — buyers subscribe instead of buying once; the product page prices as $X/mo or $X/yr, the buy button reads Subscribe, and an optional free trial (in days) can precede the first charge. An active subscription is what members-only content checks.\n- Both — buyer chooses — the product page shows a one-time / subscribe toggle (same price either way, at the interval you pick) and defaults to one-time. The choice is validated server-side against the product: a one-time sale here is a plain order, while the subscribe choice creates a recurring subscription exactly like a subscription-only product.\nSelling subscriptions (including the subscribe side of Both) requires a plan with recurring billing (Pro and up). Subscription billing applies to the product page\'s direct checkout — cart checkouts always charge one-time.\nWhether a subscription moves stock follows the product\'s Type. A physical subscription decrements one unit per paid cycle — the first charge and every renewal each create an order on the Subscription channel and take the box off the shelf, so the stock field stays live and low-stock alerts apply. A digital or service subscription never moves stock, and the stock field is disabled there; any number already saved is kept and shown, but it does not cap subscribers and will not change on its own. A saved 0 still stops new subscribers, so clear it (Clear stock on the notice in the editor) if that is not what you want. On a Both product the stock field stays live, because the one-time sales do decrement it.'
|
|
4801
4801
|
},
|
|
4802
4802
|
{
|
|
4803
4803
|
path: '/commerce-and-bookings/commerce/catalog',
|
|
@@ -5315,7 +5315,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
5315
5315
|
title: 'Commerce',
|
|
5316
5316
|
heading: '',
|
|
5317
5317
|
anchor: '',
|
|
5318
|
-
text: 'Commerce\nAglyn commerce sells from your own Stripe account: buyers pay you directly, and Aglyn collects a per-sale platform fee set by your plan (see Platform fees — the fee
|
|
5318
|
+
text: 'Commerce\nAglyn commerce sells from your own Stripe account: buyers pay you directly, and Aglyn collects a per-sale platform fee set by your plan (see Platform fees — the fee is lower on Pro than on Starter, and Custom carries none).\nPlan availability Paid. Starter sells up to 100 products (2% physical / 5% digital fee). Pro has no product limit and a lower fee: 0.5% on physical goods and 3% on digital and service products. Custom carries no platform fee.'
|
|
5319
5319
|
},
|
|
5320
5320
|
{
|
|
5321
5321
|
path: '/commerce-and-bookings/commerce/overview',
|
|
@@ -5336,7 +5336,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
5336
5336
|
title: 'Commerce',
|
|
5337
5337
|
heading: 'Gift cards & store credit',
|
|
5338
5338
|
anchor: '#gift-cards',
|
|
5339
|
-
text: 'Gift cards lists every card your store has issued, what is left on each one, and what that adds up to.
|
|
5339
|
+
text: 'Gift cards lists every card your store has issued, what is left on each one, and what that adds up to. Pro plan and up.\nCards arrive two ways:\n- A shopper buys one. A gift-card purchase mints a card with a code at the moment the payment settles.\n- You issue one by hand. Enter an amount and, optionally, an email address and the code is created and mailed to that person. This is the goodwill gesture and the service-recovery path — a refund you would rather keep as store credit.\n- You import them. Moving from another platform, Import issues one card per row of a file, under the codes your shoppers already hold, once you have typed back the total. Owners and admins only. See Import and export store data.\nBalances apply automatically at checkout; a shopper enters the code and the card is drawn down by what the order uses. Search by code or email finds a card anywhere in the list, not only on the page in front of you: type the start of its code (with or without GC-) or a word of the recipient\'s address. Search matches one word at a time and reads the first 12 characters of it.\nOutstanding balance is a liability, not revenue The outstanding total at the top is money customers have already paid you and have not yet spent. It is store credit you owe against future orders, and it belongs on the liability side of your books — not in a sales figure. Cards are counted at zero or above, so a card that has somehow gone negative cannot flatter that total downward.\nVoiding a card zeroes whatever is left on it. The holder can no longer redeem it and the action cannot be undone, so you are asked to confirm the remaining amount first.'
|
|
5340
5340
|
},
|
|
5341
5341
|
{
|
|
5342
5342
|
path: '/commerce-and-bookings/commerce/overview',
|
|
@@ -5462,7 +5462,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
5462
5462
|
title: 'POS & reservations',
|
|
5463
5463
|
heading: '',
|
|
5464
5464
|
anchor: '',
|
|
5465
|
-
text: 'POS & reservations\nPlan availability POS requires Pro or above. The number of registers a site can run at once follows your plan —
|
|
5465
|
+
text: 'POS & reservations\nPlan availability POS requires Pro or above. The number of registers a site can run at once follows your plan — 1 on Pro — plus any additional register seats you\'ve assigned to that site. A seat is bought once for the workspace and then placed on one site, so buying one does not raise the limit everywhere; see Assigning register seats. Opening more browser tabs does not give you more registers; each sale runs through a register you\'ve created.'
|
|
5466
5466
|
},
|
|
5467
5467
|
{
|
|
5468
5468
|
path: '/commerce-and-bookings/commerce/pos-and-reservations',
|
|
@@ -6680,7 +6680,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
6680
6680
|
title: 'Term reference',
|
|
6681
6681
|
heading: 'Platform & accounts',
|
|
6682
6682
|
anchor: '#platform--accounts',
|
|
6683
|
-
text: 'Aglyn\nThe platform these docs cover — the console you build in and the sites you publish. Pronounced AG-lin — "ag" as in agriculture, with the stress on the first syllable (IPA /ˈæɡlɪn/).\nAglyn AI\nThe generative side of the assistant: the doors that build a page, layout, page template, reusable component, form, email, campaign, product copy, SEO text or theme change from a description. Included on every plan and metered in its AI credits, with
|
|
6683
|
+
text: 'Aglyn\nThe platform these docs cover — the console you build in and the sites you publish. Pronounced AG-lin — "ag" as in agriculture, with the stress on the first syllable (IPA /ˈæɡlɪn/).\nAglyn AI\nThe generative side of the assistant: the doors that build a page, layout, page template, reusable component, form, email, campaign, product copy, SEO text or theme change from a description. Included on every plan and metered in its AI credits, with blocks of AI credits that add more on top; carried by agreement on Custom. Everything it makes is a draft — it never publishes, changes a live page in place or sends anything. → Aglyn AI, Add-ons\nAglyn Assist\nThe chat helper in the console, which answers questions about the product from this documentation and cites the sections it drew on. Aglyn AI is the same assistant when it builds rather than explains. → Aglyn Assist\nOrganization (org)\nThe account entity: one subscription, one team roster, one plugin switchboard, one data-isolation boundary. Everything you own in Aglyn — sites, datasets, media, installs — belongs to an organization. In code and APIs this is always org. → Glossary, Teams & roles\nWorkspace\nThe same entity as an organization, in the product\'s user-facing language — "your workspace", including the {slug}.aglyn.com workspace URL. Workspace never names anything in code; it\'s the word the UI uses for your org. → Glossary\nTenant\nThe published-site runtime: the single deployment that takes any incoming domain, resolves it to one of your sites, and renders its published pages. "Tenant" always means this serving side of the platform — it is not another word for organization. → Glossary, Architecture & multi-tenancy\nHost\nOne site, as the data model sees it: its subdomain or custom domain, its pages and layouts, its media,'
|
|
6684
6684
|
},
|
|
6685
6685
|
{
|
|
6686
6686
|
path: '/concepts/term-reference',
|
|
@@ -6736,7 +6736,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
6736
6736
|
title: 'Term reference',
|
|
6737
6737
|
heading: 'Billing & plans',
|
|
6738
6738
|
anchor: '#billing--plans',
|
|
6739
|
-
text: 'Plan\nThe subscription tier an organization is on. Entitlements resolve from the plan at read time; workspaces without a plan run dark-launch (ungated). → Billing & plans\nEntitlement\nA capability or limit granted by the plan — feature switches and quotas — optionally overridden per organization by staff. → Billing & plans\nQuota\nA numeric entitlement (sites, datasets, storage) checked at the point of use, with warnings as you approach the limit. → Billing & plans\nSeat\nA team-member allowance. Plans include seats; addon seats can be purchased up to a per-plan maximum. → Teams & roles\nMetered usage\nConsumption billed monthly in arrears (storage, delivery) with a live estimate shown before it lands on an invoice. → Billing & plans\nCredit (AI credit)\nThe unit every AI request is measured in — an assistant answer, a rewrite, a generated section, a whole site — drawn from one monthly pool per workspace rather than a meter per feature. What a request costs varies with how much work it is, and a job estimates itself before you confirm. A plan includes a band each month,
|
|
6739
|
+
text: 'Plan\nThe subscription tier an organization is on. Entitlements resolve from the plan at read time; workspaces without a plan run dark-launch (ungated). → Billing & plans\nEntitlement\nA capability or limit granted by the plan — feature switches and quotas — optionally overridden per organization by staff. → Billing & plans\nQuota\nA numeric entitlement (sites, datasets, storage) checked at the point of use, with warnings as you approach the limit. → Billing & plans\nSeat\nA team-member allowance. Plans include seats; addon seats can be purchased up to a per-plan maximum. → Teams & roles\nMetered usage\nConsumption billed monthly in arrears (storage, delivery) with a live estimate shown before it lands on an invoice. → Billing & plans\nCredit (AI credit)\nThe unit every AI request is measured in — an assistant answer, a rewrite, a generated section, a whole site — drawn from one monthly pool per workspace rather than a meter per feature. What a request costs varies with how much work it is, and a job estimates itself before you confirm. A plan includes a band each month, blocks of AI credits add more on top, and a workspace can stop at the band or set a ceiling on what it will pay past it. → Credits and caps, AI assist overage\nAllotment\nOne member\'s, one site collaborator\'s or one whole site\'s monthly share of the workspace\'s AI credits. Hard stops AI there; soft keeps working and notifies. A share of the pool, never an addition to it. → AI allotments'
|
|
6740
6740
|
},
|
|
6741
6741
|
{
|
|
6742
6742
|
path: '/content-and-data/crm/activities',
|
|
@@ -9207,7 +9207,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
9207
9207
|
title: 'Publisher handbook',
|
|
9208
9208
|
heading: 'What your listing can say about Aglyn',
|
|
9209
9209
|
anchor: '#what-your-listing-can-say-about-aglyn',
|
|
9210
|
-
text: 'Your listing renders inside Aglyn\'s own console, on the page a customer is reading while they decide whether to upgrade. That is why this one has a rule attached: a plugin sold as "the cheap way out of
|
|
9210
|
+
text: 'Your listing renders inside Aglyn\'s own console, on the page a customer is reading while they decide whether to upgrade. That is why this one has a rule attached: a plugin sold as "the cheap way out of Pro" is doing its selling with our pricing page, not with your plugin.\nFine — say all of this:\n- What your plugin does, and how well it does it.\n- Which Aglyn plans or features it requires: "needs the Pro plan", "uses custom domains", "requires the datasets API".\n- Which plans or features it is compatible with, stated as fact.\n- What it costs, and what a buyer gets for it.\nNot fine:\n- Disparaging Aglyn or the platform ("Aglyn\'s built-in analytics are useless").\n- Stating or implying what an Aglyn plan costs or contains ("Pro is $X for features you won\'t use", "the Pro plan caps you at 5 sites"). Plans and prices change; a listing that quotes them goes stale and misinforms buyers who trust it.\n- Comparing your price against ours ("half the price of an upgrade").\n- Naming, framing or marketing the plugin around avoiding, replacing or discouraging an Aglyn plan or upgrade — "Skip the upgrade", "Pro features without the Pro plan", "don\'t pay for Pro".\nThe line is simple: describe your plugin, not our pricing. If you need a customer to know they must be on Pro for your plugin to work, say exactly that — a requirement is a fact about your plugin, and it belongs in the listing.\nThis is §3(h) of the publisher agreement, you confirm it at every publish, and a reviewer checks the title, description and README against it. A listing that crosses it is rejected with the reason rather than quietly edited, so you get to fix your own words.'
|
|
9211
9211
|
},
|
|
9212
9212
|
{
|
|
9213
9213
|
path: '/developers/plugins/publishing/publisher-handbook',
|
|
@@ -10184,24 +10184,24 @@ export const DOCS_SECTION_INDEX = [
|
|
|
10184
10184
|
},
|
|
10185
10185
|
{
|
|
10186
10186
|
path: '/enterprise/overview',
|
|
10187
|
-
title: 'Enterprise
|
|
10187
|
+
title: 'Enterprise and the Custom plan',
|
|
10188
10188
|
heading: '',
|
|
10189
10189
|
anchor: '',
|
|
10190
|
-
text: 'Enterprise
|
|
10190
|
+
text: 'Enterprise and the Custom plan\nCustom is the plan for enterprise agreements, and the only plan that is not self-serve. It is quoted rather than listed, and it is the plan the pages in this section describe. Until November 2026 it was labeled Enterprise; only the name changed.\nCustom carries everything in Pro, plus white-label, single sign-on, a dedicated support commitment, no transaction fee, and limits sized by your agreement.\n| | |\n| Single sign-on | SAML SSO against your identity provider, optionally enforced so passwords stop working. |\n| Support commitments | A 24–48 hour first-response commitment measured in clock hours, and a named success manager. |\n| Availability & status | What we measure, what /status shows, and what we have not committed to. |\n| Security & compliance | The material a security review needs, including what we do not have. |'
|
|
10191
10191
|
},
|
|
10192
10192
|
{
|
|
10193
10193
|
path: '/enterprise/overview',
|
|
10194
|
-
title: 'Enterprise
|
|
10195
|
-
heading: 'What
|
|
10196
|
-
anchor: '#what-
|
|
10197
|
-
text: 'Worth saying plainly, because it is the usual assumption:\n- Quotas and features are entitlements, not plan names.
|
|
10194
|
+
title: 'Enterprise and the Custom plan',
|
|
10195
|
+
heading: 'What Custom does not change',
|
|
10196
|
+
anchor: '#what-custom-does-not-change',
|
|
10197
|
+
text: 'Worth saying plainly, because it is the usual assumption:\n- Quotas and features are entitlements, not plan names. A Custom workspace can have any combination of limits, and they are set per organization rather than implied by the plan.\n- The product is the same product. Custom is about how we contract, respond and authenticate — not a separate build.'
|
|
10198
10198
|
},
|
|
10199
10199
|
{
|
|
10200
10200
|
path: '/enterprise/overview',
|
|
10201
|
-
title: 'Enterprise
|
|
10202
|
-
heading: 'Getting
|
|
10203
|
-
anchor: '#getting-
|
|
10204
|
-
text: 'Contact us —
|
|
10201
|
+
title: 'Enterprise and the Custom plan',
|
|
10202
|
+
heading: 'Getting the Custom plan',
|
|
10203
|
+
anchor: '#getting-the-custom-plan',
|
|
10204
|
+
text: 'Contact us — Custom is the one plan with no self-serve checkout, so the plan itself is arranged with us rather than bought from the billing page.\nEverything after that is yours to configure. Single sign-on in particular is set up by your own admins in Organization → Settings → Single sign-on: claim your domain, verify a DNS TXT record, exchange IdP metadata, rehearse enforcement, and activate. There is no provisioning step on our side and nothing to wait for.'
|
|
10205
10205
|
},
|
|
10206
10206
|
{
|
|
10207
10207
|
path: '/enterprise/security-and-compliance',
|
|
@@ -10250,7 +10250,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
10250
10250
|
title: 'Single sign-on (SAML)',
|
|
10251
10251
|
heading: '',
|
|
10252
10252
|
anchor: '',
|
|
10253
|
-
text: 'Single sign-on (SAML)\nSSO signs your team in against your own identity provider. It is
|
|
10253
|
+
text: 'Single sign-on (SAML)\nSSO signs your team in against your own identity provider. It is a feature of the Custom plan (once labeled Enterprise), and once your organization is on Custom you set it up yourself in Organization → Settings → Single sign-on. There is no provisioning step on our side and nothing to wait for.'
|
|
10254
10254
|
},
|
|
10255
10255
|
{
|
|
10256
10256
|
path: '/enterprise/sso',
|
|
@@ -10299,14 +10299,14 @@ export const DOCS_SECTION_INDEX = [
|
|
|
10299
10299
|
title: 'Support commitments',
|
|
10300
10300
|
heading: '',
|
|
10301
10301
|
anchor: '',
|
|
10302
|
-
text: 'Support commitments\nEvery plan gets the community forum. Private ticket support starts at Pro — Free and Starter pay for product, not for our time.\nThe commitment below is a first response, not a resolution. It is what the Support tickets page shows you, and what the staff queue is ordered by.\n| Plan | Tier | First response | Named success manager |\n| Free | Community | Forum only | — |\n| Starter | Community | Forum only | — |\n| Pro | Standard | 7–14 business days | — |\n|
|
|
10302
|
+
text: 'Support commitments\nEvery plan gets the community forum. Private ticket support starts at Pro — Free and Starter pay for product, not for our time.\nThe commitment below is a first response, not a resolution. It is what the Support tickets page shows you, and what the staff queue is ordered by.\n| Plan | Tier | First response | Named success manager |\n| Free | Community | Forum only | — |\n| Starter | Community | Forum only | — |\n| Pro | Standard | 7–14 business days | — |\n| Custom | Dedicated | 24–48 hours | Yes |\nCustom is the plan once labeled Enterprise.'
|
|
10303
10303
|
},
|
|
10304
10304
|
{
|
|
10305
10305
|
path: '/enterprise/support-tiers',
|
|
10306
10306
|
title: 'Support commitments',
|
|
10307
|
-
heading: 'Why
|
|
10308
|
-
anchor: '#why-
|
|
10309
|
-
text: 'It is the point of the tier. 24–48 clock hours runs through a weekend;
|
|
10307
|
+
heading: 'Why Custom is in hours, not business days',
|
|
10308
|
+
anchor: '#why-custom-is-in-hours-not-business-days',
|
|
10309
|
+
text: 'It is the point of the tier. 24–48 clock hours runs through a weekend; a window counted in business days does not. Read as business hours, the Custom window would stretch to 3–6 business days.\nThere is a test asserting the ladder stays monotonic, so this cannot quietly regress into the wrong order.'
|
|
10310
10310
|
},
|
|
10311
10311
|
{
|
|
10312
10312
|
path: '/enterprise/support-tiers',
|
|
@@ -10355,7 +10355,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
10355
10355
|
title: 'Availability & status',
|
|
10356
10356
|
heading: 'Reporting an outage',
|
|
10357
10357
|
anchor: '#reporting-an-outage',
|
|
10358
|
-
text: 'If something is down and /status disagrees, tell us — the status page checks reachability, which is not the same as everything working.\nOpen a ticket from Organization → Support → Support tickets. Response is governed by your support commitment;
|
|
10358
|
+
text: 'If something is down and /status disagrees, tell us — the status page checks reachability, which is not the same as everything working.\nOpen a ticket from Organization → Support → Support tickets. Response is governed by your support commitment; on the Custom plan it is 24–48 clock hours.'
|
|
10359
10359
|
},
|
|
10360
10360
|
{
|
|
10361
10361
|
path: '/getting-started/aglyn-assist',
|
|
@@ -10376,7 +10376,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
10376
10376
|
title: 'Aglyn Assist',
|
|
10377
10377
|
heading: 'When it builds instead of answering',
|
|
10378
10378
|
anchor: '#aglyn-ai',
|
|
10379
|
-
text: 'Everything above is the assistant explaining. On every plan, from the AI credits it includes (and any
|
|
10379
|
+
text: 'Everything above is the assistant explaining. On every plan, from the AI credits it includes (and any blocks of AI credits on top), the same assistant also builds: whole pages, layouts, page templates, reusable components, forms, designed emails, campaigns, product copy, your search titles and descriptions, a change to your theme, and a small site from one brief. AI jobs in the panel is where you watch one work and open what it made. It opens on its own while a job is running or waiting for you, the AI chip in the top bar says what your jobs are doing, and the Assist button carries a badge while one runs. See Finding your AI jobs.\nEverything it builds arrives as a draft. It never publishes, never changes a live page in place and never sends anything, so a generated page has no address on your live site until you publish it yourself.\nWhat each door does, what it costs in credits and who can use it is in Aglyn AI. To build several things from one chat message, see Build from Assist chat.'
|
|
10380
10380
|
},
|
|
10381
10381
|
{
|
|
10382
10382
|
path: '/getting-started/aglyn-assist',
|
|
@@ -10397,7 +10397,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
10397
10397
|
title: 'Aglyn Assist',
|
|
10398
10398
|
heading: 'Edits in the Besigner',
|
|
10399
10399
|
anchor: '#edits-in-the-besigner',
|
|
10400
|
-
text: 'With a page, a reusable component or a layout open in the Besigner, you can ask the assistant for a change: "make this hero darker", "add a testimonial band below", "point this button at the pricing page". On every plan, from its included AI credits (and any
|
|
10400
|
+
text: 'With a page, a reusable component or a layout open in the Besigner, you can ask the assistant for a change: "make this hero darker", "add a testimonial band below", "point this button at the pricing page". On every plan, from its included AI credits (and any blocks of AI credits on top), it answers with a Proposed change card listing what would change: elements added, removed, moved or restyled, settings changed, interactions added, and a page\'s search title or description filled in. Anything it could not match to your canvas is listed under Left out.\n- Interactions on the selected element. Ask "when this is clicked, show the panel below" and the assistant proposes an interaction on the element: something a visitor does to it — a click, a hover, scrolling it into view — and the steps that follow, chosen from the presentational ones every plan runs (show, hide or toggle an element, add or remove a class, scroll to or play an element, open or close a drawer or menu, go to a page, show a message). It is added beside anything the element already does, never in place of it; edit or remove it under Interactions like any other. Ask "what does this do?" and it explains the interactions the element carries.\n- Nothing changes until you apply. Apply as draft puts the changes on the open canvas as unsaved edits, all in one step, so a single Undo takes the whole change back. Nothing is saved or published until you do that yourself. A proposed search title or description is filled into Page Properties, where Save SEO stores it.\n- The version your live site shows takes the change too. Apply as draft works there the same way, as unsaved edits on the canvas. Save draft keeps them in the page\'s draft, and visitors see nothing until you publish. To make the change on a copy instead, choos'
|
|
10401
10401
|
},
|
|
10402
10402
|
{
|
|
10403
10403
|
path: '/getting-started/aglyn-assist',
|
|
@@ -10635,7 +10635,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
10635
10635
|
title: 'Publish your first page',
|
|
10636
10636
|
heading: '3. Preview and publish',
|
|
10637
10637
|
anchor: '#3-preview-and-publish',
|
|
10638
|
-
text: '1. Use the artboard light/dark toggle to check both color schemes.\n2. Save the canvas. Saving writes your working version — it isn\'t publishing.\n3. Publish. The page\'s slug is registered in the routing map and the page goes live on your site\'s domain.\nKeeping more than one version is a Pro feature Every page is created with one working version, and Save updates that version on every plan — the core loop above needs nothing extra. Keeping more than one — named snapshots you can reopen, publish to roll back to, or schedule — requires Pro or above,
|
|
10638
|
+
text: '1. Use the artboard light/dark toggle to check both color schemes.\n2. Save the canvas. Saving writes your working version — it isn\'t publishing.\n3. Publish. The page\'s slug is registered in the routing map and the page goes live on your site\'s domain.\nKeeping more than one version is a Pro feature Every page is created with one working version, and Save updates that version on every plan — the core loop above needs nothing extra. Keeping more than one — named snapshots you can reopen, publish to roll back to, or schedule — requires Pro or above too, as does scheduling a version. On Free and Starter the Versions dialog still shows New version, disabled, with a note naming the plan that includes it and an Upgrade button to the plans on Billing. See Versions & scheduled publishing.\nThe Live button The Live button is environment-aware — in production it reflects your published saves so you can jump straight to the real page.'
|
|
10639
10639
|
},
|
|
10640
10640
|
{
|
|
10641
10641
|
path: '/getting-started/publish-your-first-screen',
|
|
@@ -10775,7 +10775,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
10775
10775
|
title: 'Commerce end to end',
|
|
10776
10776
|
heading: '',
|
|
10777
10777
|
anchor: '',
|
|
10778
|
-
text: 'Commerce end to end\nThis walkthrough runs the whole selling loop: catalog → storefront → checkout → orders → subscriptions. It links into the commerce reference rather than repeating it — the goal here is the end-to-end path.\nPlan availability Selling needs a paid plan (fees
|
|
10778
|
+
text: 'Commerce end to end\nThis walkthrough runs the whole selling loop: catalog → storefront → checkout → orders → subscriptions. It links into the commerce reference rather than repeating it — the goal here is the end-to-end path.\nPlan availability Selling needs a paid plan (fees are lower on Pro — see Billing & plans). Storefront subscriptions (including the subscribe side of "Both — buyer chooses") need Pro and up.'
|
|
10779
10779
|
},
|
|
10780
10780
|
{
|
|
10781
10781
|
path: '/guides/commerce-end-to-end',
|
|
@@ -10859,7 +10859,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
10859
10859
|
title: 'Datasets & schema deep-dive',
|
|
10860
10860
|
heading: 'Record quotas per plan',
|
|
10861
10861
|
anchor: '#record-quotas-per-plan',
|
|
10862
|
-
text: 'Dataset counts, records per dataset and dataset storage are entitlements of your organization\'s plan:\n| Plan | Datasets | Most with add-ons | Records per dataset | Dataset storage |\n| Free | — (no data store) | — | — | — |\n| Starter |
|
|
10862
|
+
text: 'Dataset counts, records per dataset and dataset storage are entitlements of your organization\'s plan:\n| Plan | Datasets | Most with add-ons | Records per dataset | Dataset storage |\n| Free | — (no data store) | — | — | — |\n| Starter | 2 | 10 | 1,000 | 512 MB |\n| Pro | 5 | No limit | Unlimited | 2 GB |\n| Custom | Set by agreement | Set by agreement | Set by agreement | Set by agreement |\n- Creating datasets on Free is rejected with "Datasets require a Starter plan or higher."\n- Hitting the record cap surfaces "Record limit reached — see Billing to upgrade" in the console. An import that would overflow writes the rows that fit and skips the rest, reporting them as over the record limit.\n- Form submissions never fail on quota — if the dataset is full the record write is skipped silently, but the inbox copy is always kept.\n- Add-ons raise the dataset count beyond the base allowance, up to the most shown above.\n- Dataset storage past the included amount bills per GB-month on Starter and Pro, at the rate on aglyn.com/pricing. Custom has no overage rate, so writes stop at its limit.'
|
|
10863
10863
|
},
|
|
10864
10864
|
{
|
|
10865
10865
|
path: '/guides/datasets-and-schema',
|
|
@@ -11055,7 +11055,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
11055
11055
|
title: 'Member accounts',
|
|
11056
11056
|
heading: '',
|
|
11057
11057
|
anchor: '',
|
|
11058
|
-
text: 'Member accounts\nVisitors can become members of your published site — sign up, sign in, see their orders, and unlock members-only pages. This walkthrough covers the visitor side (built-in auth pages and the account block) and the console side (the Users page and the member drawer).\nPlan availability Member signups and the account block work wherever commerce does; gating pages to members needs the content-gating feature (
|
|
11058
|
+
text: 'Member accounts\nVisitors can become members of your published site — sign up, sign in, see their orders, and unlock members-only pages. This walkthrough covers the visitor side (built-in auth pages and the account block) and the console side (the Users page and the member drawer).\nPlan availability Member signups and the account block work wherever commerce does; gating pages to members needs the content-gating feature (Pro and up) — see Members-only areas.\nMembers are not console users Site members are your site\'s audience, separate from the console teammates you invite to collaborate. Members sign in on your published site only, with a per-site session — they never see the console.'
|
|
11059
11059
|
},
|
|
11060
11060
|
{
|
|
11061
11061
|
path: '/guides/member-accounts',
|
|
@@ -11195,14 +11195,14 @@ export const DOCS_SECTION_INDEX = [
|
|
|
11195
11195
|
title: 'Run an agency workspace',
|
|
11196
11196
|
heading: 'The mental model, first',
|
|
11197
11197
|
anchor: '#the-model',
|
|
11198
|
-
text: 'Three words, and getting them straight up front saves a lot of confusion later:\n| Term | What it is | For an agency |\n| Organization | The billing and identity boundary. Owns the plan, the invoice, the members, the shared library. | You. One organization for your agency. |\n| Site (or host) | One published website with its own pages, domain, media and store. | One per client project. |\n| Workspace | What the console calls your organization when you\'re working in it. | Same thing as organization — you\'ll see both words. |\nThe consequence that matters: your plan\'s limits are per organization, and your access controls are per site. You buy 25 sites once; you decide separately who can touch which one.\nOne organization or one per client? Use one organization when the sites are yours to run: you hold the domains, you bill the client for a service, you\'re the one on call. That\'s the normal agency shape, and it\'s what
|
|
11198
|
+
text: 'Three words, and getting them straight up front saves a lot of confusion later:\n| Term | What it is | For an agency |\n| Organization | The billing and identity boundary. Owns the plan, the invoice, the members, the shared library. | You. One organization for your agency. |\n| Site (or host) | One published website with its own pages, domain, media and store. | One per client project. |\n| Workspace | What the console calls your organization when you\'re working in it. | Same thing as organization — you\'ll see both words. |\nThe consequence that matters: your plan\'s limits are per organization, and your access controls are per site. You buy 25 sites once; you decide separately who can touch which one.\nOne organization or one per client? Use one organization when the sites are yours to run: you hold the domains, you bill the client for a service, you\'re the one on call. That\'s the normal agency shape, and it\'s what Pro, with an extra site per client, is priced for.\nUse a separate organization per client when the client ultimately owns the account and you\'re only building it — they hold the card, the domain, and the risk. You then join their organization as a member and can leave cleanly.\nTo build first and hand over later, create a workspace for the client, build the site there, and then send the client an owner handoff from its Team page: Role → Owner (hand off this workspace). When they sign in with that address, the workspace and every site in it are theirs, with nothing to accept. You choose whether you stay on as an admin or leave. Staying needs a free team seat on their plan, so on Free choose Leave after the handoff, or have them add a seat first.'
|
|
11199
11199
|
},
|
|
11200
11200
|
{
|
|
11201
11201
|
path: '/guides/run-an-agency-workspace',
|
|
11202
11202
|
title: 'Run an agency workspace',
|
|
11203
11203
|
heading: 'Step 1 — Pick the plan by site count, not by features',
|
|
11204
11204
|
anchor: '#step-1-plan',
|
|
11205
|
-
text: 'For agencies the binding limit is almost always how many sites you can publish, not which features you get. Check the site allowance on the plan table and pick from there.\nTwo things that change the arithmetic:\n- Extra sites are an add-on, so you don\'t
|
|
11205
|
+
text: 'For agencies the binding limit is almost always how many sites you can publish, not which features you get. Check the site allowance on the plan table and pick from there.\nTwo things that change the arithmetic:\n- Extra sites are an add-on, so you don\'t change plan for one more client. Pro includes three sites, and each one past that is the same flat price.\n- The platform fee on client storefront sales is lower on Pro and none on Custom. If your clients sell, that fee can dominate the subscription price — do that sum before choosing. White-label, if you resell the platform under your own name, is on Custom.\nUpgrades are instant, downgrades are not An upgrade applies immediately and prorates. A downgrade waits until the end of the period you already paid for, and $0 is due on the day you choose it. Plan seasonal capacity accordingly: dropping a plan in January doesn\'t reduce a January invoice. When each change takes effect.'
|
|
11206
11206
|
},
|
|
11207
11207
|
{
|
|
11208
11208
|
path: '/guides/run-an-agency-workspace',
|
|
@@ -11328,7 +11328,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
11328
11328
|
title: 'Your first API call',
|
|
11329
11329
|
heading: '',
|
|
11330
11330
|
anchor: '',
|
|
11331
|
-
text: 'Your first API call\nBy the end of this page you\'ll have made a real request to your own data and handled the errors properly. It assumes nothing — if you\'ve never used an API before, start at the top and follow along; if you have, skip to Step 3 and then read the API reference instead of the rest of this.\nEverything here uses curl, which is already installed on macOS and Linux and ships with Windows 10 and later. There\'s a JavaScript version of each step underneath.\nWhat you need\n- An organization on a plan that includes API access —
|
|
11331
|
+
text: 'Your first API call\nBy the end of this page you\'ll have made a real request to your own data and handled the errors properly. It assumes nothing — if you\'ve never used an API before, start at the top and follow along; if you have, skip to Step 3 and then read the API reference instead of the rest of this.\nEverything here uses curl, which is already installed on macOS and Linux and ships with Windows 10 and later. There\'s a JavaScript version of each step underneath.\nWhat you need\n- An organization on a plan that includes API access — Pro or Custom.\n- Permission to manage the organization — only owners and admins can create keys.\n- A terminal.'
|
|
11332
11332
|
},
|
|
11333
11333
|
{
|
|
11334
11334
|
path: '/guides/your-first-api-call',
|
|
@@ -11468,7 +11468,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
11468
11468
|
title: 'Cookie consent',
|
|
11469
11469
|
heading: 'What needs consent',
|
|
11470
11470
|
anchor: '#what-needs-consent',
|
|
11471
|
-
text: 'Consent-gated — held back unless the visitor\'s recorded state grants analytics:\n- Google Analytics (your configured measurement ID) and every event Aglyn sends to it — see Google Analytics events.\n- Google Tag Manager (your configured container ID). The container is gated the same way and never more loosely, so it cannot be used to install a tag that runs before consent.\n- Core Web Vitals reporting. Page-speed metrics reach your property only through the same tag, and are discarded rather than held if consent is refused while a page is open.\n- Cross-visit A/B test identity: without an analytics grant, experiment variant assignment is remembered only for the visit (sessionStorage) instead of across visits.\n- Funnel visits. On a site with a funnel, each visit\'s steps are tied together by a random id kept in that browser tab\'s session storage, and the id is sent with each step. No step is recorded until the visitor\'s state grants analytics; a refusal deletes the id. See What counts as a visit.\n- Remembering the campaign that last touched a visitor. Reading it on the page they are on needs no grant; keeping it across visits does. See The campaign a visitor came from.\n- A Wistia player loaded with the page — see Videos that load with the page.\n- Advertising storage (adstorage, aduserdata, adpersonalization), on sites that have turned the advertising question on. Where it starts depends on the visitor\'s region, and it is the same split analytics uses:\n- Prior-consent regions. The EU/EEA, the UK, and any visitor whose region cannot be determined see the banner first, and advertising storage is denied until they tick that specific box. Not objecting is never a yes here.\n- Everywhere else. Advertising runs from their first visit, alongside analytics, on the
|
|
11471
|
+
text: 'Consent-gated — held back unless the visitor\'s recorded state grants analytics:\n- Google Analytics (your configured measurement ID) and every event Aglyn sends to it — see Google Analytics events.\n- Google Tag Manager (your configured container ID). The container is gated the same way and never more loosely, so it cannot be used to install a tag that runs before consent.\n- Core Web Vitals reporting. Page-speed metrics reach your property only through the same tag, and are discarded rather than held if consent is refused while a page is open.\n- Cross-visit A/B test identity: without an analytics grant, experiment variant assignment is remembered only for the visit (sessionStorage) instead of across visits.\n- Funnel visits. On a site with a funnel, each visit\'s steps are tied together by a random id kept in that browser tab\'s session storage, and the id is sent with each step. No step is recorded until the visitor\'s state grants analytics; a refusal deletes the id. See What counts as a visit.\n- Remembering the campaign that last touched a visitor. Reading it on the page they are on needs no grant; keeping it across visits does. See The campaign a visitor came from.\n- A Wistia, YouTube or Vimeo player loaded with the page — see Videos that load with the page.\n- Advertising storage (adstorage, aduserdata, adpersonalization), on sites that have turned the advertising question on. Where it starts depends on the visitor\'s region, and it is the same split analytics uses:\n- Prior-consent regions. The EU/EEA, the UK, and any visitor whose region cannot be determined see the banner first, and advertising storage is denied until they tick that specific box. Not objecting is never a yes here.\n- Everywhere else. Advertising runs from their first visit, alongside analytics, on the sam'
|
|
11472
11472
|
},
|
|
11473
11473
|
{
|
|
11474
11474
|
path: '/marketing-and-automation/analytics/cookie-consent',
|
|
@@ -11482,7 +11482,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
11482
11482
|
title: 'Cookie consent',
|
|
11483
11483
|
heading: 'Videos that load with the page',
|
|
11484
11484
|
anchor: '#videos-that-load-with-the-page',
|
|
11485
|
-
text: 'A Video element with Load the player with the page on is consent-gated like the list above: it puts
|
|
11485
|
+
text: 'A Video element with Load the player with the page on is consent-gated like the list above: it puts the video host\'s player (Wistia, YouTube or Vimeo) in place of its poster only for a visitor whose recorded state grants analytics, and everyone else gets the poster. The player keeps its own storage inside its frame as soon as it loads, before anyone presses play; Wistia\'s is wistia and wistia-video-progress-{media id}. A press loads the player for any visitor: Wistia\'s with its do-not-track option unless analytics is granted, YouTube\'s always in its privacy-enhanced player, and Vimeo\'s always with its do-not-track option on. The player keeps its storage then too.'
|
|
11486
11486
|
},
|
|
11487
11487
|
{
|
|
11488
11488
|
path: '/marketing-and-automation/analytics/cookie-consent',
|
|
@@ -12105,7 +12105,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
12105
12105
|
title: 'Email Campaigns',
|
|
12106
12106
|
heading: 'Experiments',
|
|
12107
12107
|
anchor: '#experiments',
|
|
12108
|
-
text: '
|
|
12108
|
+
text: 'Pro and Custom plans can A/B test pages, sections, and emails from the Experiments card on the Marketing page: weighted variants, deterministic visitor assignment, a conversion goal, and per-variant exposure/conversion rates with a pick-the-winner flow.\nTwo ways to finish a test without watching it:\n- End date — past it, visitors get the default and stats stop accruing until you pick a winner.\n- Auto-declare winner — opt in with a minimum exposure count per variant and a confidence level (90/95/99%); once a challenger clears the bar (or every challenger confidently loses to the control), the experiment completes itself and serves the winner. Auto-completed tests carry a chip in the results dialog.\n- Pages & sections — variants pin a page version; visitors are split deterministically and the winning version serves to everyone once you pick it. Start a section test straight from the Besigner\'s Interactions panel.\n- Emails — variants override the campaign\'s subject and/or body. Attach a running email experiment in the campaign composer; each recipient deterministically receives one variant (re-sends reach the same variant), sends count as exposures, and once a winner is picked every later send uses the winning copy.\nThe Experiments table filters through its toolbar by Experiment (a name that contains a word, or is exactly a name in either case), Tests (page, section or email) and Status (draft, running, paused or done; one or several of each). Search finds an experiment by the start of any word in its name: cop finds Hero copy. Every filter and the search are answered by the query, across all of the site\'s experiments, a page at a time and in name order, not only over the page on screen. Experiment containing a word and Search both match words of the name, so only one of t'
|
|
12109
12109
|
},
|
|
12110
12110
|
{
|
|
12111
12111
|
path: '/marketing-and-automation/email-campaigns/overview',
|
|
@@ -12217,7 +12217,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
12217
12217
|
title: 'Actions builder',
|
|
12218
12218
|
heading: 'Steps',
|
|
12219
12219
|
anchor: '#steps',
|
|
12220
|
-
text: 'Steps run in order and mix in-page effects with server-side work:\n- Basic in-page effects (all plans): open/close/toggle a menu or drawer, show/hide or toggle an element, add/remove/toggle a CSS class, set or remove an ARIA or data attribute, scroll to an element, play a video, make the navigation sticky, redirect, show a site alert. These are pure DOM choreography — they run everywhere and are never metered.\n- Advanced in-page effects (Pro+): show a popup or bar from your Marketing overlays, show custom HTML, track an analytics event, and run custom JS
|
|
12220
|
+
text: 'Steps run in order and mix in-page effects with server-side work:\n- Basic in-page effects (all plans): open/close/toggle a menu or drawer, show/hide or toggle an element, add/remove/toggle a CSS class, set or remove an ARIA or data attribute, scroll to an element, play a video, make the navigation sticky, redirect, show a site alert. These are pure DOM choreography — they run everywhere and are never metered.\n- Advanced in-page effects (Pro+): show a popup or bar from your Marketing overlays, show custom HTML, track an analytics event, and run custom JS.\n- On the server (Pro+): run a workflow, write to or update a dataset, send a webhook, send an email, notify site admins, enroll the contact in a list, assign a campaign, fire a custom event to chain more actions. A dataset step holds its record to the dataset\'s model like every other write: each value is stored as its field\'s type, and a value that doesn\'t fit fails the step, naming the field, with nothing written. An update checks only the fields it sends.\n- In the CRM (Pro+): set the contact\'s lifecycle stage, tag the contact, assign the contact an owner, create a CRM task, log a CRM activity. See CRM steps.\n- Flow steps (Pro+): Wait, Wait for something to happen, and End the flow here. See Sequences below.\nOn plans without the automations entitlement, an automation that mixes tiers still runs its basic in-page steps — the Pro+ steps are simply skipped until you upgrade.\nEverything above that runs on the server — the server-side, CRM and flow steps — is also a step you can add to a workflow, beside its function calls. The in-page effects are not, because a workflow runs on a server event with no page open.\nCRM steps {#crm-steps}\nFive server steps act on the CRM. None of them asks which contact: each acts on the person'
|
|
12221
12221
|
},
|
|
12222
12222
|
{
|
|
12223
12223
|
path: '/marketing-and-automation/workflows-and-actions/actions-builder',
|
|
@@ -12280,7 +12280,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
12280
12280
|
title: 'Build a workflow',
|
|
12281
12281
|
heading: '3. Add steps',
|
|
12282
12282
|
anchor: '#3-add-steps',
|
|
12283
|
-
text: 'Add steps in order. Each one\'s Do picker offers two kinds of step.\nCall a function is what a workflow has always been, and what a new step starts as. It runs one of your functions and binds the answer under a Result name — step1 when you leave it blank — so every step after it can use the value in an expression. You can compose an existing workflow inside a function or variable, and vice versa; workflows are composable.\nEverything else in the picker is a step from the actions builder — write to or update a dataset, send an email, notify site admins, enroll the contact in a list, assign a campaign, send a webhook, the CRM steps, and the flow steps below. They take the same fields, the same Only if condition, and the same plan tiers they take in the actions builder: server-side steps
|
|
12283
|
+
text: 'Add steps in order. Each one\'s Do picker offers two kinds of step.\nCall a function is what a workflow has always been, and what a new step starts as. It runs one of your functions and binds the answer under a Result name — step1 when you leave it blank — so every step after it can use the value in an expression. You can compose an existing workflow inside a function or variable, and vice versa; workflows are composable.\nEverything else in the picker is a step from the actions builder — write to or update a dataset, send an email, notify site admins, enroll the contact in a list, assign a campaign, send a webhook, the CRM steps, and the flow steps below. They take the same fields, the same Only if condition, and the same plan tiers they take in the actions builder: server-side steps, a webhook and custom JS are Pro+, and the CRM steps need the CRM.\nThe in-page effects — menus, drawers, class toggles, redirects, analytics events — are not offered. A workflow runs on a server event, and there is no page open to perform them on. If you need one, build it as an action instead.\nWait, and ending early {#waiting}\nThe three flow steps make a workflow a sequence rather than a single burst, and they behave exactly as they do in an action:\n- Wait holds for anything from a minute to 90 days. Everything before it runs at once; the rest picks up later, with the results your function calls had already bound still in scope.\n- Wait for something to happen continues as soon as the event you pick happens for that person, or when the timeout you set runs out. Set an Only if condition of waitTimedOut is not empty on the next step to tell the clock from the event.\n- End the flow here stops the rest. With an Only if condition it is a branch.\nA waiting workflow needs to know who it is waiting f'
|
|
12284
12284
|
},
|
|
12285
12285
|
{
|
|
12286
12286
|
path: '/marketing-and-automation/workflows-and-actions/build-a-workflow',
|
|
@@ -12364,7 +12364,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
12364
12364
|
title: 'Automation',
|
|
12365
12365
|
heading: '',
|
|
12366
12366
|
anchor: '',
|
|
12367
|
-
text: 'Automation\nAutomate what happens on your site. The section holds three tabs — Workflows, Actions and Webhooks — over one engine. A workflow step is either a call to one of your functions or any of the steps the actions builder offers, so "write to a dataset, send an email, update the contact" is a sequence of one workflow rather than two automations that have to find each other. Webhooks connect Aglyn to outside systems.\nThe two tabs are two ways into the same steps, kept apart by what they run on:\n| | What starts it | What it can do |\n| Workflows | a server event — a form submission, a booking, a new member, a CRM event | function calls and every server-side step |\n| Actions | the same server events, and what a visitor does on the page — a click, a hover, exit intent, a scroll depth | everything a workflow can do, plus the in-page effects |\nSo an automation that touches the page is an action; one triggered by something that happened on the server is a workflow; and the steps in between are the same steps. Nothing you have already built moves or changes.\nPlan availability Basic in-page interactions (menu/drawer open-close, show/hide, class toggles, sticky nav, navigation, site alerts) are on every plan and never metered. The automations engine — server-side steps, analytics, overlays, and custom JS — is Pro+ with metered runs per
|
|
12367
|
+
text: 'Automation\nAutomate what happens on your site. The section holds three tabs — Workflows, Actions and Webhooks — over one engine. A workflow step is either a call to one of your functions or any of the steps the actions builder offers, so "write to a dataset, send an email, update the contact" is a sequence of one workflow rather than two automations that have to find each other. Webhooks connect Aglyn to outside systems.\nThe two tabs are two ways into the same steps, kept apart by what they run on:\n| | What starts it | What it can do |\n| Workflows | a server event — a form submission, a booking, a new member, a CRM event | function calls and every server-side step |\n| Actions | the same server events, and what a visitor does on the page — a click, a hover, exit intent, a scroll depth | everything a workflow can do, plus the in-page effects |\nSo an automation that touches the page is an action; one triggered by something that happened on the server is a workflow; and the steps in between are the same steps. Nothing you have already built moves or changes.\nPlan availability Basic in-page interactions (menu/drawer open-close, show/hide, class toggles, sticky nav, navigation, site alerts) are on every plan and never metered. The automations engine — server-side steps, analytics, overlays, and custom JS — is Pro+ with metered runs per plan. Webhooks are Pro+ too.'
|
|
12368
12368
|
},
|
|
12369
12369
|
{
|
|
12370
12370
|
path: '/marketing-and-automation/workflows-and-actions/overview',
|
|
@@ -12385,7 +12385,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
12385
12385
|
title: 'Automation',
|
|
12386
12386
|
heading: 'Webhooks',
|
|
12387
12387
|
anchor: '#webhooks',
|
|
12388
|
-
text: 'Outbound and inbound webhooks let Aglyn notify other systems and receive events from them. Webhooks are
|
|
12388
|
+
text: 'Outbound and inbound webhooks let Aglyn notify other systems and receive events from them. Webhooks are included from Pro.'
|
|
12389
12389
|
},
|
|
12390
12390
|
{
|
|
12391
12391
|
path: '/marketing-and-automation/workflows-and-actions/overview',
|
|
@@ -12413,7 +12413,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
12413
12413
|
title: 'Webhooks',
|
|
12414
12414
|
heading: '',
|
|
12415
12415
|
anchor: '',
|
|
12416
|
-
text: 'Webhooks\nWebhooks connect Aglyn to the outside world. Outbound webhooks notify another system when something happens on your site; inbound webhooks let another system trigger something in Aglyn.\nPlan availability
|
|
12416
|
+
text: 'Webhooks\nWebhooks connect Aglyn to the outside world. Outbound webhooks notify another system when something happens on your site; inbound webhooks let another system trigger something in Aglyn.\nPlan availability Pro and up. Webhooks are included from Pro.'
|
|
12417
12417
|
},
|
|
12418
12418
|
{
|
|
12419
12419
|
path: '/marketing-and-automation/workflows-and-actions/webhooks',
|
|
@@ -12448,35 +12448,35 @@ export const DOCS_SECTION_INDEX = [
|
|
|
12448
12448
|
title: 'Add-ons',
|
|
12449
12449
|
heading: '',
|
|
12450
12450
|
anchor: '',
|
|
12451
|
-
text: 'Add-ons\nAdd-ons let you buy more of a specific thing without
|
|
12451
|
+
text: 'Add-ons\nAdd-ons let you buy more of a specific thing without changing plan. On Pro they are how the plan grows: there is no larger self-serve plan above it, and no ceiling on how many seats, collaborators or datasets a Pro workspace can add. They bill as extra line items on your existing subscription, prorate onto your current billing period, and take effect immediately.\nManage them on Billing → Add-ons (requires the billing.manage permission and an active plan subscription — add-ons ride your plan\'s subscription, so Free workspaces pick a plan first).'
|
|
12452
12452
|
},
|
|
12453
12453
|
{
|
|
12454
12454
|
path: '/workspace-and-billing/billing-and-plans/add-ons',
|
|
12455
12455
|
title: 'Add-ons',
|
|
12456
12456
|
heading: 'What you can add',
|
|
12457
12457
|
anchor: '#what-you-can-add',
|
|
12458
|
-
text: 'Buy extra capacity for the whole workspace on the Plan add-ons card under Billing → Plan: manager seats, datasets and extra sites apply straight away, while collaborator seats and POS registers become pools you then assign to a site.\nPrices live on one page Per-unit add-on prices are on aglyn.com/pricing, and what YOUR workspace would pay is shown in Billing before you confirm. This page covers what each add-on does and how it is billed; restating the numbers here would just be a second copy to keep in step.\n| Add-on | What it does | How it is priced |\n| Manager seats | Workspace manager seats beyond the included count | Per seat, per month — cheaper on
|
|
12458
|
+
text: 'Buy extra capacity for the whole workspace on the Plan add-ons card under Billing → Plan: manager seats, datasets and extra sites apply straight away, while collaborator seats and POS registers become pools you then assign to a site.\nPrices live on one page Per-unit add-on prices are on aglyn.com/pricing, and what YOUR workspace would pay is shown in Billing before you confirm. This page covers what each add-on does and how it is billed; restating the numbers here would just be a second copy to keep in step.\n| Add-on | What it does | How it is priced |\n| Manager seats | Workspace manager seats beyond the included count | Per seat, per month — cheaper on Pro |\n| Collaborator seats | Per-site collaborator (teammate) seats beyond the included count | Per seat, per month — cheaper on Pro |\n| Extra datasets | Additional shared datasets across the workspace | Per dataset, per month |\n| Extra sites | Publish more sites than your plan includes | Per site, per month — the same on every paid plan |\n| POS registers | One extra point-of-sale register, assigned to one site | Flat per register, per month — the same on every plan |\n| Event Calendar | The event manager + calendar elements, workspace-wide | Flat per month — the same on every plan |\n| AI credits | Blocks of 5,000 AI credits a month added to your plan\'s own, workspace-wide, up to 30 blocks | Per block, per month — the same on every paid plan |\n| Site Care | Our team makes your small site changes for you, about an hour of work a month, workspace-wide | Flat per month — the same on every paid plan |\n- Prices are per unit per month. On annual billing, add-ons bill yearly alongside your plan (12× the monthly price) — a subscription has one billing interval.\n- POS registers also require a plan with POS (Pro or Custom), and eac'
|
|
12459
12459
|
},
|
|
12460
12460
|
{
|
|
12461
12461
|
path: '/workspace-and-billing/billing-and-plans/add-ons',
|
|
12462
12462
|
title: 'Add-ons',
|
|
12463
12463
|
heading: 'Assigning register seats',
|
|
12464
12464
|
anchor: '#assigning-register-seats',
|
|
12465
|
-
text: 'Unlike every other add-on, a POS register seat is bought once for your workspace and then assigned to one site. Buying a seat does not raise the register limit everywhere — it adds one register\'s worth of capacity that you place where you need it.\nYour plan already gives every site a register allowance on its own (
|
|
12465
|
+
text: 'Unlike every other add-on, a POS register seat is bought once for your workspace and then assigned to one site. Buying a seat does not raise the register limit everywhere — it adds one register\'s worth of capacity that you place where you need it.\nYour plan already gives every site a register allowance on its own (1 on Pro). A seat is added on top of that, for the one site you assign it to.\nTo assign one, go to Billing → POS register seats, directly under Plan add-ons. The card shows how many seats you\'ve purchased, how many are assigned, and how many are unassigned, then lets you add or remove seats per site.\n- Seats are reassignable. Moving a seat between sites is immediate and costs nothing — you\'re not buying or canceling anything, just relocating capacity.\n- Taking a seat off a busy site doesn\'t delete anything. If the site is running more registers than it can after the move, the extra ones stay set up but stop taking sales until you assign seats back or remove them. The console warns you before the move, with the number affected.\n- Deleting a site returns its seats to the pool automatically, in the same action that removes the site. There\'s nothing to reclaim by hand.\n- You need the Manage billing permission to move seats, the same permission that buys them.\nIf every purchased seat is already assigned and a site needs another register, either move a seat off a site that isn\'t using it, or buy another seat under Plan add-ons.'
|
|
12466
12466
|
},
|
|
12467
12467
|
{
|
|
12468
12468
|
path: '/workspace-and-billing/billing-and-plans/add-ons',
|
|
12469
12469
|
title: 'Add-ons',
|
|
12470
12470
|
heading: 'Assigning collaborator seats',
|
|
12471
12471
|
anchor: '#assigning-collaborator-seats',
|
|
12472
|
-
text: 'Collaborator seats work exactly like register seats: a seat is bought once for your workspace and then assigned to one site. Buying a seat does not raise the collaborator limit on every site — it adds one site\'s worth of capacity that you place where you need it.\nYour plan already gives every site a collaborator allowance on its own. A purchased seat is added on top of that, for the one site you assign it to
|
|
12472
|
+
text: 'Collaborator seats work exactly like register seats: a seat is bought once for your workspace and then assigned to one site. Buying a seat does not raise the collaborator limit on every site — it adds one site\'s worth of capacity that you place where you need it.\nYour plan already gives every site a collaborator allowance on its own. A purchased seat is added on top of that, for the one site you assign it to. On Starter that stops at the plan\'s per-site maximum, and past it the path is Pro; Pro has no maximum.\nTo assign one, go to Billing → Site collaborator seats, directly under Plan add-ons. The card shows how many seats you\'ve purchased, how many are assigned, and how many are unassigned, then lets you add or remove seats per site. The same numbers appear on each site\'s own Collaborators card.\n- Seats are reassignable. Moving a seat between sites is immediate and costs nothing — you\'re not buying or canceling anything, just relocating capacity.\n- Nobody is ever removed for being over the limit. If a site has more collaborators than its limit — because a seat moved, a plan changed, or the limit was corrected — everyone on it keeps their access and stays signed in. The only effect is that the site can\'t take on another collaborator until it\'s back under. The console warns you before a move that would leave a site over, with the number affected.\n- Deleting a site returns its seats to the pool automatically, in the same action that removes the site. There\'s nothing to reclaim by hand.\n- You need the Manage billing permission to move seats, the same permission that buys them.\nIf every purchased seat is already assigned and a site needs another collaborator, either move a seat off a site that isn\'t using it, or buy another seat under Plan add-ons.'
|
|
12473
12473
|
},
|
|
12474
12474
|
{
|
|
12475
12475
|
path: '/workspace-and-billing/billing-and-plans/add-ons',
|
|
12476
12476
|
title: 'Add-ons',
|
|
12477
|
-
heading: 'Aglyn AI',
|
|
12477
|
+
heading: 'Aglyn AI and AI credits',
|
|
12478
12478
|
anchor: '#aglyn-ai',
|
|
12479
|
-
text: 'Every plan\'s included AI credits pay for all of Aglyn AI: the assistant\'s answers and building for you — pages, components, emails, campaigns, products and more.
|
|
12479
|
+
text: 'Every plan\'s included AI credits pay for all of Aglyn AI: the assistant\'s answers and building for you — pages, components, emails, campaigns, products and more. The AI credits add-on adds more on top, every month, in blocks of 5,000 credits. Choose how many blocks in the AI credits row of the Plan add-ons card under Billing → Plan, the same way you add seats; the change is shown with what it costs before you confirm it. What each AI door does is under Aglyn AI.\n- One add-on, sold by the block. Each block adds 5,000 credits a month, up to 30 blocks (see AI credits). Any paid plan can add blocks, at the same price per block, and changing your plan keeps them. The price is on aglyn.com/pricing and in Billing before you confirm; on annual billing blocks bill yearly with the plan, like every add-on. Custom workspaces carry more AI in their agreement instead.\n- Everything it builds is a draft. Aglyn AI cannot publish a page, change a live one or send an email. It writes drafts and unpublished versions, which a person reviews and publishes through the buttons that already exist — see the draft rule.\n- One pool, one meter. Blocks add their credits to the credits your plan already includes. There is no second meter: the AI credits meter on Billing → Usage shows your plan\'s credits and your blocks\' as one figure, and the same overage rate, stop switch and monthly ceiling apply to the whole pool — see AI credits and overage.\n- Adding blocks is charged now, prorated for the rest of the period, like a plan upgrade. Removing blocks takes effect at the end of the period you already paid for, like a plan downgrade. Then the pool shrinks back to your plan\'s own credits plus the blocks you kept; what the assistant already built stays exactly as it is.\n- Free workspaces cannot add blocks'
|
|
12480
12480
|
},
|
|
12481
12481
|
{
|
|
12482
12482
|
path: '/workspace-and-billing/billing-and-plans/add-ons',
|
|
@@ -12490,7 +12490,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
12490
12490
|
title: 'Add-ons',
|
|
12491
12491
|
heading: 'How changes bill',
|
|
12492
12492
|
anchor: '#how-changes-bill',
|
|
12493
|
-
text: '- Adding units shows a prorated preview of today\'s charge before you confirm. It is charged to your card when you confirm, and the units are yours as soon as that payment goes through — if your bank asks you to confirm it, Billing shows the check right there.\n- Removing units charges nothing and refunds nothing: you keep them until the end of the period you already paid for, and they drop off then.\nAdd-ons are not on the plan-switch schedule Adding an add-on works like a plan upgrade: charged today, prorated, and applied once paid. Removing one works like a plan downgrade: nothing today, and it ends at your period end. See when each change takes effect.\n- Hard caps: seat and dataset add-ons stop at
|
|
12493
|
+
text: '- Adding units shows a prorated preview of today\'s charge before you confirm. It is charged to your card when you confirm, and the units are yours as soon as that payment goes through — if your bank asks you to confirm it, Billing shows the check right there.\n- Removing units charges nothing and refunds nothing: you keep them until the end of the period you already paid for, and they drop off then.\nAdd-ons are not on the plan-switch schedule Adding an add-on works like a plan upgrade: charged today, prorated, and applied once paid. Removing one works like a plan downgrade: nothing today, and it ends at your period end. See when each change takes effect.\n- Hard caps on Starter only: Starter\'s seat and dataset add-ons stop at the plan\'s maximum (5 workspace managers, for example), and past it the answer is Pro, which has no maximum — the Billing page tells you when you\'re there.'
|
|
12494
12494
|
},
|
|
12495
12495
|
{
|
|
12496
12496
|
path: '/workspace-and-billing/billing-and-plans/add-ons',
|
|
@@ -12518,7 +12518,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
12518
12518
|
title: 'Bandwidth',
|
|
12519
12519
|
heading: 'What each plan includes',
|
|
12520
12520
|
anchor: '#what-each-plan-includes',
|
|
12521
|
-
text: '| Plan | Included bandwidth per month | Past the allowance |\n| Free | 2 GB | Sites are paused until the start of next month |\n| Starter |
|
|
12521
|
+
text: '| Plan | Included bandwidth per month | Past the allowance |\n| Free | 2 GB | Sites are paused until the start of next month |\n| Starter | 15 GB | Keeps serving; the extra is billed |\n| Pro | 25 GB | Keeps serving; the extra is billed |\n| Custom | Set by your agreement | Keeps serving; not billed — your agreement sets the terms |\nThe allowance is per organization, across every site in it — not per site. If you run four sites on one Pro plan (three included and one extra), they share the 25 GB.'
|
|
12522
12522
|
},
|
|
12523
12523
|
{
|
|
12524
12524
|
path: '/workspace-and-billing/billing-and-plans/bandwidth',
|
|
@@ -12616,7 +12616,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
12616
12616
|
title: 'Billing & Plans',
|
|
12617
12617
|
heading: '',
|
|
12618
12618
|
anchor: '',
|
|
12619
|
-
text: 'Billing & Plans\nYour plan determines which features you can use and how much of each. Aglyn checks entitlements (can you use a feature) and quotas (how much) throughout the product, and shows usage meters so you always know where you stand.\nPlan availability Every site has a plan. Free, Starter, Pro, Business, Scale, Advanced
|
|
12619
|
+
text: 'Billing & Plans\nYour plan determines which features you can use and how much of each. Aglyn checks entitlements (can you use a feature) and quotas (how much) throughout the product, and shows usage meters so you always know where you stand.\nPlan availability Every site has a plan. There are four: Free, Starter, Pro and Custom. Free and Starter are for one site; Pro is the full platform, and grows past its included amounts through add-ons and metered usage; Custom, quoted for you, adds white-label, single sign-on and a support commitment.\nPlans retired in November 2026 Business, Scale, Advanced and Agency are no longer sold. Every feature Business carried is now in Pro, and what Agency added on top of it, white-label among it, is on Custom. The plan once labeled Enterprise is now called Custom; what it includes has not changed.'
|
|
12620
12620
|
},
|
|
12621
12621
|
{
|
|
12622
12622
|
path: '/workspace-and-billing/billing-and-plans/overview',
|
|
@@ -12630,7 +12630,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
12630
12630
|
title: 'Billing & Plans',
|
|
12631
12631
|
heading: 'Tiers & entitlements',
|
|
12632
12632
|
anchor: '#tiers--entitlements',
|
|
12633
|
-
text: 'Prices live on one page Current prices — monthly, annual, transaction fees and per-unit overage rates — are on aglyn.com/pricing, and your own plan and next invoice are in Billing in the console. This page explains how billing WORKS; it deliberately does not restate the numbers, because a second copy is a copy that goes stale.\n| Plan |
|
|
12633
|
+
text: 'Prices live on one page Current prices — monthly, annual, transaction fees and per-unit overage rates — are on aglyn.com/pricing, and your own plan and next invoice are in Billing in the console. This page explains how billing WORKS; it deliberately does not restate the numbers, because a second copy is a copy that goes stale.\n| Plan | What it is for |\n| Free | One site to build and publish — no selling, no custom domain |\n| Starter | One site with your own domain, a store, bookings and the CRM, with the highest transaction fee |\n| Pro | The full platform: unlimited pages, products, forms, workflows and dataset records, POS, video, recurring billing, members-only content, gift cards, A/B testing, multilingual sites, scheduled publishing, the API and webhooks |\n| Custom | Everything in Pro, plus white-label, single sign-on, a dedicated support commitment, no transaction fee, and limits set by agreement |\nPro grows by add-ons, not by changing plan. It includes three sites and a set amount of storage, bandwidth, team seats, collaborators, datasets, CRM records, email, workflow runs, API requests and AI credits. Past any of them you buy more — an extra site, seat or dataset from Add-ons — or the extra usage is metered on your invoice. There is no ceiling on how many seats, collaborators or datasets a Pro workspace can add.\nTransaction fees are Aglyn platform fees on the sales you take through your site — storefront orders, recurring billing and paid bookings alike — separate from Stripe\'s payment-processing fees. Pro\'s are lower than Starter\'s, and Custom has none.\nEvery plan also includes an amount of monthly traffic — 2 GB on Free, more on each paid plan, and on Custom whatever the agreement sets. Passing it is metered and billed on Starter and Pro, and pauses the site un'
|
|
12634
12634
|
},
|
|
12635
12635
|
{
|
|
12636
12636
|
path: '/workspace-and-billing/billing-and-plans/overview',
|
|
@@ -12644,14 +12644,14 @@ export const DOCS_SECTION_INDEX = [
|
|
|
12644
12644
|
title: 'Billing & Plans',
|
|
12645
12645
|
heading: 'Storage overage',
|
|
12646
12646
|
anchor: '#storage-overage',
|
|
12647
|
-
text: 'Your plan includes an amount of storage for each of its sites, and the workspace shares it as one allowance: every site\'s media library, the organization library, and the files kept with quotes and forms draw on the same total. On a paid plan, going past it is not a wall:\n- Uploads keep working. You are never stopped from adding files because you reached your included storage.\n- The extra storage is billed on your monthly invoice at our infrastructure cost plus 30%, kept after card fees — the exact per-GB rate is on the pricing page and in Billing → Storage cap.\n- We tell you before it happens. You get an alert as you approach your included storage and another when you cross it, so the invoice is never the first you hear of it. See usage meters.\nIf you would rather uploads stopped\nSet a monthly storage cap on the Storage cap card under Billing → Usage when you would rather new uploads stopped than pay for extra storage past a figure you choose. This is optional and off unless you choose it. Once a month\'s storage overage would pass the amount you set, new uploads are refused and you are never billed above that number.\nYou can change or remove the cap at any time, including while you are over your included allowance. Nothing is ever deleted — a cap only affects new uploads, and removing one takes effect immediately.\nFree plans are never billed for storage On the Free plan there is no storage overage at all. Your included storage is a fixed cap, shared the same way: your uploads stop when the workspace reaches it, wherever they are going, nothing is metered, and no amount of usage produces a charge — so there is nothing to cap and nothing to configure.
|
|
12647
|
+
text: 'Your plan includes an amount of storage for each of its sites, and the workspace shares it as one allowance: every site\'s media library, the organization library, and the files kept with quotes and forms draw on the same total. On a paid plan, going past it is not a wall:\n- Uploads keep working. You are never stopped from adding files because you reached your included storage.\n- The extra storage is billed on your monthly invoice at our infrastructure cost plus 30%, kept after card fees — the exact per-GB rate is on the pricing page and in Billing → Storage cap.\n- We tell you before it happens. You get an alert as you approach your included storage and another when you cross it, so the invoice is never the first you hear of it. See usage meters.\nIf you would rather uploads stopped\nSet a monthly storage cap on the Storage cap card under Billing → Usage when you would rather new uploads stopped than pay for extra storage past a figure you choose. This is optional and off unless you choose it. Once a month\'s storage overage would pass the amount you set, new uploads are refused and you are never billed above that number.\nYou can change or remove the cap at any time, including while you are over your included allowance. Nothing is ever deleted — a cap only affects new uploads, and removing one takes effect immediately.\nFree plans are never billed for storage On the Free plan there is no storage overage at all. Your included storage is a fixed cap, shared the same way: your uploads stop when the workspace reaches it, wherever they are going, nothing is metered, and no amount of usage produces a charge — so there is nothing to cap and nothing to configure. Custom storage is a fixed amount set by the agreement, with no overage either: uploads stop there. Files your customers s'
|
|
12648
12648
|
},
|
|
12649
12649
|
{
|
|
12650
12650
|
path: '/workspace-and-billing/billing-and-plans/overview',
|
|
12651
12651
|
title: 'Billing & Plans',
|
|
12652
12652
|
heading: 'AI assist overage',
|
|
12653
12653
|
anchor: '#assist-overage',
|
|
12654
|
-
text: 'Paid plans include a monthly band of AI assist credits — the Aglyn Assist credits meter on the billing page shows how much of it this month\'s assistant use has drawn. The included credits pay for every AI request, building included, and
|
|
12654
|
+
text: 'Paid plans include a monthly band of AI assist credits — the Aglyn Assist credits meter on the billing page shows how much of it this month\'s assistant use has drawn. The included credits pay for every AI request, building included, and blocks of AI credits add credits on top; it is one pool, so everything below applies to the widened band as a whole. What the credits are spent on, and what each kind of request costs relative to the others, is under Aglyn AI. On a plan that sells credits past the band, reaching it is not a wall:\n- The assistant keeps answering. Nothing stops because you reached your included credits.\n- The extra credits are billed on your monthly invoice, per 1,000 credits over the band, at your plan\'s rate — the exact figure is on the pricing page and in Billing → Usage → AI assist overage.\nIf you would rather the assistant stopped {#stop-ai-assist-at-the-included-band}\nTurn on Stop AI assist at the included band in Billing → Usage → AI assist overage. This is optional and off unless you choose it. Once it is on, the assistant refuses once the included credits are used — the refusal names this switch and where it lives — and you are never billed for AI assist. Turn it off at any time to keep going at your plan\'s rate; either change takes effect on the next message. Changing it needs the Manage billing permission.\nIf you would rather it kept going, up to a figure you choose {#ai-overage-ceiling}\nWith the switch off, the same card offers a monthly ceiling on the extra credits you will pay for: Stop AI when this month\'s overage reaches a dollar figure you type. Once the month\'s overage — the extra credits priced at your plan\'s rate, exactly as the invoice would price them — reaches that figure, the assistant stops for the rest of the month, and the refusa'
|
|
12655
12655
|
},
|
|
12656
12656
|
{
|
|
12657
12657
|
path: '/workspace-and-billing/billing-and-plans/overview',
|
|
@@ -12665,28 +12665,28 @@ export const DOCS_SECTION_INDEX = [
|
|
|
12665
12665
|
title: 'Billing & Plans',
|
|
12666
12666
|
heading: 'Seats',
|
|
12667
12667
|
anchor: '#seats',
|
|
12668
|
-
text: '- Team seats (workspace-wide) and per-site collaborator seats are metered and enforced per tier — seats cover the people who build and manage your sites.\n- Buy paid seat add-ons to grow your team beyond the included seats — self-serve from Billing → Add-ons, alongside extra sites, datasets, POS registers, the Event Calendar, and
|
|
12668
|
+
text: '- Team seats (workspace-wide) and per-site collaborator seats are metered and enforced per tier — seats cover the people who build and manage your sites.\n- Buy paid seat add-ons to grow your team beyond the included seats — self-serve from Billing → Add-ons, alongside extra sites, datasets, POS registers, the Event Calendar, and AI credits. On Pro there is no ceiling on how many seats you add.\n- Site member accounts are not seats: visitors who sign up to your published site are unlimited on every plan.\n- Aglyn staff take no seat, whether they built the workspace or joined it to help. See Aglyn staff on your team.'
|
|
12669
12669
|
},
|
|
12670
12670
|
{
|
|
12671
12671
|
path: '/workspace-and-billing/billing-and-plans/overview',
|
|
12672
12672
|
title: 'Billing & Plans',
|
|
12673
12673
|
heading: 'CRM records',
|
|
12674
12674
|
anchor: '#crm-records',
|
|
12675
|
-
text: 'Your CRM — the contacts captured from forms, member sign-ups, buyers and bookings, and the companies and deals your team files beside them — is priced as one CRM records band, not a hard cap. A record is a contact, a company or a deal; tasks, logged activities, pipelines and custom fields are not counted.\n- Each
|
|
12675
|
+
text: 'Your CRM — the contacts captured from forms, member sign-ups, buyers and bookings, and the companies and deals your team files beside them — is priced as one CRM records band, not a hard cap. A record is a contact, a company or a deal; tasks, logged activities, pipelines and custom fields are not counted.\n- Each plan includes a band: Free 100, Starter 1,000 and Pro 10,000 records; on Custom the agreement sets it.\n- On Starter and Pro, growing past the band never blocks or drops anything — extra records are metered overage on your monthly invoice, at a per-1,000 rate that is lower on Pro — see pricing for the current rate on your plan, per extra 1,000 records per month.\n- On Free, which includes no CRM, the band is a hard limit on capture: past 100 records a site adds no new person — a new visitor keeps their member account and orders, but no contact is kept — and the count of missed captures is recorded. On Billing → Usage the band reads Stored records (organization), captioned At this limit your sites stop adding new people. Working with them is part of the CRM, included from Starter. The Free plan card names no CRM records.\n- The billed count is the size of your CRM at the end of the month, not its size on any other day. The three collections are a running total rather than a monthly tally, so a month has to be charged on one moment in it, and that moment is the last daily reading taken before the month closes. Records added after a month ends belong to the new month; records deleted after it ends do not undo the month that already ran.\n- On a plan with the CRM, the billing page\'s CRM records (organization) meter shows the total against your band, with the contacts, companies and deals it is made of beneath it.\nThe CRM {#the-crm-suite}\nThe CRM is included from Starter'
|
|
12676
12676
|
},
|
|
12677
12677
|
{
|
|
12678
12678
|
path: '/workspace-and-billing/billing-and-plans/overview',
|
|
12679
12679
|
title: 'Billing & Plans',
|
|
12680
12680
|
heading: 'Organization data',
|
|
12681
12681
|
anchor: '#organization-data',
|
|
12682
|
-
text: '- Datasets are organization-scoped: counts and storage meter against your organization, not individual sites.\n- Each paid
|
|
12682
|
+
text: '- Datasets are organization-scoped: counts and storage meter against your organization, not individual sites.\n- Each paid plan includes a number of datasets and an included data storage size (Starter 512 MB, Pro 2 GB; on Custom the agreement sets both).\n- Extra datasets are a monthly add-on, with no ceiling on how many a Pro workspace adds; storage beyond the included size is metered overage, billed per GB-month on your monthly invoice.\n- Records per dataset are capped on Starter and unlimited on Pro.\n- The billed size is what you were storing at the end of the month, on the same basis as the audience band above: the last daily reading taken before the month closes. Clearing datasets after a month has ended lowers the next invoice, not the one for the month that just finished.'
|
|
12683
12683
|
},
|
|
12684
12684
|
{
|
|
12685
12685
|
path: '/workspace-and-billing/billing-and-plans/overview',
|
|
12686
12686
|
title: 'Billing & Plans',
|
|
12687
12687
|
heading: 'API access',
|
|
12688
12688
|
anchor: '#api-access',
|
|
12689
|
-
text: 'The customer REST API is
|
|
12689
|
+
text: 'The customer REST API is included on Pro and Custom — mint scoped API keys and call the versioned /v1 endpoints from anywhere. Requests are metered per organization:\n| Plan | Included requests / month | Overage |\n| Pro | 1,500 | Metered per additional 1,000 |\n| Custom | Set by your agreement | — |\n- Requests past the included quota keep working and bill as metered overage on your monthly invoice — never a hard wall mid-integration.\n- The billing page shows an API requests meter, and the usage-cap banner warns at 80% and 100% of the included quota.\n- Only requests that pass authentication and the rate limit are counted — rejected calls (bad key, wrong plan, rate-limited) are never billed.'
|
|
12690
12690
|
},
|
|
12691
12691
|
{
|
|
12692
12692
|
path: '/workspace-and-billing/billing-and-plans/overview',
|
|
@@ -12714,7 +12714,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
12714
12714
|
title: 'Import and export',
|
|
12715
12715
|
heading: 'What you can move',
|
|
12716
12716
|
anchor: '#what-you-can-move',
|
|
12717
|
-
text: 'The page lists every kind of data your workspace\'s plugins can move, grouped by plugin. A plugin your workspace doesn\'t run isn\'t listed.\n- Records are things like contacts, leads and list members. They import from CSV, JSON or NDJSON files, one row per record, and export to the same formats.\n- Packages are things you build rather than collect: sequences, campaigns, org automations, email templates and email topics. A package is one JSON file. It can hold several kinds of item together, so a sequence and the email templates it uses travel as a set.\n- Site packages hold a site\'s pages, emails, forms, theme and content. Each site has its own, under Backup & restore, linked from this page. See Site backup and packages.\nSome records belong to the whole workspace and others to one site. To work with a site\'s records, pick the site first. The site\'s own plugins decide what is listed for it.\nSome data also depends on your plan. The CRM is included from Starter, so on Free its companies, deals, tasks, activities, pipelines, custom fields and email templates are listed with the plan that includes them instead of Import and Export, and contacts and leads can\'t be imported. Exporting your contacts and leads works on every plan, here and in Settings → Privacy.\nThe same goes for every other kind of data: it moves on the plans that include its page. Datasets, bookings and redirects are included from Starter, org automations
|
|
12717
|
+
text: 'The page lists every kind of data your workspace\'s plugins can move, grouped by plugin. A plugin your workspace doesn\'t run isn\'t listed.\n- Records are things like contacts, leads and list members. They import from CSV, JSON or NDJSON files, one row per record, and export to the same formats.\n- Packages are things you build rather than collect: sequences, campaigns, org automations, email templates and email topics. A package is one JSON file. It can hold several kinds of item together, so a sequence and the email templates it uses travel as a set.\n- Site packages hold a site\'s pages, emails, forms, theme and content. Each site has its own, under Backup & restore, linked from this page. See Site backup and packages.\nSome records belong to the whole workspace and others to one site. To work with a site\'s records, pick the site first. The site\'s own plugins decide what is listed for it.\nSome data also depends on your plan. The CRM is included from Starter, so on Free its companies, deals, tasks, activities, pipelines, custom fields and email templates are listed with the plan that includes them instead of Import and Export, and contacts and leads can\'t be imported. Exporting your contacts and leads works on every plan, here and in Settings → Privacy.\nThe same goes for every other kind of data: it moves on the plans that include its page. Datasets, bookings and redirects are included from Starter, and org automations and importing gift cards from Pro (the gift cards you already have can be exported on any plan). Events need the Event Calendar add-on and sequences the Sequences add-on. Data from a plugin that is switched off for the workspace or the site isn\'t listed.'
|
|
12718
12718
|
},
|
|
12719
12719
|
{
|
|
12720
12720
|
path: '/workspace-and-billing/import-and-export',
|
|
@@ -12994,14 +12994,14 @@ export const DOCS_SECTION_INDEX = [
|
|
|
12994
12994
|
title: 'Support & community',
|
|
12995
12995
|
heading: '',
|
|
12996
12996
|
anchor: '',
|
|
12997
|
-
text: 'Support & community\nTwo ways to get help, each with its own page under Support: private support tickets with the Aglyn team, and a community forum shared with other Aglyn builders.\nOpen Support from Organization → Support, or from Support in your account menu. It lands on whichever channel your plan makes primary — the forum on Free and Starter, tickets from Pro upward — and each page links to the other, so you always have both.\nIf you were invited to a single site Support isn\'t part of a site collaborator\'s console. A ticket is a conversation between the organization and Aglyn — it isn\'t scoped to one site, and the thread is readable by the organization\'s team — so the console doesn\'t offer it to someone whose access stops at a single site.\nRaise anything you run into with whoever invited you. They can open a ticket, and because tickets belong to the organization rather than to the person who filed them, any of their teammates can carry the thread on.\nPlan availability The community forum is on every plan, including Free. Private support tickets start on Pro — Free and Starter are forum-only tiers.\nEach plan with tickets carries a first-response target, shown on the Support tickets page itself:\n| Plan | Tier | First response |\n| Free · Starter | Community | Forum only — no ticket channel |\n| Pro | Standard | 7–14 business days |\n|
|
|
12997
|
+
text: 'Support & community\nTwo ways to get help, each with its own page under Support: private support tickets with the Aglyn team, and a community forum shared with other Aglyn builders.\nOpen Support from Organization → Support, or from Support in your account menu. It lands on whichever channel your plan makes primary — the forum on Free and Starter, tickets from Pro upward — and each page links to the other, so you always have both.\nIf you were invited to a single site Support isn\'t part of a site collaborator\'s console. A ticket is a conversation between the organization and Aglyn — it isn\'t scoped to one site, and the thread is readable by the organization\'s team — so the console doesn\'t offer it to someone whose access stops at a single site.\nRaise anything you run into with whoever invited you. They can open a ticket, and because tickets belong to the organization rather than to the person who filed them, any of their teammates can carry the thread on.\nPlan availability The community forum is on every plan, including Free. Private support tickets start on Pro — Free and Starter are forum-only tiers.\nEach plan with tickets carries a first-response target, shown on the Support tickets page itself:\n| Plan | Tier | First response |\n| Free · Starter | Community | Forum only — no ticket channel |\n| Pro | Standard | 7–14 business days |\n| Custom | Dedicated | 24–48 hours, plus a named success manager |\nCustom, the plan once labeled Enterprise, is measured in clock hours rather than business days, so a ticket opened on Friday is still answered over the weekend. The target is the upper bound of the range, measured to our first reply — not to resolution. See Billing & plans.'
|
|
12998
12998
|
},
|
|
12999
12999
|
{
|
|
13000
13000
|
path: '/workspace-and-billing/support-and-community',
|
|
13001
13001
|
title: 'Support & community',
|
|
13002
13002
|
heading: 'Support tickets',
|
|
13003
13003
|
anchor: '#support-tickets',
|
|
13004
|
-
text: 'At Organization → Support → Support tickets.\nA ticket is a private conversation between your organization and Aglyn staff. Anyone in the organization can open one and follow the thread.\nOn Free and Starter this page explains where ticket support starts and points you at the forum instead — it never offers a New ticket button the server would refuse.\n1. Choose New ticket.\n2. Give it a Subject (up to 150 characters) and describe what\'s going on in the message body (up to 5,000 characters).\n3. Submit. The ticket appears in your list marked open, and Aglyn staff are notified immediately.\nOpen a ticket from the list to read the thread and reply. Each message shows who sent it, so a staff reply is always distinguishable from your own.\nYour tickets {#your-tickets}\nThe Your tickets card lists every ticket your organization has opened, each marked open or closed, under the first-response target your plan carries. Choose New ticket to start one, or Open on a ticket to read the thread and reply. On
|
|
13004
|
+
text: 'At Organization → Support → Support tickets.\nA ticket is a private conversation between your organization and Aglyn staff. Anyone in the organization can open one and follow the thread.\nOn Free and Starter this page explains where ticket support starts and points you at the forum instead — it never offers a New ticket button the server would refuse.\n1. Choose New ticket.\n2. Give it a Subject (up to 150 characters) and describe what\'s going on in the message body (up to 5,000 characters).\n3. Submit. The ticket appears in your list marked open, and Aglyn staff are notified immediately.\nOpen a ticket from the list to read the thread and reply. Each message shows who sent it, so a staff reply is always distinguishable from your own.\nYour tickets {#your-tickets}\nThe Your tickets card lists every ticket your organization has opened, each marked open or closed, under the first-response target your plan carries. Choose New ticket to start one, or Open on a ticket to read the thread and reply. On Custom the card also names your success manager, who is copied on every ticket, once one is appointed. On Free and Starter it says where ticket support starts instead.\nTicket status\n- open — with you or with Aglyn; new replies from either side keep it open.\n- closed — resolved. Either side can close a ticket, and replying to a closed ticket reopens it automatically — you never need to file a duplicate to follow up on something you thought was finished.\nTickets belong to the organization, not to the person who opened them, so a teammate can pick up a thread while you\'re away. They stay in the list after closing as a record of what was asked and answered.\nWhat to include\nSupport answers faster with the specifics: the site and page involved, what you expected versus what happened, and the '
|
|
13005
13005
|
},
|
|
13006
13006
|
{
|
|
13007
13007
|
path: '/workspace-and-billing/support-and-community',
|
|
@@ -13162,14 +13162,14 @@ export const DOCS_SECTION_INDEX = [
|
|
|
13162
13162
|
title: 'Members-only areas',
|
|
13163
13163
|
heading: '',
|
|
13164
13164
|
anchor: '',
|
|
13165
|
-
text: 'Members-only areas\nBeyond your team, your site visitors can become members — and you can restrict certain pages to signed-in members only.\nPlan availability
|
|
13165
|
+
text: 'Members-only areas\nBeyond your team, your site visitors can become members — and you can restrict certain pages to signed-in members only.\nPlan availability Three things here share the word "member", and they are on different plans:\n- Member accounts: signing up, signing in, recovering a password, and the account page with past orders. These work wherever commerce does.\n- Members-only content: members-only pages, gated video and the content paywall. These need the content-gating feature, on Pro and up. On a lower plan, or if a subscription lapses, gated content is not served.\n- Recurring billing: subscription products and paid memberships charged on a schedule. Also Pro and up.'
|
|
13166
13166
|
},
|
|
13167
13167
|
{
|
|
13168
13168
|
path: '/workspace-and-billing/teams-and-roles/members-only',
|
|
13169
13169
|
title: 'Members-only areas',
|
|
13170
13170
|
heading: 'Let visitors sign up',
|
|
13171
13171
|
anchor: '#let-visitors-sign-up',
|
|
13172
|
-
text: '
|
|
13172
|
+
text: 'Turn on User Accounts for the site so visitors can sign in / sign up. A new site starts with it on; the switch is at Sites → your site → Admin → Plugins (see Member accounts). New members flow into your CRM automatically.'
|
|
13173
13173
|
},
|
|
13174
13174
|
{
|
|
13175
13175
|
path: '/workspace-and-billing/teams-and-roles/members-only',
|
|
@@ -13183,7 +13183,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
13183
13183
|
title: 'Members-only areas',
|
|
13184
13184
|
heading: 'Gate a page',
|
|
13185
13185
|
anchor: '#gate-a-screen',
|
|
13186
|
-
text: '
|
|
13186
|
+
text: 'Members-only pages are on Pro and up.\n1. Open the page you want to protect.\n2. Mark it members-only.\n3. Publish. Only signed-in members can now view it; everyone else is prompted to sign in.'
|
|
13187
13187
|
},
|
|
13188
13188
|
{
|
|
13189
13189
|
path: '/workspace-and-billing/teams-and-roles/members-only',
|
|
@@ -13260,14 +13260,14 @@ export const DOCS_SECTION_INDEX = [
|
|
|
13260
13260
|
title: 'White-label',
|
|
13261
13261
|
heading: '',
|
|
13262
13262
|
anchor: '',
|
|
13263
|
-
text: 'White-label\nWhite-labeling replaces the Aglyn brand everywhere your organization and its sites are shown: the console your team signs in to, the sites you publish, and the transactional email your members and customers receive.\nIt is one setting card, and the fields are short. The part worth reading closely is what each field actually replaces — a few of them change a surface you never look at yourself.\nPlan availability White-labeling is the whiteLabel entitlement.
|
|
13263
|
+
text: 'White-label\nWhite-labeling replaces the Aglyn brand everywhere your organization and its sites are shown: the console your team signs in to, the sites you publish, and the transactional email your members and customers receive.\nIt is one setting card, and the fields are short. The part worth reading closely is what each field actually replaces — a few of them change a surface you never look at yourself.\nPlan availability White-labeling is the whiteLabel entitlement. One plan carries it by default: Custom, the plan once labeled Enterprise. No self-serve plan does, Pro included, and no add-on buys it.\nEntitlements can also be granted per organization on top of a plan\'s defaults, which is how a Custom agreement enables it for one organization.\nAn organization that white-labels and then downgrades reverts cleanly: the stored brand is ignored, not deleted, and the Aglyn brand comes back everywhere at once. Upgrade again and the same values return.'
|
|
13264
13264
|
},
|
|
13265
13265
|
{
|
|
13266
13266
|
path: '/workspace-and-billing/white-label',
|
|
13267
13267
|
title: 'White-label',
|
|
13268
13268
|
heading: 'Where the settings are',
|
|
13269
13269
|
anchor: '#where',
|
|
13270
|
-
text: '1. Open your organization\'s Settings page — the heading reads Organization Settings.\n2. Choose the Branding tab.\n3. The card is White-label brand.\nYou need the admin role. The Branding tab is not shown at all to members below it, so a teammate who cannot find it is looking at a shorter tab strip than you are, not at a hidden card.\nWhile your plan is still being read the card says "Checking your plan…". On a plan without the entitlement it shows an information notice
|
|
13270
|
+
text: '1. Open your organization\'s Settings page — the heading reads Organization Settings.\n2. Choose the Branding tab.\n3. The card is White-label brand.\nYou need the admin role. The Branding tab is not shown at all to members below it, so a teammate who cannot find it is looking at a shorter tab strip than you are, not at a hidden card.\nWhile your plan is still being read the card says "Checking your plan…". On a plan without the entitlement it shows an information notice pointing you to Billing instead of the editor.'
|
|
13271
13271
|
},
|
|
13272
13272
|
{
|
|
13273
13273
|
path: '/workspace-and-billing/white-label',
|
|
@@ -13281,7 +13281,7 @@ export const DOCS_SECTION_INDEX = [
|
|
|
13281
13281
|
title: 'White-label',
|
|
13282
13282
|
heading: 'Where you will see the change',
|
|
13283
13283
|
anchor: '#where-you-see-it',
|
|
13284
|
-
text: '- Console header. Your Logo URL replaces the Aglyn wordmark, and your Dark mode logo URL takes its place when the console is in dark mode. Set a Product name but no logo and the name is rendered as text in the same place instead.\n- Console theme and tab. Primary color and Favicon URL are applied to the page you are already on, so the change is visible without a reload.\n- Published sites. The site badge and the site favicon follow the same brand. The badge is white text on a dark pill in both light and dark mode, so it shows your Dark mode logo URL when you set one. A site that sets its own favicon keeps it; otherwise the site uses your favicon, and your Dark mode favicon URL in a dark browser.\n- Email stays on the light logo. Mail clients paint a light background and do not reliably honor dark mode, so Email logo URL has no dark partner.\n- Site fingerprint. The tag and the x-powered-by header that otherwise credit Aglyn are suppressed on a white-label organization\'s published sites. This one is worth knowing about because it is invisible in a browser and is the part a technically curious visitor would otherwise read.\n- Transactional email. Covered in its own section next.\nOne counter-intuitive rule governs all of it: the branded chrome activates only once you have actually set a product name or a logo, not the moment your plan grants the entitlement.
|
|
13284
|
+
text: '- Console header. Your Logo URL replaces the Aglyn wordmark, and your Dark mode logo URL takes its place when the console is in dark mode. Set a Product name but no logo and the name is rendered as text in the same place instead.\n- Console theme and tab. Primary color and Favicon URL are applied to the page you are already on, so the change is visible without a reload.\n- Published sites. The site badge and the site favicon follow the same brand. The badge is white text on a dark pill in both light and dark mode, so it shows your Dark mode logo URL when you set one. A site that sets its own favicon keeps it; otherwise the site uses your favicon, and your Dark mode favicon URL in a dark browser.\n- Email stays on the light logo. Mail clients paint a light background and do not reliably honor dark mode, so Email logo URL has no dark partner.\n- Site fingerprint. The tag and the x-powered-by header that otherwise credit Aglyn are suppressed on a white-label organization\'s published sites. This one is worth knowing about because it is invisible in a browser and is the part a technically curious visitor would otherwise read.\n- Transactional email. Covered in its own section next.\nOne counter-intuitive rule governs all of it: the branded chrome activates only once you have actually set a product name or a logo, not the moment your plan grants the entitlement. A Custom organization that has never opened this card keeps the plain Aglyn wordmark — there is no half-branded state and no flash of one brand turning into the other.'
|
|
13285
13285
|
},
|
|
13286
13286
|
{
|
|
13287
13287
|
path: '/workspace-and-billing/white-label',
|