@aglyn/aglyn 1.18.0 → 1.20.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 (47) hide show
  1. package/package.json +11 -11
  2. package/src/lib/app-utils/analytics-events.d.ts +44 -0
  3. package/src/lib/app-utils/analytics-events.js +226 -21
  4. package/src/lib/app-utils/analytics-events.js.map +1 -1
  5. package/src/lib/app-utils/analytics-link-clicks.js +3 -4
  6. package/src/lib/app-utils/analytics-link-clicks.js.map +1 -1
  7. package/src/lib/app-utils/compose-reusable-components.js +7 -3
  8. package/src/lib/app-utils/compose-reusable-components.js.map +1 -1
  9. package/src/lib/app-utils/crm.d.ts +80 -1
  10. package/src/lib/app-utils/crm.js +136 -5
  11. package/src/lib/app-utils/crm.js.map +1 -1
  12. package/src/lib/app-utils/docs-help-sections.generated.js +1 -1
  13. package/src/lib/app-utils/docs-help-sections.generated.js.map +1 -1
  14. package/src/lib/app-utils/docs-help.generated.d.ts +2 -2
  15. package/src/lib/app-utils/docs-help.generated.js +6 -1
  16. package/src/lib/app-utils/docs-help.generated.js.map +1 -1
  17. package/src/lib/app-utils/docs-index.generated.js +44 -16
  18. package/src/lib/app-utils/docs-index.generated.js.map +1 -1
  19. package/src/lib/app-utils/element-motion.js +6 -5
  20. package/src/lib/app-utils/element-motion.js.map +1 -1
  21. package/src/lib/app-utils/expand-repeatables.d.ts +23 -3
  22. package/src/lib/app-utils/expand-repeatables.js +61 -7
  23. package/src/lib/app-utils/expand-repeatables.js.map +1 -1
  24. package/src/lib/app-utils/plugin-connection-editor.d.ts +22 -0
  25. package/src/lib/app-utils/plugin-connection-editor.js.map +1 -1
  26. package/src/lib/app-utils/plugin-connection-repeat.d.ts +82 -0
  27. package/src/lib/app-utils/plugin-connection-repeat.js +162 -0
  28. package/src/lib/app-utils/plugin-connection-repeat.js.map +1 -0
  29. package/src/lib/app-utils/repeat-sources.d.ts +33 -1
  30. package/src/lib/app-utils/repeat-sources.js +27 -3
  31. package/src/lib/app-utils/repeat-sources.js.map +1 -1
  32. package/src/lib/app-utils/seo-page-facts.js +3 -6
  33. package/src/lib/app-utils/seo-page-facts.js.map +1 -1
  34. package/src/lib/plugin-manager/feature-plugins.d.ts +8 -0
  35. package/src/lib/plugin-manager/feature-plugins.js.map +1 -1
  36. package/src/lib/plugin-manager/first-party-plugins.generated.d.ts +6 -0
  37. package/src/lib/plugin-manager/first-party-plugins.generated.js +8 -0
  38. package/src/lib/plugin-manager/first-party-plugins.generated.js.map +1 -1
  39. package/src/lib/plugin-manager/plugin-scope-sharing.d.ts +22 -0
  40. package/src/lib/plugin-manager/plugin-scope-sharing.js +21 -1
  41. package/src/lib/plugin-manager/plugin-scope-sharing.js.map +1 -1
  42. package/src/lib/plugin-manager/plugin-site-exclusions.d.ts +107 -0
  43. package/src/lib/plugin-manager/plugin-site-exclusions.js +169 -0
  44. package/src/lib/plugin-manager/plugin-site-exclusions.js.map +1 -0
  45. package/src/lib/plugin-manager/repeat-rows.d.ts +20 -2
  46. package/src/lib/plugin-manager/repeat-rows.js +42 -16
  47. package/src/lib/plugin-manager/repeat-rows.js.map +1 -1
@@ -2375,7 +2375,7 @@ export const DOCS_SECTION_INDEX = [
2375
2375
  title: 'Repeat over data',
2376
2376
  heading: '',
2377
2377
  anchor: '',
2378
- text: 'Repeat over data\nAny element on a page can repeat. Point it at a dataset and it renders once per record on the published page, with each copy filled in from that record. A row of cards, a gallery, a team list, a price table — one design, as many copies as you have rows.'
2378
+ text: 'Repeat over data\nAny element on a page can repeat. Point it at a dataset — or at what a connected service last synced — and it renders once per record on the published page, with each copy filled in from that record. A row of cards, a gallery, a team list, a price table — one design, as many copies as you have rows.'
2379
2379
  },
