@aglyn/aglyn 1.13.0 → 1.14.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.
@@ -7345,7 +7345,7 @@ export const DOCS_SECTION_INDEX = [
7345
7345
  title: 'Email templates',
7346
7346
  heading: 'Shared or personal',
7347
7347
  anchor: '#shared-or-personal',
7348
- text: '| | Who sees it | Who can change or delete it |\n| Shared | Everyone who can send email from the CRM. | Any CRM editor, and any org-wide member. |\n| Personal | You alone. | You, and an org-wide owner or admin tidying up. |\nA personal template is your own working arrangement, the way a private saved view is: it is kept out of colleagues\' menus rather than locked, so an admin can still remove one a departed teammate left behind.'
7348
+ text: '| | Who sees it | Who can change or delete it |\n| Shared | Everyone who can send email from the CRM. | Any CRM editor, and any org-wide member. |\n| Personal | You alone. | You, and any org-wide member who holds Manage data and Change colleagues\' email templates tidying up. Every role holds the second by default. |\nA personal template is your own working arrangement, the way a private saved view is: it is kept out of colleagues\' menus rather than locked, so an admin can still remove one a departed teammate left behind.'
7349
7349
  },
7350
7350
  {
7351
7351
  path: '/content-and-data/crm/email-templates',
@@ -8122,7 +8122,7 @@ export const DOCS_SECTION_INDEX = [
8122
8122
  title: 'Saved views',
8123
8123
  heading: 'Segments and views',
8124
8124
  anchor: '#segments-and-views',
8125
- text: 'A segment is the older, narrower thing: saved tags and sources, usable as a campaign audience. Views keep everything a segment kept and more, and the two meet in two places:\n- Every segment is offered in the Contacts views menu. Choosing one puts its tags and sources among the list\'s filters, where you can narrow further and save the result as a view.\n- Save as segment… in the views menu keeps the tag and source filters of the current view as a segment. The other filters stay on the view.\nA contacts view can also be an email audience in its own right. When you build an audience from a rule, pick it under Saved view, beside Saved segment: the view\'s filters — owner, stage, company, tags, sources, dates, purchases and custom fields — always apply, the way a segment\'s do. Only views whose filters can be an audience are offered: a view filtered by a name or an email, or by the updated date, describes a list on a screen rather than a set of people, and is left out. So is a view filtered by a source a plugin adds, such as Waiver signed; save that filter as a segment to send to those people. A view that is deleted, or edited past what an audience can express after a rule named it, makes that audience select nobody rather than everybody.'
8125
+ text: 'A segment is the older, narrower thing: saved tags and sources, usable as a campaign audience. Views keep everything a segment kept and more, and the two meet in two places:\n- Every segment is offered in the Contacts views menu. Choosing one puts its tags and sources among the list\'s filters, where you can narrow further and save the result as a view.\n- Save as segment… in the views menu keeps the tag and source filters of the current view as a segment. The other filters stay on the view.\nA contacts view can also be an email audience in its own right. When you build an audience from a rule, pick it under Saved view, beside Saved segment: the view\'s filters — owner, stage, company, tags, sources, dates, purchases and custom fields — always apply, the way a segment\'s do. Only views whose filters can be an audience are offered: a view filtered by a name or an email, or by the updated date, describes a list on a screen rather than a set of people, and is left out. A view filtered by a source a plugin adds, such as Waiver signed, is offered like any other. A view that is deleted, or edited past what an audience can express after a rule named it, makes that audience select nobody rather than everybody.'
8126
8126
  },
8127
8127
  {
8128
8128
  path: '/content-and-data/crm/views',
@@ -8276,7 +8276,7 @@ export const DOCS_SECTION_INDEX = [
8276
8276
  title: 'Datasets & Dynamic Content',
8277
8277
  heading: 'Who a dataset is shared with',
8278
8278
  anchor: '#who-a-dataset-is-shared-with',
8279
- text: 'Datasets belong to the workspace, not to a single site, so one dataset can drive pages on every site you run. When that isn\'t what you want, the Sharing control on each dataset decides which sites can see it:\n- All sites — everyone in the workspace, on every site.\n- Selected sites… — pick the sites that share it, up to 30.\nWhere a new dataset starts depends on where you create it and on your workspace\'s Default sharing for new datasets, the setting at the top of the organization Data page (new media files have a default of their own, on the workspace Media page):\n- Created on a site\'s Data page — it follows that setting. Set to All sites, the dataset starts on All sites. Set to Only the site they were created in, it starts shared with that site alone, and its control reads Selected sites… with just that site picked.\n- Created on the organization Data page — it starts on All sites whatever the setting says, because there is no site to limit it to.\n- Installed from the Marketplace, or created through the REST API — it starts on All sites too. Both act for the whole organization, not for one site.\n- Made by Aglyn AI for a site — for example the lists a guided start builds, such as your packages or FAQs — it starts shared with that site alone, whatever the setting says, because it was made for that site. Share it with more sites from its Sharing control.\nDefault sharing for new datasets {#default-dataset-sharing}\nDefault sharing for new datasets, at the top of the organization Data page, decides what a dataset created on a site\'s Data page starts shared with: All sites, or only that site. Changing it takes the Organization settings permission, which workspace owners and admins hold by default; without it the control stays off.\nThe setting only decides where a new dataset st'
8279
+ text: 'Datasets belong to the workspace, not to a single site, so one dataset can drive pages on every site you run. When that isn\'t what you want, the Sharing control on each dataset decides which sites can see it:\n- All sites — everyone in the workspace, on every site. 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.\nWhere a new dataset starts depends on where you create it and on your workspace\'s Default sharing for new datasets, the setting at the top of the organization Data page (new media files have a default of their own, on the workspace Media page):\n- Created on a site\'s Data page — it follows that setting. Set to All sites, the dataset starts on All sites. Set to Only the site they were created in, it starts shared with that site alone, and its control reads Selected sites with just that site picked.\n- Created on the organization Data page — it starts on All sites whatever the setting says, because there is no site to limit it to.\n- Installed from the Marketplace, or created through the REST API — it starts on All sites too. Both act for the whole organization, not for one site.\n- Made by Aglyn AI for a site — for example the lists a guided start builds, such as your packages or FAQs — it starts shared with that site alone, whatever the setting says, because it was made for that site. Share it with more sites from its Sharing control.\nDefault sharing for new datasets {#default-dataset-sharing}\nDefault sharing for new data'
8280
8280
  },
8281
8281
  {
8282
8282
  path: '/content-and-data/datasets/overview',
@@ -12623,7 +12623,7 @@ export const DOCS_SECTION_INDEX = [
12623
12623
  title: 'Downgrading, canceling & your data',
12624
12624
  heading: 'Deleting a single site',
12625
12625
  anchor: '#deleting-a-single-site',
12626
- text: 'To remove just one site (not the whole organization), open the site\'s Admin → Danger zone and use Delete site. It takes the Manage site settings permission on the site and Delete sites, which workspace owners and admins hold by default. You type the site name to confirm, and it\'s deleted immediately — its pages, media, and settings are permanently removed and its address stops resolving. Unlike an organization deletion there\'s no hold, so export a backup first (Setup → Backup & restore) if you might want it back. Your other sites and the organization are unaffected.\nDeleting a site also deletes what is the site\'s own:\n- Datasets shared with this site only, with all their records. The Delete site card lists them, with how many records each holds, before you confirm. A dataset the site shares with other sites stays, and the site is removed from its sharing. A dataset shared with All sites isn\'t affected.\n- The site\'s AI jobs, AI insights and Assist conversations.\nTo keep a dataset, share it with another site, or with All sites, from its Sharing control on the Data page before you delete the site.\nA site in a consent group can\'t be deleted while it\'s in the group, because the group\'s other sites honor the unsubscribes it holds. Remove it from the group first, which copies those opt-outs to the sites that stay, then delete it. The same applies while a consent group change that includes the site is still finishing.'
12626
+ text: 'To remove just one site (not the whole organization), open the site\'s Admin → Danger zone and use Delete site. It takes the Manage site settings permission on the site and Delete sites, which workspace owners and admins hold by default. You type the site name to confirm, and it\'s deleted immediately — its pages, media, and settings are permanently removed and its address stops resolving. Unlike an organization deletion there\'s no hold, so export a backup first (Setup → Backup & restore) if you might want it back. Your other sites and the organization are unaffected.\nDeleting a site also deletes what is the site\'s own:\n- Datasets shared with this site only, with all their records. The Delete site card lists them, with how many records each holds, before you confirm. A dataset the site shares with other sites stays, and the site is removed from its sharing, even if it\'s shared with all sites except some and this was the last site it reached. A dataset shared with All sites isn\'t affected.\n- The site\'s AI jobs, AI insights and Assist conversations.\nTo keep a dataset, share it with another site, or with All sites, from its Sharing control on the Data page before you delete the site.\nA site in a consent group can\'t be deleted while it\'s in the group, because the group\'s other sites honor the unsubscribes it holds. Remove it from the group first, which copies those opt-outs to the sites that stay, then delete it. The same applies while a consent group change that includes the site is still finishing.'
12627
12627
  },
12628
12628
  {
12629
12629
  path: '/workspace-and-billing/billing-and-plans/downgrading-and-canceling',