@aglyn/aglyn 1.24.0 → 1.26.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (54) hide show
  1. package/package.json +11 -11
  2. package/src/lib/app-utils/activity-labels.js +4 -1
  3. package/src/lib/app-utils/activity-labels.js.map +1 -1
  4. package/src/lib/app-utils/bandwidth-cap.d.ts +99 -1
  5. package/src/lib/app-utils/bandwidth-cap.js +148 -4
  6. package/src/lib/app-utils/bandwidth-cap.js.map +1 -1
  7. package/src/lib/app-utils/business-details.d.ts +5 -0
  8. package/src/lib/app-utils/business-details.js +4 -0
  9. package/src/lib/app-utils/business-details.js.map +1 -1
  10. package/src/lib/app-utils/crm.d.ts +17 -30
  11. package/src/lib/app-utils/crm.js +139 -3
  12. package/src/lib/app-utils/crm.js.map +1 -1
  13. package/src/lib/app-utils/docs-help-sections.generated.js +4 -1
  14. package/src/lib/app-utils/docs-help-sections.generated.js.map +1 -1
  15. package/src/lib/app-utils/docs-help.generated.d.ts +1 -1
  16. package/src/lib/app-utils/docs-help.generated.js +7 -0
  17. package/src/lib/app-utils/docs-help.generated.js.map +1 -1
  18. package/src/lib/app-utils/docs-index.generated.js +95 -11
  19. package/src/lib/app-utils/docs-index.generated.js.map +1 -1
  20. package/src/lib/app-utils/host-tokens.d.ts +17 -0
  21. package/src/lib/app-utils/host-tokens.js +18 -0
  22. package/src/lib/app-utils/host-tokens.js.map +1 -1
  23. package/src/lib/app-utils/native-app-association.d.ts +5 -3
  24. package/src/lib/app-utils/native-app-association.js +5 -3
  25. package/src/lib/app-utils/native-app-association.js.map +1 -1
  26. package/src/lib/app-utils/native-nav.js +1 -1
  27. package/src/lib/app-utils/native-nav.js.map +1 -1
  28. package/src/lib/app-utils/notifications.js +5 -0
  29. package/src/lib/app-utils/notifications.js.map +1 -1
  30. package/src/lib/app-utils/plan-entitlements.d.ts +227 -36
  31. package/src/lib/app-utils/plan-entitlements.js +339 -45
  32. package/src/lib/app-utils/plan-entitlements.js.map +1 -1
  33. package/src/lib/app-utils/reusable-component-keys.d.ts +9 -0
  34. package/src/lib/app-utils/reusable-component-keys.js +9 -0
  35. package/src/lib/app-utils/reusable-component-keys.js.map +1 -1
  36. package/src/lib/app-utils/server.d.ts +1 -0
  37. package/src/lib/app-utils/server.js +1 -0
  38. package/src/lib/app-utils/server.js.map +1 -1
  39. package/src/lib/app-utils/sign-in-hint-cookie.d.ts +58 -0
  40. package/src/lib/app-utils/sign-in-hint-cookie.js +71 -0
  41. package/src/lib/app-utils/sign-in-hint-cookie.js.map +1 -0
  42. package/src/lib/app-utils/sign-in-visibility.d.ts +75 -0
  43. package/src/lib/app-utils/sign-in-visibility.js +79 -0
  44. package/src/lib/app-utils/sign-in-visibility.js.map +1 -0
  45. package/src/lib/app-utils/site-live-url.d.ts +4 -1
  46. package/src/lib/app-utils/site-live-url.js +17 -3
  47. package/src/lib/app-utils/site-live-url.js.map +1 -1
  48. package/src/lib/app-utils/usage-level.d.ts +50 -0
  49. package/src/lib/app-utils/usage-level.js +94 -0
  50. package/src/lib/app-utils/usage-level.js.map +1 -0
  51. package/src/lib/foundation/definitions/org-billing.types.d.ts +45 -2
  52. package/src/lib/foundation/definitions/org-billing.types.js.map +1 -1
  53. package/src/lib/foundation/definitions/platform.types.d.ts +9 -0
  54. package/src/lib/foundation/definitions/platform.types.js.map +1 -1