2380
2380
  {
2381
2381
  path: '/building-sites/besigner/repeat',
@@ -2419,6 +2419,20 @@ export const DOCS_SECTION_INDEX = [
2419
2419
  anchor: '#what-you-cant-do',
2420
2420
  text: '- Repeats don\'t nest. A repeat inside another repeat\'s template renders once inside each copy, using its own record — it does not multiply out.\n- A copy is not a page. Copies share one design by definition. If one record needs to look different, that\'s a condition on the design, not a second design.'
2421
2421
  },
2422
+ {
2423
+ path: '/building-sites/besigner/repeat',
2424
+ title: 'Repeat over data',
2425
+ heading: 'Repeat over a connected service',
2426
+ anchor: '#repeat-over-a-connected-service',
2427
+ text: 'A plugin that connects to a service — Google reviews, say — keeps a small copy of what that service last sent: a list of items (each review) and a summary (the overall rating and the number of reviews). Any element can repeat over that copy the same way it repeats over a dataset, so you design the reviews with ordinary elements — a Card, a Stack, Typography, an image, a link — instead of styling one closed block.\n1. Install the plugin and connect it to the service on the site\'s page for that plugin.\n2. Select the element on the canvas and open the Attributes tab.\n3. In Repeat over a connection, pick what to repeat over. Each connection is listed twice, by its name:\n- each item (for example Google: each item) — one copy per item, such as one card per review;\n- summary (for example Google: summary) — one copy holding the summary, such as a "4.8 stars from 120 reviews" header.\nThe picker lists only the connections this site has. On a site with none, it does not appear at all.\nInside the repeating element, Insert binding lists the fields the plugin provides — for example {{item.author}}, {{item.rating}}, {{item.text}}. Dates read as Nov 3, 2026; each date also comes as …Iso (for example {{item.publishedAtIso}}) when you need the exact moment rather than the words.\nFilter, sort and limit work exactly as they do for a dataset: Repeat limit 3 shows the first three reviews, Repeat filter rating >= 4 only the good ones, and Repeat sort publishedAtIso desc the newest first.\nUntil the plugin has synced for the first time, there is nothing to show: a repeat over the items renders no copies, and a repeat over the summary renders none either, so the published page never shows an empty card.'
2428
+ },
2429
+ {
2430
+ path: '/building-sites/besigner/repeat',
2431
+ title: 'Repeat over data',
2432
+ heading: 'Hide part of a copy when a field is empty',
2433
+ anchor: '#hide-part-of-a-copy-when-a-field-is-empty',
2434
+ text: 'Some records fill a field and others don\'t — a review the owner replied to, and one they didn\'t. To draw a block only on the copies that have the value, bind its visibility to the field:\n1. Select the block inside the repeating element (for example a Box holding a "Response from the owner" caption and {{item.reply}}).\n2. In the Attributes tab, set Hide unless to {{item.reply}} (the Insert binding button lists the fields). Every element inside a repeating element has this field.\nEach copy whose review has a reply draws the block; every other copy leaves it out, caption included. Hide when works the other way round: the block is left out of each copy where the field holds a value. Both work the same way inside a repeat over a dataset.\nA field that is empty, false, 0, no or off counts as no value. On the canvas, the copy you edit always shows the block so you can keep designing it; the copies beside it, Preview and the published page leave it out where the record has no value.'
2435
+ },
2422
2436
  {
2423
2437
  path: '/building-sites/besigner/repeat',
2424
2438
  title: 'Repeat over data',
@@ -6834,7 +6848,7 @@ export const DOCS_SECTION_INDEX = [
6834
6848
  title: 'Activities & the timeline',
6835
6849
  heading: 'Where an activity is visible',
6836
6850
  anchor: '#where-an-activity-is-visible',
6837
- text: 'An activity is visible exactly where a contact captured on the same site would be: to that site alone, or to every site declared to be one sender with it, or to the whole organization when the organization has chosen an org-wide default. Logging an activity never widens what a scoped member can see, and a section of the CRM can never show an activity to somebody who could not open the record it belongs to.'
6851
+ text: 'An activity is visible exactly where a contact captured on the same site would be: to that site alone, or to every site declared to be one sender with it, or to the whole organization when the organization has chosen an org-wide default. Under All sites except… it is visible to every site but the ones left out, including sites added later. Logging an activity never widens what a scoped member can see, and a section of the CRM can never show an activity to somebody who could not open the record it belongs to.'
6838
6852
  },
6839
6853
  {
6840
6854
  path: '/content-and-data/crm/activities',
@@ -7961,28 +7975,42 @@ export const DOCS_SECTION_INDEX = [
7961
7975
  title: 'Share records across sites',
7962
7976
  heading: '',
7963
7977
  anchor: '',
7964
- text: 'Share records across sites\nA record in your CRM belongs to the whole workspace: every site sees the contacts, companies, deals and tasks, whichever site they came in on. The site a record came from is kept as its source, so you can still tell which brand met the person.\nAn agency that keeps each client\'s records apart can change that. A member holding Change CRM settings (owners and admins by default) sets Default sharing for new records in the CRM\'s Settings to Only the site they came in on. Each site then sees the people it captured, a site in a consent group also sees the records of the group\'s other sites, and every other record is hidden from it, so one client\'s collaborator never sees another client\'s people. The setting covers new contacts, companies, deals and tasks, and changes nothing that already exists. It is separate from the defaults for new datasets and media files, which are set on the organization Data and Media pages.\nThe rest of this page is for a workspace that keeps its sites apart.\nWhen you run several brands and want one brand\'s team to work records another brand captured, a member holding Change CRM settings can share them. You can share a lead, a contact, a company or a deal:\n- By hand: one record from its page, or a selection from the Leads or Contacts list.\n- By a sharing rule: every record the rule matches, including the ones you already have and every one captured or changed later.\nYou can share with chosen sites or with All sites. All sites includes sites you add to the workspace later.'
7978
+ text: 'Share records across sites\nA record in your CRM belongs to the whole workspace: every site sees the contacts, companies, deals and tasks, whichever site they came in on. The site a record came from is kept as its source, so you can still tell which brand met the person.'
7979
+ },
7980
+ {
7981
+ path: '/content-and-data/crm/sharing',
7982
+ title: 'Share records across sites',
7983
+ heading: 'Default sharing for new records',
7984
+ anchor: '#default-sharing-for-new-records',
7985
+ text: 'A member holding Change CRM settings (owners and admins by default) chooses, in the CRM\'s Settings, what new contacts, leads, companies, deals, tasks and logged activities are shared with, and saves it:\n- All sites in the organization, as above.\n- Only the site they came in on: what an agency that keeps each client\'s records apart chooses. Each site then sees the people it captured, a site in a consent group also sees the records of the group\'s other sites, and every other record is hidden from it, so one client\'s collaborator never sees another client\'s people.\n- All sites except…: every site but the ones you tick to leave out, including sites you add later. The site a person came in on always keeps them, even if you left it out. Leave out at least one site and keep at least one in. A workspace with one site has nothing to leave out, and the choice works up to 30 sites; past either, it is switched off, with the reason.\nThe setting covers records created from then on, and changes nothing that already exists. It is separate from the defaults for new datasets and media files, which are set on the organization Data and Media pages.\nApply to existing records {#apply-to-existing-records}\nUnder All sites except…, the records you already have can be shared the same way. Choose Apply to existing records… below the setting, after saving it, and confirm. Every contact, lead, company, deal, task and logged activity in the workspace is then shared with every site except the ones you left out:\n- the site that captured a person keeps them, whatever you left out;\n- sites left out stop seeing the rest;\n- records shared by hand or by a sharing rule keep those shares on top.\nNothing changes on existing records until you apply it, and it changes them only once: to apply a later change of '
7986
+ },
7987
+ {
7988
+ path: '/content-and-data/crm/sharing',
7989
+ title: 'Share records across sites',
7990
+ heading: 'Share a record with more sites',
7991
+ anchor: '#share-a-record-with-more-sites',
7992
+ text: 'The rest of this page is for a workspace whose records don\'t all reach every site.\nWhen you run several brands and want one brand\'s team to work records another brand captured, a member holding Change CRM settings can share them. You can share a lead, a contact, a company or a deal:\n- By hand: one record from its page, or a selection from the Leads or Contacts list.\n- By a sharing rule: every record the rule matches, including the ones you already have and every one captured or changed later.\nYou can share with All sites, with Selected sites, or with All sites except… the ones you leave out. All sites, and all sites except some, include sites you add to the workspace later; selected sites don\'t.\nAll sites except some {#all-sites-except-some}\nTick the sites to leave out, and every other site sees the record. A site you add later sees it too, once the workspace has finished adding the site. Leave out at least one site and keep at least one in; a workspace with one site has nothing to leave out, so the choice is switched off there, with the reason. It reaches up to 30 sites, so a workspace with more than 30 sites shares with selected sites instead.\nLeaving out the site that captured the person changes nothing for that site: it holds the record, and sharing never takes that away.\nSharing only adds sites to a record. A record every site already sees, which is every record in a workspace that hasn\'t chosen Only the site they came in on, looks the same after sharing with all sites except some.'
7965
7993
  },
7966
7994
  {
7967
7995
  path: '/content-and-data/crm/sharing',
7968
7996
  title: 'Share records across sites',
7969
7997
  heading: 'What a shared record looks like',
7970
7998
  anchor: '#what-a-shared-record-looks-like',
7971
- text: 'On the site you shared it with, the record appears on the site\'s own CRM lists with a Shared by chip. The chip names the person who shared it, or the rule that did.\nThe Sharing card {#sharing-card}\nThe Sharing card on a lead\'s, contact\'s, company\'s or deal\'s page lists every site that can see the record and why; a member holding Change CRM settings shares it with more sites from Share with sites… in the card\'s header. For anyone else that button is switched off, with the permission named:\n- Held by: the sites that captured the record. Their visibility comes from the record itself, and sharing never removes it.\n- Shared by hand: the site, who shared it and when. A member holding Change CRM settings can stop sharing it in one click.\n- Shared by a rule: the rule\'s name. To stop it, edit or delete the rule in Settings.\nUnsharing removes only the visibility that the share added. If the site also holds the record (it captured the person itself), it keeps seeing it.'
7999
+ text: 'On the site you shared it with, the record appears on the site\'s own CRM lists with a Shared by chip. The chip names the person who shared it, or the rule that did.\nThe Sharing card {#sharing-card}\nThe Sharing card on a lead\'s, contact\'s, company\'s or deal\'s page lists every site that can see the record and why; a member holding Change CRM settings shares it with more sites from Share with sites… in the card\'s header. For anyone else that button is switched off, with the permission named:\n- Held by: the sites that captured the record. Their visibility comes from the record itself, and sharing never removes it.\n- Shared by hand: the site, or all sites except the ones left out, who shared it and when. A member holding Change CRM settings can stop sharing it in one click.\n- Shared by a rule: the rule\'s name. To stop it, edit or delete the rule in Settings.\nUnsharing removes only the visibility that the share added. If the site also holds the record (it captured the person itself), it keeps seeing it.'
7972
8000
  },
7973
8001
  {
7974
8002
  path: '/content-and-data/crm/sharing',
7975
8003
  title: 'Share records across sites',
7976
8004
  heading: 'Share a record by hand',
7977
8005
  anchor: '#share-a-record-by-hand',
7978
- text: '1. Open the lead, contact, company or deal.\n2. In the Sharing card, choose Share with sites….\n3. Pick the sites, or All sites, including sites added later.\n4. Choose the access, then Share.\nThe record\'s Activity gets an entry that says who shared it and with which sites, and the workspace activity log records it too.\nSeveral records at once\nSelect rows on the Leads or Contacts list and choose Share with sites… on the bar that appears. Up to 200 records are shared in one go.'
8006
+ text: '1. Open the lead, contact, company or deal.\n2. In the Sharing card, choose Share with sites….\n3. Choose All sites, Selected sites and tick them, or All sites except… and tick the sites to leave out.\n4. Choose the access, then Share.\nThe record\'s Activity gets an entry that says who shared it and with which sites, and the workspace activity log records it too.\nSeveral records at once\nSelect rows on the Leads or Contacts list and choose Share with sites… on the bar that appears. Up to 200 records are shared in one go.'
7979
8007
  },
7980
8008
  {
7981
8009
  path: '/content-and-data/crm/sharing',
7982
8010
  title: 'Share records across sites',
7983
8011
  heading: 'Sharing rules',
7984
8012
  anchor: '#sharing-rules',
7985
- text: 'CRM → Settings → Sharing rules, at the organization level, lists your rules. Each rule has three parts:\n| part | what you choose |\n| -- | -- |\n| Which records | Leads, contacts, companies or deals. You can limit it to records captured on certain sites, and add optional conditions: lead source, lead source direction (Inbound or Outbound), tags, campaign, status or lifecycle stage, and owner. |\n| Shared with | Chosen sites, or all sites (including sites added later). |\n| Access | Read-only, or read and edit. |\nConditions are combined with AND. Several values in one condition are combined with OR. A contact matches if any site that holds it recorded the value. A lead source direction is read through your lead source values\' groups each time a record is checked, so moving a value to another group changes which records the rule matches from then on — a record already shared keeps its share until it is next saved or the rule is saved again.\nWhen you save a rule, it is applied to the records you already have. The Status column shows the progress. Keep the page open until it says how many records changed. If the run stops, choose Resume from the rule\'s menu to continue where it stopped. From then on, every record captured or changed is checked against your rules as it is saved.\nSwitching a rule off keeps it and removes the visibility it granted. Deleting a rule removes only the visibility it granted. Records shared by hand, or by another rule, stay shared.\nA workspace can have up to 20 sharing rules.'
8013
+ text: 'CRM → Settings → Sharing rules, at the organization level, lists your rules. Each rule has three parts:\n| part | what you choose |\n| -- | -- |\n| Which records | Leads, contacts, companies or deals. You can limit it to records captured on certain sites, and add optional conditions: lead source, lead source direction (Inbound or Outbound), tags, campaign, status or lifecycle stage, and owner. |\n| Shared with | All sites, selected sites, or all sites except the ones you leave out. All sites, and all sites except some, include sites added later. |\n| Access | Read-only, or read and edit. |\nConditions are combined with AND. Several values in one condition are combined with OR. A contact matches if any site that holds it recorded the value. A lead source direction is read through your lead source values\' groups each time a record is checked, so moving a value to another group changes which records the rule matches from then on — a record already shared keeps its share until it is next saved or the rule is saved again.\nWhen you save a rule, it is applied to the records you already have. The Status column shows the progress. Keep the page open until it says how many records changed. If the run stops, choose Resume from the rule\'s menu to continue where it stopped. From then on, every record captured or changed is checked against your rules as it is saved.\nSwitching a rule off keeps it and removes the visibility it granted. Deleting a rule removes only the visibility it granted. Records shared by hand, or by another rule, stay shared.\nA workspace can have up to 20 sharing rules.'
7986
8014
  },
7987
8015
  {
7988
8016
  path: '/content-and-data/crm/sharing',
@@ -8003,7 +8031,7 @@ export const DOCS_SECTION_INDEX = [
8003
8031
  title: 'Share records across sites',
8004
8032
  heading: 'Who can do this',
8005
8033
  anchor: '#who-can-do-this',
8006
- text: 'Sharing, unsharing and sharing rules take the Change CRM settings permission, which owners and admins hold by default. Other members see the Sharing card and the chips, with the share buttons switched off and the permission named.\nEditing a shared record is a different permission. A member invited to one site who holds Manage data can change and delete records shared with the whole workspace, because a record shared with every site is shared with theirs too; see Custom roles & permissions. They can\'t change what a record is shared with.\nSharing is part of the CRM, included from Starter. It is only useful with more than one site, and the number of sites is set by your plan.'
8034
+ text: 'Sharing, unsharing, sharing rules, the default sharing for new records and Apply to existing records take the Change CRM settings permission, which owners and admins hold by default. Other members see the Sharing card and the chips, with the share buttons switched off and the permission named.\nEditing a shared record is a different permission. A member invited to one site who holds Manage data can change and delete records shared with the whole workspace, because a record shared with every site is shared with theirs too; see Custom roles & permissions. They can\'t change what a record is shared with.\nSharing is part of the CRM, included from Starter. It is only useful with more than one site, and the number of sites is set by your plan.'
8007
8035
  },
8008
8036
  {
8009
8037
  path: '/content-and-data/crm/sharing',
@@ -8017,7 +8045,7 @@ export const DOCS_SECTION_INDEX = [
8017
8045
  title: 'Tasks & follow-ups',
8018
8046
  heading: '',
8019
8047
  anchor: '',
8020
- text: 'Tasks & follow-ups\nA task is a piece of work somebody on your team owes a person in the CRM: a call to return, an email to send, a meeting to hold, or a plain to-do. Every task has a subject, a type, a priority, a status, an optional due date and time, an optional assignee, notes, and a link to the contact, company or deal it is about.\nTasks live in the CRM hub at …/hosts/{site}/crm/tasks and, over every site at once, at …/{organization}/crm/tasks; every record page carries its own short list of them. They follow the same per-site visibility as the contacts themselves: a task made from one site\'s console is seen from that site (and the sites it shares an audience with), and an organization that has set Default sharing for new records to All sites sees every task everywhere. A task is also the one CRM record that can belong to no site at all — see Organization tasks.\nPlan availability Tasks are part of the CRM, included from Starter. On Free the section is shown locked, with the rest of the CRM. See What each plan includes.'
8048
+ text: 'Tasks & follow-ups\nA task is a piece of work somebody on your team owes a person in the CRM: a call to return, an email to send, a meeting to hold, or a plain to-do. Every task has a subject, a type, a priority, a status, an optional due date and time, an optional assignee, notes, and a link to the contact, company or deal it is about.\nTasks live in the CRM hub at …/hosts/{site}/crm/tasks and, over every site at once, at …/{organization}/crm/tasks; every record page carries its own short list of them. They follow the same per-site visibility as the contacts themselves: a task made from one site\'s console is seen from that site (and the sites it shares an audience with), and an organization that has set Default sharing for new records to All sites sees every task everywhere, and one that set it to All sites except… sees it on every site but the ones it left out. A task is also the one CRM record that can belong to no site at all — see Organization tasks.\nPlan availability Tasks are part of the CRM, included from Starter. On Free the section is shown locked, with the rest of the CRM. See What each plan includes.'
8021
8049
  },
8022
8050
  {
8023
8051
  path: '/content-and-data/crm/tasks',
@@ -8528,7 +8556,7 @@ export const DOCS_SECTION_INDEX = [
8528
8556
  title: 'Media Library & CDN',
8529
8557
  heading: 'Who an asset is shared with',
8530
8558
  anchor: '#who-an-asset-is-shared-with',
8531
- text: 'Workspace media is shared across every site by default. The Shared with control narrows that, with the same two choices as datasets — All sites or Selected sites…. You\'ll find it in three places:\n- on a single asset, in its details drawer;\n- on a selection — tick several files and use Shared with… in the toolbar;\n- on a folder, from its ⋮ menu, which offers to apply the same sharing to the files inside it and its subfolders (it names the count, so you know what you\'re about to change).\nA folder applies its sharing when you save it — files keep their own setting afterwards, so moving a file into a "Client A" folder later does not re-share it. Narrowing a file that sites are already using names those sites first and asks you to confirm. Changing sharing takes the Edit the workspace media library permission, which workspace owners, admins and editors hold by default, and access to every site in the workspace: someone added to particular sites can\'t change it.\nA new folder or file starts shared with All sites, so it appears everywhere the moment you create it — or with the site you were working in, if your workspace has been set to make new media site-scoped by default. That default is Default sharing for new media, at the top of the workspace\'s Media page, and it changes nothing that already exists. The site you were working in is the one whose Media tab you uploaded on, or the one you were editing when you opened the media picker. A folder or file created on the workspace Media page has no site to limit it to, so it starts on All sites either way. New datasets have a default of their own, Default sharing for new datasets on the organization Data page, so files can start on every site while datasets start on one, or the other way round. If the Shared with dialog ever opens'
8559
+ text: 'Workspace media is shared across every site by default. The Shared with control narrows that, with the same three choices as datasets:\n- All sites — every site in the workspace. A new site gets it automatically.\n- Selected sites — tick the sites that share it, up to 30. A new site doesn\'t get it until you add that site.\n- All sites except… — tick the sites to leave out. Every other site shares it, and a new site gets it automatically. A workspace with one site has nothing to leave out, so this choice stays off until you add a second, and at least one site has to stay in.\nA site left out can\'t find the file in its media picker, and its pages stop showing the file wherever they show it from the media library. A link to the file that was pasted as text into custom HTML on that site keeps loading: the workspace\'s media link serves a file shared with all sites except some to anyone who has it. Narrowing a file names the sites left out that use it, and says this, before you confirm.\nYou\'ll find the control in three places:\n- on a single asset, in its details drawer;\n- on a selection — tick several files and use Shared with… in the toolbar;\n- on a folder, from its ⋮ menu, which offers to apply the same sharing to the files inside it and its subfolders (it names the count, so you know what you\'re about to change).\nA folder applies its sharing when you save it — files keep their own setting afterwards, so moving a file into a "Client A" folder later does not re-share it. Narrowing a file that sites are already using names those sites first and asks you to confirm. Changing sharing takes the Edit the workspace media library permission, which workspace owners, admins and editors hold by default, and access to every site in the workspace: someone added to particular sites can\'t cha'
8532
8560
  },
8533
8561
  {
8534
8562
  path: '/content-and-data/media/overview',
@@ -9557,7 +9585,7 @@ export const DOCS_SECTION_INDEX = [
9557
9585
  title: 'Plugin-manager API reference',
9558
9586
  heading: 'Shared with all sites except some — `plugin-scope-sharing` (`/server`)',
9559
9587
  anchor: '#shared-with-all-sites-except-some--plugin-scope-sharing-server',
9560
- text: 'A document in an org collection can be shared with every site but a few. It keeps the sites it reaches in visibleTo, so that list has to change when a site joins or leaves the workspace. One sweep does that for every collection, and it walks what plugins declare in the scopeSharingCollections block of plugins.config.json, compiled with no runtime door.\n| Declaration field | Semantics |\n| -- | -- |\n| name | The subcollection under orgs/{orgId}. One collection has one owner. |\n| patch | true when stored fields follow visibleTo, such as scoped search tokens. The sweep writes nothing to the collection until the patch is registered. |\n| maxIncluded | The most sites one document may reach. Past it the document stops gaining sites, still loses sites that left, and shows in the weekly drift report. |\n| keepSiteFields | Fields naming sites that stay included though they are excluded, such as the site that captured a person. |\n| API | Semantics |\n| -- | -- |\n| listScopeSharingCollections() | Every collection the sweep walks, with its owner, in a stable order. |\n| registerPluginScopeSharingPatch(collections, patch, { pluginId? }) | Registers the function that recomputes those fields. It receives the collection and the whole document as it will be stored, and its answer is merged into the write. Refuses a collection the plugin did not declare with patch: true. |\nRegister a patch from serverDeclarations, deferring what it needs behind an await import: it registers in every server process, and only a sweep that finds a marked document calls it.'
9588
+ text: 'A document in an org collection can be shared with every site but a few. It keeps the sites it reaches in visibleTo, so that list has to change when a site joins or leaves the workspace. One sweep does that for every collection, and it walks what plugins declare in the scopeSharingCollections block of plugins.config.json, compiled with no runtime door.\n| Declaration field | Semantics |\n| -- | -- |\n| name | The subcollection under orgs/{orgId}. One collection has one owner. |\n| patch | true when stored fields follow visibleTo, such as scoped search tokens. The sweep writes nothing to the collection until the patch is registered. |\n| maxIncluded | The most sites one document may reach. Past it the document stops gaining sites, still loses sites that left, and shows in the weekly drift report. |\n| keepSiteFields | Fields naming sites that stay included though they are excluded, such as the site that captured a person. |\n| API | Semantics |\n| -- | -- |\n| listScopeSharingCollections() | Every collection the sweep walks, with its owner, in a stable order. |\n| registerPluginScopeSharingPatch(collections, patch, { pluginId? }) | Registers the function that recomputes those fields. It receives the collection and the whole document as it will be stored, and its answer is merged into the write. Refuses a collection the plugin did not declare with patch: true. |\n| registerPluginScopeSharingSiteChange(hook, { pluginId? }) | For sharing a plugin keeps somewhere the sweep does not walk, such as a grant inside a document. After every site change, once the sweep has run, the hook receives { orgId, reason, hostId?, budgetMs }. It works for at most budgetMs, finishes the rest itself, and must never throw. One per plugin; registering again replaces it. |\n| listScopeSharingSiteChangeHooks()'
9561
9589
  },
9562
9590
  {
9563
9591
  path: '/developers/plugins/reference/plugin-manager-api',
@@ -10985,7 +11013,7 @@ export const DOCS_SECTION_INDEX = [
10985
11013
  title: 'Install your first marketplace item',
10986
11014
  heading: 'Step 4 — Choose which sites get it',
10987
11015
  anchor: '#step-4-targeting',
10988
- text: 'This is the step to read.\nOn the detail page you\'ll find an Install to dropdown with two options:\n| Option | What it means |\n| All sites | Everything in the organization. For a plugin, that includes sites you add later. |\n| Selected sites | Only the sites you tick. A Sites checklist appears underneath — tick at least one. |\n"All sites" does not mean the same thing for every kind of listing, and that is the whole reason this step exists:\n- Plugins and dataset schemas install organization-wide. A site you create next month gets them too.\n- Components, templates, layouts, themes and email templates are site-scoped. "All sites" copies them onto every site you have right now; a site you add later will not have them.\nYou will have seen this fact once already, in the What\'s included box further up the page — Installs org-wide, covering sites you add later, or Installs per site — new sites are not covered automatically. The helper text under the Install to dropdown is the same fact with your own numbers in it: for the site-scoped case it reads "Installs to all 4 sites. New sites won\'t get it automatically." Two wordings, one behavior — if they ever seem to disagree, the helper text is the one counting your actual sites.\n"Selected sites" only appears when there\'s a choice to make, so on a one-site organization you won\'t see it.\nEvery site here is a live site There is no staging site in Aglyn. Whatever you install is reachable by real visitors as soon as it\'s on a site. If you want to try something cautiously, install it to one site — ideally the quietest one — rather than to all of them.'
11016
+ text: 'This is the step to read.\nOn the detail page you\'ll find Install to, with up to three choices:\n| Option | What it means |\n| All sites | Everything in the organization. For a plugin, that includes sites you add later. |\n| Selected sites | Only the sites you tick. A list of your sites appears underneath — tick at least one. |\n| All sites except… | Every site but the ones you tick to leave out. For a plugin, that includes sites you add later. Tick at least one, and keep at least one in. |\n"All sites" does not mean the same thing for every kind of listing, and that is the whole reason this step exists:\n- Plugins and dataset schemas install organization-wide. A site you create next month gets them too.\n- Components, templates, layouts, themes and email templates are site-scoped. "All sites" copies them onto every site you have right now; a site you add later will not have them. "All sites except…" works the same way: it copies them onto the sites you have now, minus the ones you leave out, and a site you add later will not have them.\nYou will have seen this fact once already, in the What\'s included box further up the page — Installs org-wide, covering sites you add later, or Installs per site — new sites are not covered automatically. The line under each Install to choice is the same fact with your own numbers in it: for the site-scoped case it reads "Installs to all 4 sites. New sites won\'t get it automatically." Two wordings, one behavior — if they ever seem to disagree, the line under the choice is the one counting your actual sites.\n"Selected sites" and "All sites except…" only appear when there\'s a choice to make. A dataset schema installs for the whole organization, so it offers All sites alone. On a one-site organization "All sites except…" is switched off, because th'
10989
11017
  },
10990
11018
  {
10991
11019
  path: '/guides/install-your-first-plugin',
@@ -11013,7 +11041,7 @@ export const DOCS_SECTION_INDEX = [
11013
11041
  title: 'Install your first marketplace item',
11014
11042
  heading: 'Manage your plugins',
11015
11043
  anchor: '#manage-plugins',
11016
- text: 'Plugins, in the organization navigation, is where you switch plugins on and off for the whole workspace — the ones you installed from the Marketplace, listed first, and Aglyn\'s own built-in plugins below them. Open any plugin to see where it runs and change its settings.\nFind the Plugins section {#find-plugins}\nPlugins is its own section in the organization navigation, next to Marketplace. Organization → Settings → Plugins used to hold the switches; it now only points you to the section, where enabling, configuring and managing marketplace installs all live.\nBuilt-in plugins {#built-in-plugins}\nThe Built in card lists the plugins that ship with Aglyn, each with its own switch. Switching one off removes it from every site in the workspace — its navigation, the editor, published pages and the API — and switching it back on restores it.\n- Flipping a switch needs the Organization settings permission, which the workspace\'s owners and admins hold by default. Without it the switches stay off, and a plugin\'s page names the permission to ask an organization admin for.\n- A few cannot be switched off at all, because sites are built out of them.\n- AI and Forms have no workspace switch: they stay on for the workspace, and a site switches them off for itself — see A plugin on one site.\n- Switching off a plugin that another one depends on asks first, and names what else will go with it.\nA plugin\'s page {#a-plugins-page}\nOpen a plugin from the Plugins section to manage it for the workspace. Its page shows Where it runs, the plugin\'s own settings — saved once for the workspace and followed by every site — its Dependencies, and, for a marketplace plugin, the version you are pinned to and what it is allowed to reach. View listing opens a marketplace plugin\'s listing.\nWhere a plugin runs {'
11044
+ text: 'Plugins, in the organization navigation, is where you switch plugins on and off for the whole workspace — the ones you installed from the Marketplace, listed first, and Aglyn\'s own built-in plugins below them. Open any plugin to see where it runs and change its settings.\nFind the Plugins section {#find-plugins}\nPlugins is its own section in the organization navigation, next to Marketplace. Organization → Settings → Plugins used to hold the switches; it now only points you to the section, where enabling, configuring and managing marketplace installs all live.\nBuilt-in plugins {#built-in-plugins}\nThe Built in card lists the plugins that ship with Aglyn, each with its own switch. Switching one off removes it from every site in the workspace — its navigation, the editor, published pages and the API — and switching it back on restores it.\n- Flipping a switch needs the Organization settings permission, which the workspace\'s owners and admins hold by default. Without it the switches stay off, and a plugin\'s page names the permission to ask an organization admin for.\n- A few cannot be switched off at all, because sites are built out of them.\n- AI and Forms have no workspace switch: they stay on for the workspace, and a site switches them off for itself — see A plugin on one site. Their page\'s Runs on can leave sites out from the workspace too — see Where a plugin runs.\n- Switching off a plugin that another one depends on asks first, and names what else will go with it.\nA plugin\'s page {#a-plugins-page}\nOpen a plugin from the Plugins section to manage it for the workspace. Its page shows Where it runs, the plugin\'s own settings — saved once for the workspace and followed by every site — its Dependencies, and, for a marketplace plugin, the version you are pinned to and what it is'
11017
11045
  },
11018
11046
  {
11019
11047
  path: '/guides/install-your-first-plugin',
@@ -12140,7 +12168,7 @@ export const DOCS_SECTION_INDEX = [
12140
12168
  title: 'Email Campaigns',
12141
12169
  heading: 'Send a campaign',
12142
12170
  anchor: '#send-a-campaign',
12143
- text: '1. Create a campaign on Marketing → Campaigns — a name, the dates it runs between, the lists it is aimed at, and the sites it runs on. Your organization has its own Marketing page beside CRM, and every site has one too.\n2. Open it and write an email inside it. Pick the audience for that email — leads, site members, segments, or an email list. An audience built from a rule can also reuse a saved Contacts view beside a segment.\n3. Send — subject to your plan\'s send cap.\nA campaign lives under Marketing because that is what it is: a window of dates, a set of lists, a topic and the revenue it earned, which happens to reach people by email. The individual messages it sent, the templates they are built from, the audiences, the topics, the sending domains, the consent groups and the suppression list are all on the Emails page, and each message links back to the campaign it belongs to.\nCampaigns belong to your organization {#campaigns-belong-to-the-organization}\nA campaign is your organization\'s, like its contacts, lists and topics, so one campaign can coordinate a push across every site you run, the sequences your reps send and the leads they produce.\n- Which sites it runs on. A campaign is placed on every site or on the sites you choose. It is offered in a site\'s pickers — on its forms, pages and automations — only where it is placed, and a collaborator invited to one site sees only the campaigns placed there. A campaign created from a site\'s own Marketing page starts on that site; one created from the organization\'s starts on every site, and you can change either later from the organization\'s page.\n- Which site an email is sent as. Each email goes out as one site: that site\'s sender, its unsubscribe page and the consent people gave it. Writing an email from the organization\''
12171
+ text: '1. Create a campaign on Marketing → Campaigns — a name, the dates it runs between, the lists it is aimed at, and the sites it runs on. Your organization has its own Marketing page beside CRM, and every site has one too.\n2. Open it and write an email inside it. Pick the audience for that email — leads, site members, segments, or an email list. An audience built from a rule can also reuse a saved Contacts view beside a segment.\n3. Send — subject to your plan\'s send cap.\nA campaign lives under Marketing because that is what it is: a window of dates, a set of lists, a topic and the revenue it earned, which happens to reach people by email. The individual messages it sent, the templates they are built from, the audiences, the topics, the sending domains, the consent groups and the suppression list are all on the Emails page, and each message links back to the campaign it belongs to.\nCampaigns belong to your organization {#campaigns-belong-to-the-organization}\nA campaign is your organization\'s, like its contacts, lists and topics, so one campaign can coordinate a push across every site you run, the sequences your reps send and the leads they produce.\n- Which sites it runs on. A campaign is offered in a site\'s pickers — on its forms, pages and automations — only where it is placed, and a collaborator invited to one site sees only the campaigns placed there. Shared with on the organization\'s page decides which sites:\n- All sites — every site you run. A new site gets it automatically.\n- Selected sites — tick the sites that share it, up to 30. A new site doesn\'t get it until you add that site.\n- All sites except… — tick the sites to leave out. Every other site gets it, with no limit on how many, and so does a new site, automatically. A workspace with one site has nothing to leave'
12144
12172
  },
12145
12173
  {
12146
12174
  path: '/marketing-and-automation/email-campaigns/overview',
@@ -12364,7 +12392,7 @@ export const DOCS_SECTION_INDEX = [
12364
12392
  title: 'Org automations',
12365
12393
  heading: '',
12366
12394
  anchor: '',
12367
- text: 'Org automations\nAn org automation is one automation your organization writes once and runs on the sites it chooses — every site, or the ones you pick. Build it at the organization level under Automation → Org automations; each site shows the ones that run on it, and can pause them for itself.\nPlan availability Org automations are built from the actions builder\'s steps, so they are Pro+, like the actions builder, and their runs are metered on the same allowance a site\'s own actions use.'
12395
+ text: 'Org automations\nAn org automation is one automation your organization writes once and runs on the sites it chooses — every site, the ones you pick, or every site except the ones you leave out. Build it at the organization level under Automation → Org automations; each site shows the ones that run on it, and can pause them for itself.\nPlan availability Org automations are built from the actions builder\'s steps, so they are Pro+, like the actions builder, and their runs are metered on the same allowance a site\'s own actions use.'
12368
12396
  },
12369
12397
  {
12370
12398
  path: '/marketing-and-automation/workflows-and-actions/org-automations',
@@ -12378,7 +12406,7 @@ export const DOCS_SECTION_INDEX = [
12378
12406
  title: 'Org automations',
12379
12407
  heading: 'Create one',
12380
12408
  anchor: '#create-one',
12381
- text: '1. At the organization level, open Automation → Org automations and choose Add org automation.\n2. Name it and pick the trigger event. Optionally add a filter or conditions — the same ones the actions builder offers.\n3. Choose where it runs on: Every site — including sites you add later — or Chosen sites, up to 30 of them.\n4. Add the steps, then save.\nTo start from a description instead, choose Create with AI in the card\'s header: Aglyn AI drafts one and opens it in the editor, switched off, for you to place on sites and save. See Automations with AI.\nCreating and editing org automations takes the Manage org automations permission, which a workspace\'s owners, admins and editors have. An organization holds up to 100 of them; deleting one frees its place.\nTriggers\nOrg automations start on what the server records about a person: Form submitted, New lead, Contact created, Contact changed stage, New booking, Member signed up, Member signed in, Deal moved, Deal won, Deal lost and CRM task completed. What each event carries for filters and conditions is listed under the filter field as you pick it.\nPage views and on-page events (clicks, scroll depth, exit intent) are not offered: they belong to one site\'s pages. Build those as actions on the site.\nSteps\nSend an email, Notify site admins, Enroll in a list, Assign to a campaign, Write to a dataset, Update a dataset record, the five CRM steps, Fire a custom event, Wait, Wait for something to happen and End the flow here.\nWhat is left out belongs to one site, so an org automation cannot run it:\n- Run a workflow — a workflow calls its own site\'s functions and variables;\n- Send a webhook — a webhook holds its own site\'s address and secret;\n- every in-page step — popups, drawers, menus, show and hide, CSS classes, custom HTML and Java'
12409
+ text: '1. At the organization level, open Automation → Org automations and choose Add org automation.\n2. Name it and pick the trigger event. Optionally add a filter or conditions — the same ones the actions builder offers.\n3. Choose where it runs on:\n- All sites — including sites you add later;\n- Selected sites, up to 30 of them — a site you add later doesn\'t get it until you add it here;\n- All sites except… — every site but the ones you tick to leave out, including sites you add later. Leave out at least one site and keep at least one in. A workspace with one site has nothing to leave out, so this choice is switched off there, with the reason.\n4. Add the steps, then save.\nA site you leave out doesn\'t run it and can\'t pause it, because it isn\'t placed there. If that site had paused it, its pause is dropped; put the site back and it starts unpaused.\nTo start from a description instead, choose Create with AI in the card\'s header: Aglyn AI drafts one and opens it in the editor, switched off, for you to place on sites and save. See Automations with AI.\nCreating and editing org automations, including choosing the sites they run on, takes the Manage org automations permission, which a workspace\'s owners, admins and editors have. An organization holds up to 100 of them; deleting one frees its place.\nTriggers\nOrg automations start on what the server records about a person: Form submitted, New lead, Contact created, Contact changed stage, New booking, Member signed up, Member signed in, Deal moved, Deal won, Deal lost and CRM task completed. What each event carries for filters and conditions is listed under the filter field as you pick it.\nPage views and on-page events (clicks, scroll depth, exit intent) are not offered: they belong to one site\'s pages. Build those as actions on the si'
12382
12410
  },
12383
12411
  {
12384
12412
  path: '/marketing-and-automation/workflows-and-actions/org-automations',
@@ -12392,7 +12420,7 @@ export const DOCS_SECTION_INDEX = [
12392
12420
  title: 'Org automations',
12393
12421
  heading: 'Waiting, switching off and deleting',
12394
12422
  anchor: '#waiting-switching-off-and-deleting',
12395
- text: 'An org automation can Wait and Wait for something to happen, like an action. A person who is waiting waits on the site their run started on, and continues with the steps as they were when they entered, even if the automation is edited meanwhile.\nSwitching an org automation off, deleting it, taking a site off its placement, or pausing it on a site stops the people waiting inside it on the sites affected, on their next step — the same as switching off an action does.'
12423
+ text: 'An org automation can Wait and Wait for something to happen, like an action. A person who is waiting waits on the site their run started on, and continues with the steps as they were when they entered, even if the automation is edited meanwhile.\nSwitching an org automation off, deleting it, taking a site off its placement (including leaving it out of All sites except…), or pausing it on a site stops the people waiting inside it on the sites affected, on their next step — the same as switching off an action does.'
12396
12424
  },
12397
12425
  {
12398
12426
  path: '/marketing-and-automation/workflows-and-actions/org-automations',