@@ -2643,6 +2643,27 @@ export const DOCS_SECTION_INDEX = [
2643
2643
  anchor: '#related',
2644
2644
  text: '- Copy & paste elements\n- The Besigner\n- Pages & layouts\n- Generate a reusable component with Aglyn AI'
2645
2645
  },
2646
+ {
2647
+ path: '/building-sites/besigner/show-to-signed-in-visitors',
2648
+ title: 'Show to signed-in or signed-out visitors',
2649
+ heading: '',
2650
+ anchor: '',
2651
+ text: 'Show to signed-in or signed-out visitors\nWhen your site has accounts, some things are for members and some are for everyone else: Sign in in the header for visitors and Account once they have signed in, a "Create an account" banner only for people who have not, a "Welcome back" only for those who have.'
2652
+ },
2653
+ {
2654
+ path: '/building-sites/besigner/show-to-signed-in-visitors',
2655
+ title: 'Show to signed-in or signed-out visitors',
2656
+ heading: 'Choose who sees an element',
2657
+ anchor: '#choose-who-sees-an-element',
2658
+ text: '1. Select the element on the canvas.\n2. In the Attributes panel, find Show to.\n3. Pick Signed-in visitors or Signed-out visitors. Everyone is the default.\nFor a header that says "Sign in" to visitors and "Account" to members, put two buttons side by side: set the "Sign in" button to Signed-out visitors and the "Account" button to Signed-in visitors. Both can open your account page, which shows the sign-in form to anyone who is not signed in yet.'
2659
+ },
2660
+ {
2661
+ path: '/building-sites/besigner/show-to-signed-in-visitors',
2662
+ title: 'Show to signed-in or signed-out visitors',
2663
+ heading: 'What visitors see',
2664
+ anchor: '#what-visitors-see',
2665
+ text: 'The live site decides as the page loads, so a visitor never sees the wrong button appear and disappear. Signing in or out on the account page updates the page straight away.\nIn the Besigner every element shows, whatever its Show to, so you can select and edit both versions.\nIt hides, it does not protect Show to decides what is shown, not who may see it: the content is still in the page. For content only members may read, use a members-only page.'
2666
+ },
2646
2667
  {
2647
2668
  path: '/building-sites/besigner/text-editing',
2648
2669
  title: 'Inline & rich text editing',
@@ -8633,7 +8654,7 @@ export const DOCS_SECTION_INDEX = [
8633
8654
  title: 'Forms & Lead Capture',
8634
8655
  heading: 'Where submissions go',
8635
8656
  anchor: '#where-submissions-go',
8636
- text: '- Inbox — every submission is captured; open it in the console\'s mail reader dialog.\n- Datasets — bind a form to a dataset (Write to dataset on the Form element) and each submission is also appended as a record. The inbox always gets its copy, and each submission\'s own detail dialog carries chips saying where it went — including saying nothing about a dataset when the record wasn\'t created.\n- Contacts — every submission that carries an email address updates the person in the CRM at stage Lead: a new contact when the address is new, an interaction on their timeline when it is not, and a customer stays a customer. A field can also save its answer into one of your custom contact fields — pick the field under Saves to contact fields on the form\'s own page.\n- Leads — only when the form\'s CRM routing card has the lead switch on. See What makes a lead.\nThe inbox\nThe site\'s Inbox page collects everything visitors send, in three tabs — Submissions, Members & leads, and Campaigns. The Form Submissions table reads as a list of people, not of forms: From, Message, Received, and the row actions.\n- From shows the sender — a colored initials avatar and their name, with the form name as a caption underneath (the Form element\'s Form name attribute, so name your forms distinctly: "Contact", "Newsletter", "Survey"). The avatar\'s color is derived from the name, so one sender keeps one color on every machine.\n- Unread submissions are bold with a dot at the left of the row. There is no "New" chip — bold text and a chip saying New are the same fact twice. Site managers also get an in-app notification per submission, and an email too unless they switched that off. It names the form, the page and the campaign, and opens that submission rather than the list — see What an open submission links to'
8657
+ text: '- Inbox — every submission is captured; open it in the console\'s mail reader dialog.\n- Datasets — bind a form to a dataset (Write to dataset on the Form element) and each submission is also appended as a record. The inbox always gets its copy, and each submission\'s own detail dialog carries chips saying where it went — including saying nothing about a dataset when the record wasn\'t created.\n- Contacts — every submission that carries an email address updates the person in the CRM at stage Lead: a new contact when the address is new, an interaction on their timeline when it is not, and a customer stays a customer. A field can also save its answer into one of your custom contact fields — pick the field under Saves to contact fields on the form\'s own page.\n- Leads — only when the form\'s CRM routing card has the lead switch on. See What makes a lead.\nOn Free, which keeps up to 100 people for the CRM, a submission past that is still saved in the inbox and the visitor sees the normal confirmation, but no new contact or lead is made from it, now or later — see CRM records.\nThe inbox\nThe site\'s Inbox page collects everything visitors send, in three tabs — Submissions, Members & leads, and Campaigns. The Form Submissions table reads as a list of people, not of forms: From, Message, Received, and the row actions.\n- From shows the sender — a colored initials avatar and their name, with the form name as a caption underneath (the Form element\'s Form name attribute, so name your forms distinctly: "Contact", "Newsletter", "Survey"). The avatar\'s color is derived from the name, so one sender keeps one color on every machine.\n- Unread submissions are bold with a dot at the left of the row. There is no "New" chip — bold text and a chip saying New are the same fact twice. Site managers als'
8637
8658
  },
8638
8659
  {
8639
8660
  path: '/content-and-data/forms/overview',
@@ -11559,7 +11580,7 @@ export const DOCS_SECTION_INDEX = [
11559
11580
  title: 'Your first API call',
11560
11581
  heading: '',
11561
11582
  anchor: '',
11562
- text: 'Your first API call\nBy the end of this page you\'ll have made a real request to your own data and handled the errors properly. It assumes nothing — if you\'ve never used an API before, start at the top and follow along; if you have, skip to Step 3 and then read the API reference instead of the rest of this.\nEverything here uses curl, which is already installed on macOS and Linux and ships with Windows 10 and later. There\'s a JavaScript version of each step underneath.\nWhat you need\n- An organization on a plan that includes API access — Pro or Custom.\n- The Manage API keys permission, which owners and admins hold by default.\n- A terminal.'
11583
+ 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 — Starter, Pro or Custom.\n- The Manage API keys permission, which owners and admins hold by default.\n- A terminal.'
11563
11584
  },
11564
11585
  {
11565
11586
  path: '/guides/your-first-api-call',
@@ -11601,7 +11622,7 @@ export const DOCS_SECTION_INDEX = [
11601
11622
  title: 'Your first API call',
11602
11623
  heading: 'The four errors you will hit',
11603
11624
  anchor: '#the-four-errors-you-will-hit',
11604
- text: 'Every error has the same shape, and type is the field to branch on:\n| You see | It means | Do this |\n| 401 unauthorized | Key missing, mistyped, or revoked. | Check the header is Authorization: Bearer aglynsk…. A common cause is a shell variable that didn\'t expand — echo $AGLYNAPIKEY. |\n| 403 insufficientscope | The key is fine; it lacks a permission. code names the exact scope. | Create a key with that scope. You can\'t add a scope to an existing key. |\n| 403 planrequired | The organization\'s plan doesn\'t include API access — or, on commerce endpoints, doesn\'t include commerce (code: "commerce"). | Not transient. Don\'t retry — alert a human. |\n| 429 ratelimited | Over 120 requests/minute for this key. | Back off. Retry-After says for how long, and every response carries the remaining budget in its headers. |\nRetry 429 and 500. Never retry 401, 403, or 400 — nothing about them will change on the second attempt, and a loop that retries them turns a config mistake into a rate-limit ban.'
11625
+ text: 'Every error has the same shape, and type is the field to branch on:\n| You see | It means | Do this |\n| 401 unauthorized | Key missing, mistyped, or revoked. | Check the header is Authorization: Bearer aglynsk…. A common cause is a shell variable that didn\'t expand — echo $AGLYNAPIKEY. |\n| 403 insufficientscope | The key is fine; it lacks a permission. code names the exact scope. | Create a key with that scope. You can\'t add a scope to an existing key. |\n| 403 planrequired | The organization\'s plan doesn\'t include API access — or, on commerce endpoints, doesn\'t include commerce (code: "commerce"). | Not transient. Don\'t retry — alert a human. |\n| 429 ratelimited | A limit refused it — 120 requests/minute for this key, the workspace\'s per-minute limit across all its keys, or (on Starter) the monthly ceiling. code says which; see Rate limits. | Back off. Retry-After says for how long, and every response carries the remaining budget in its headers. |\nRetry 429 and 500. Never retry 401, 403, or 400 — nothing about them will change on the second attempt, and a loop that retries them turns a config mistake into a rate-limit ban.'
11605
11626
  },
11606
11627
  {
11607
11628
  path: '/guides/your-first-api-call',
@@ -12541,6 +12562,62 @@ export const DOCS_SECTION_INDEX = [
12541
12562
  anchor: '#related',
12542
12563
  text: '- Actions builder\n- Webhooks\n- Bindings, variables & functions'
12543
12564
  },
12565
+ {
12566
+ path: '/marketing-and-automation/workflows-and-actions/claude',
12567
+ title: 'Claude and other AI assistants',
12568
+ heading: '',
12569
+ anchor: '',
12570
+ text: 'Claude and other AI assistants\nConnect Claude to your workspace and ask it for things in plain words: "Who filled in the contact form this week?", "Add these five services to my site", "Mark order 1042 shipped with this tracking number", "Log my call with Dana and remind me on Friday."\nYou sign in to Aglyn and choose what the assistant may do. There is nothing to copy or paste, and you can disconnect it at any time.\nThe steps below use Claude. Other assistants connect the same way.'
12571
+ },
12572
+ {
12573
+ path: '/marketing-and-automation/workflows-and-actions/claude',
12574
+ title: 'Claude and other AI assistants',
12575
+ heading: 'Connect Claude',
12576
+ anchor: '#connect-claude',
12577
+ text: '1. In Claude, open Settings → Connectors and choose Add custom connector.\n2. Name it Aglyn and enter this address: https://app.aglyn.com/api/mcp\n3. Choose Connect. Aglyn opens and asks you to sign in if you are not already.\n4. Pick the workspace Claude should work in.\n5. Choose what it may do:\n- View only lets Claude look things up and nothing else.\n- View and make changes also lets it add and update things for you.\n6. Choose Allow. You are returned to Claude, and Aglyn appears in its list of connectors.\nConnecting takes the Manage API keys permission in the workspace, which owners and admins have. It is included from the Starter plan.\nOn a Team or Enterprise plan for Claude, an owner of your Claude organization adds the connector once, and each person then connects with their own Aglyn sign-in.'
12578
+ },
12579
+ {
12580
+ path: '/marketing-and-automation/workflows-and-actions/claude',
12581
+ title: 'Claude and other AI assistants',
12582
+ heading: 'Other assistants',
12583
+ anchor: '#other-assistants',
12584
+ text: 'Aglyn works with any assistant or tool that supports the Model Context Protocol (MCP) with sign-in, not only Claude.\n1. In the assistant, find where it adds a connector, app or MCP server.\n2. Enter the address https://app.aglyn.com/api/mcp.\n3. Sign in to Aglyn when it asks, pick the workspace and what the assistant may do, and choose Allow.\nBefore you choose Allow, Aglyn shows the name the app gives itself and where it returns to. Check that this is the assistant you started from. Only continue if you started connecting it yourself.\nEverything on this page applies to any connected assistant: what it can and cannot do, your plan, and how to disconnect it.'
12585
+ },
12586
+ {
12587
+ path: '/marketing-and-automation/workflows-and-actions/claude',
12588
+ title: 'Claude and other AI assistants',
12589
+ heading: 'What Claude can do',
12590
+ anchor: '#what-claude-can-do',
12591
+ text: '| Area | Claude can |\n| Sites | List your sites, create a site, and publish a site. |\n| Site content | Read and edit datasets and their records - the content behind listings, service pages, menus and directories. |\n| Contacts and CRM | Find, add, update and merge contacts. Work with companies, deals, tasks, activities, leads and email templates. |\n| Form submissions | Read submissions, mark them read, and delete them. |\n| Orders and products | Read orders and products, and mark an order shipped or delivered with its tracking number. |\n| Bookings | Read bookings. |\n| Media | List your media and upload new files. |\nEach area follows your plan, the same way it does in the console: the CRM needs a plan with the CRM, orders need commerce, and so on.\nWhat it cannot do\nClaude cannot cancel or refund an order, move or cancel a booking, rename or delete a site, replace or delete media, or change your team, plan or billing. Do those in the console.\nDesigning a page is also done in the console, in the editor. If you use Claude\'s browser extension, Claude can work in the console alongside you there, in your own signed-in window.'
12592
+ },
12593
+ {
12594
+ path: '/marketing-and-automation/workflows-and-actions/claude',
12595
+ title: 'Claude and other AI assistants',
12596
+ heading: 'Good habits',
12597
+ anchor: '#good-habits',
12598
+ text: '- Start with View only if you mainly want answers. You can connect again with more access later.\n- Ask Claude to tell you before it changes anything. In Claude\'s connector settings you can also choose which actions need your approval each time.\n- Check before you publish. Publishing a site makes its changes live for visitors.\n- What Claude reads from your workspace is handled by Claude under your agreement with Anthropic. Connect only a Claude account you trust with your customers\' details.'
12599
+ },
12600
+ {
12601
+ path: '/marketing-and-automation/workflows-and-actions/claude',
12602
+ title: 'Claude and other AI assistants',
12603
+ heading: 'Disconnect Claude',
12604
+ anchor: '#disconnect-claude',
12605
+ text: '1. In Aglyn, open your workspace\'s Settings → API keys.\n2. Under Connected apps, find the assistant and choose Disconnect.\nIt loses access right away. You can also remove the connector in Claude\'s own settings.\nEverything Claude does counts toward your plan\'s API requests, the same as any other connected app. See usage.'
12606
+ },
12607
+ {
12608
+ path: '/marketing-and-automation/workflows-and-actions/claude',
12609
+ title: 'Claude and other AI assistants',
12610
+ heading: 'Claude Code',
12611
+ anchor: '#claude-code',
12612
+ text: 'If you use Claude Code, install the Aglyn plugin. It adds the same connection plus guidance that teaches Claude how to work in Aglyn.\nThen run /mcp, choose aglyn, and sign in.'
12613
+ },
12614
+ {
12615
+ path: '/marketing-and-automation/workflows-and-actions/claude',
12616
+ title: 'Claude and other AI assistants',
12617
+ heading: 'For developers',
12618
+ anchor: '#for-developers',
12619
+ text: 'Scripts and servers with nobody to sign in can use an API key with the same address. The tools Claude sees are the operations in the REST API.'
12620
+ },
12544
12621
  {
12545
12622
  path: '/marketing-and-automation/workflows-and-actions/org-automations',
12546
12623
  title: 'Org automations',
@@ -12686,7 +12763,7 @@ export const DOCS_SECTION_INDEX = [
12686
12763
  title: 'Add-ons',
12687
12764
  heading: 'What you can add',
12688
12765
  anchor: '#what-you-can-add',
12689
- 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'
12766
+ 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 — Starter\'s rate is higher than Pro\'s; aglyn.com/pricing has each |\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 pl'
12690
12767
  },
12691
12768
  {
12692
12769
  path: '/workspace-and-billing/billing-and-plans/add-ons',
@@ -12742,28 +12819,35 @@ export const DOCS_SECTION_INDEX = [
12742
12819
  title: 'Bandwidth',
12743
12820
  heading: '',
12744
12821
  anchor: '',
12745
- text: 'Bandwidth\nBandwidth is how much traffic your published sites serve in a calendar month: their pages, and the video, audio and files they serve from your media library. Video, audio, file downloads and other media served from our servers count 1.6× toward bandwidth, because serving them costs more than serving pages. Every plan includes an amount. What happens when you pass it is the part worth reading, because it is not the same on Free as it is on a paid plan.\nPlan availability Every plan has a bandwidth allowance. On a paid plan going past it is metered and billed, and your sites keep serving. On Free it is a hard stop: the site is paused until the start of the next month.'
12822
+ text: 'Bandwidth\nBandwidth is how much traffic your published sites serve in a calendar month: their pages, and the video, audio and files they serve from your media library. Video, audio, file downloads and other media served from our servers count 1.6× toward bandwidth, because serving them costs more than serving pages. Every plan includes an amount. What happens when you pass it is the part worth reading, because it is not the same on Free as it is on a paid plan.\nPlan availability Every plan has a bandwidth allowance. On a paid plan going past it is metered and billed, and your sites keep serving. On Free it is a hard stop: the site is paused until the start of the next month. The first time a site goes over, it stays online for 72 hours first, so there is time to upgrade — see The one-time grace.'
12746
12823
  },
12747
12824
  {
12748
12825
  path: '/workspace-and-billing/billing-and-plans/bandwidth',
12749
12826
  title: 'Bandwidth',
12750
12827
  heading: 'What each plan includes',
12751
12828
  anchor: '#what-each-plan-includes',
12752
- 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.'
12829
+ text: '| Plan | Included bandwidth per month | Past the allowance |\n| Free | 2 GB | Sites are paused until the start of next month (the first time, after 72 hours) |\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.'
12753
12830
  },
12754
12831
  {
12755
12832
  path: '/workspace-and-billing/billing-and-plans/bandwidth',
12756
12833
  title: 'Bandwidth',
12757
12834
  heading: 'Where to see your usage',
12758
12835
  anchor: '#where-to-see-it',
12759
- text: '1. In the console, open Billing from the organization menu.\n2. Find the Usage card.\n3. Read the row labeled Bandwidth (this month, organization).\nThe meter resets on the first of each month, in UTC.\nYou do not have to be watching it. Organization admins get an in-app notification and an email at 75%, 80% and 90% of the allowance and again at 100% — each step once a month, and only the highest step reached, so a busy day that jumps from 70% to 95% sends one 90% notice. What those messages say depends on your plan, and the difference is the point:\n- On a paid plan the 100% message reads "You\'re past your included monthly bandwidth — extra usage is now billed", and tells you the overage appears on your monthly invoice.\n- On Free it reads "You\'ve reached your monthly bandwidth limit", and points you at Billing to upgrade — because on Free there is no overage to bill, only a stop.'
12836
+ text: '1. In the console, open Billing from the organization menu.\n2. Find the Usage card.\n3. Read the row labeled Bandwidth (this month, organization).\nThe meter resets on the first of each month, in UTC.\nYou do not have to be watching it. Organization admins get an in-app notification and an email at 75%, 80% and 90% of the allowance and again at 100% — each step once a month, and only the highest step reached, so a busy day that jumps from 70% to 95% sends one 90% notice. What those messages say depends on your plan, and the difference is the point:\n- On a paid plan the 100% message reads "You\'re past your included monthly bandwidth — extra usage is now billed", and tells you the overage appears on your monthly invoice.\n- On Free there is no overage to bill, only a stop, so passing 100% is told once, at the moment it happens: each site\'s managers get a notification and an email naming the site and either its deadline — "Upgrade or your site pauses on …", the date and time in UTC, the first time — or that it is paused. The 100% usage message is not sent again on top of it. A banner across the top of the console says the same until you upgrade or the month turns.'
12760
12837
  },
12761
12838
  {
12762
12839
  path: '/workspace-and-billing/billing-and-plans/bandwidth',
12763
12840
  title: 'Bandwidth',
12764
12841
  heading: 'What a paused Free site looks like',
12765
12842
  anchor: '#paused',
12766
- text: 'When a Free organization passes its band, its published sites stop serving pages and answer with a plain notice instead, and the video, audio and files in its media library stop loading until the pause lifts:\n> Over the monthly traffic limit\n>\n> This site has used all of the traffic included with it this month, so its pages are\n> paused until the start of next month. Nothing is wrong with your connection, and\n> nothing here has been removed.\nThree things are true about that page and are worth knowing before you see it:\n- Nothing is deleted. Your pages, media, datasets and settings are untouched. The console keeps working normally — only the public site is paused, along with the video, audio and files your media library serves. Those stop wherever they load from, the media library\'s own previews included, because every play is delivered the same way; images keep loading.\n- It clears itself. The pause is stamped with the month it belongs to. When the month turns over it stops applying, with no action from you and nothing to un-set.\n- Upgrading lifts it within about a minute. The check re-reads your plan every time, so a plan change releases the pause without waiting for the next month or for any sweep to run.\nSearch engines are told not to index the notice, so a pause does not cost you your rankings.'
12843
+ text: 'When a Free organization\'s pause takes hold, its published sites stop serving pages and answer with a plain notice instead, and the video, audio and files in its media library stop loading until the pause lifts:\n> Temporarily unavailable\n>\n> This site is temporarily unavailable.\nThe notice says nothing about limits, plans or traffic: your visitors are not told why. The reason, and the way to lift it, are in your console and your inbox. Your own team sees the same notice on the public site; the console is where to upgrade.\nThree things are true about that page and are worth knowing before you see it:\n- Nothing is deleted. Your pages, media, datasets and settings are untouched. The console keeps working normally — only the public site is paused, along with the video, audio and files your media library serves. Those stop wherever they load from, the media library\'s own previews included, because every play is delivered the same way; images keep loading.\n- It clears itself. The pause is stamped with the month it belongs to. When the month turns over it stops applying, with no action from you and nothing to un-set.\n- Upgrading lifts it within about a minute. The check re-reads your plan every time, so a plan change releases the pause without waiting for the next month or for any sweep to run.\nSearch engines are told not to index the notice, so a pause does not cost you your rankings.'
12844
+ },
12845
+ {
12846
+ path: '/workspace-and-billing/billing-and-plans/bandwidth',
12847
+ title: 'Bandwidth',
12848
+ heading: 'The one-time grace',
12849
+ anchor: '#grace',
12850
+ text: 'The first time a site goes over its band, it is not paused straight away. It stays online for 72 hours, and you are told the exact date and time it will pause — in the console and by email — so you can upgrade before your visitors are turned away. If you upgrade before then, nothing pauses. If you don\'t, the site pauses at that time, as above, until the month turns over.\nIf a site first goes over in the last three days of a month, its 72 hours would end after the month does. Then nothing pauses: the count starts again on the 1st, and you are told the site stays online and that its extra time has been used.\nThis extra time is given once. It is recorded on your workspace and on every site it has when it is given, so the next time your sites go over — in any later month — they pause as soon as they pass the band. A new month, changing plans and changing back, deleting a site and making a new one, or a site added later, does not bring it back.\nA surge can still pause a site during those 72 hours. Every plan has an abuse ceiling far above its band (for Free, 100,000 page views in a month — see The two mechanisms). If traffic during the 72 hours is unusually large and reaches it, the site pauses then, visitors see the same "temporarily unavailable" notice, and you are told by notification and email, as for any pause.\nIf the extra time ends and the site pauses, you are told that too, within a day.'
12767
12851
  },
12768
12852
  {
12769
12853
  path: '/workspace-and-billing/billing-and-plans/bandwidth',
@@ -12861,7 +12945,7 @@ export const DOCS_SECTION_INDEX = [
12861
12945
  title: 'Billing & Plans',
12862
12946
  heading: 'Tiers & entitlements',
12863
12947
  anchor: '#tiers--entitlements',
12864
- 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, which Stripe bills to your own Stripe account. 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 bi'
12948
+ 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, the CRM and the API, 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, which Stripe bills to your own Stripe account. 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 meter'
12865
12949
  },
12866
12950
  {
12867
12951
  path: '/workspace-and-billing/billing-and-plans/overview',
@@ -12903,7 +12987,7 @@ export const DOCS_SECTION_INDEX = [
12903
12987
  title: 'Billing & Plans',
12904
12988
  heading: 'CRM records',
12905
12989
  anchor: '#crm-records',
12906
- 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'
12990
+ 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: your sites keep up to 100 people — contacts and the leads a form files, together — ready for the CRM when you upgrade. Past 100 a site adds no new person: the form entry is still saved under Forms and the visitor sees the normal confirmation, a new visitor keeps their member account and orders, and someone already kept is still updated, but no new contact or lead is made, and none is made later from the entries saved meanwhile. Everyone already kept stays. On Billing → Usage the band reads Stored records (organization), and at the limit it says new people are not being added, that form entries are still saved under Forms, and that upgrading keeps adding people; the owner is also told as the count nears and reaches 100. 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 mo'
12907
12991
  },
12908
12992
  {
12909
12993
  path: '/workspace-and-billing/billing-and-plans/overview',
@@ -12917,7 +13001,7 @@ export const DOCS_SECTION_INDEX = [
12917
13001
  title: 'Billing & Plans',
12918
13002
  heading: 'API access',
12919
13003
  anchor: '#api-access',
12920
- 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.\nConnected apps {#connected-apps}\nConnected apps lists every app that was connected to the workspace by signing in instead of with an API key, such as an AI assistant. To connect one, add Aglyn in the app, sign in when it asks, pick the workspace and choose View only or View and make changes. Each row shows who connected it, when it was last used and its access, and Disconnect ends its access at once. A connected app\'s requests count toward the same API requests meter as your keys.'
13004
+ text: 'The customer REST API is included on Starter, Pro and Custom — mint scoped API keys and call the versioned /v1 endpoints from anywhere. Requests are metered per organization, and the plans differ in how much they allow:\n| | Starter | Pro | Custom |\n| Included requests / month | 500 | 1,500 | Set by your agreement |\n| Past the included requests | Metered per additional 1,000 | Metered per additional 1,000 | — |\n| Monthly ceiling | 20,000 requests, then refused until the month turns | None | Set by your agreement |\n| Requests per minute, whole workspace | 120 | 600 | Set by your agreement |\n| Requests per minute, per key | 120 | 120 | 120 |\n| Webhooks and Zapier hooks | Not included | Included | Included |\n- Requests past the included quota keep working and bill as metered overage on your monthly invoice. On Starter they stop at the monthly ceiling: the API answers 429 until the next calendar month (UTC). Pro has no ceiling.\n- The workspace limit counts every key together, so adding keys doesn\'t add capacity past it. See Rate limits & usage.\n- On any plan, a workspace that can\'t be billed for overage — no active subscription, or a 100% discount on the whole bill — stops at its included requests.\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 limits are counted — rejected calls (bad key, wrong plan, rate-limited, past the ceiling) are never billed.\nConnected apps {#connected-apps}\nConnected apps lists every app that was connected to the workspace by signing in instead of with an API key, such as an AI assistant. To connect one, add Aglyn in the app, sign in when it asks, pick the workspace and choose View only or View and make changes. Each row shows'
12921
13005
  },
12922
13006
  {
12923
13007
  path: '/workspace-and-billing/billing-and-plans/overview',