@adminide-stack/yantra-help-browser 12.0.17 → 12.0.19-alpha.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/lib/components/HelpCenterFooter.d.ts.map +1 -1
- package/lib/components/HelpCenterFooter.js +44 -12
- package/lib/components/HelpCenterFooter.js.map +1 -1
- package/lib/components/HelpCenterHeader.d.ts +5 -1
- package/lib/components/HelpCenterHeader.d.ts.map +1 -1
- package/lib/components/HelpCenterHeader.js +40 -128
- package/lib/components/HelpCenterHeader.js.map +1 -1
- package/lib/components/Icons.js +1 -9
- package/lib/components/Icons.js.map +1 -1
- package/lib/components/PageHero.d.ts +6 -0
- package/lib/components/PageHero.d.ts.map +1 -1
- package/lib/components/PageHero.js +35 -39
- package/lib/components/PageHero.js.map +1 -1
- package/lib/components/SearchBar.d.ts +4 -0
- package/lib/components/SearchBar.d.ts.map +1 -1
- package/lib/components/SearchBar.js +56 -95
- package/lib/components/SearchBar.js.map +1 -1
- package/lib/components/SidebarSearch.d.ts.map +1 -1
- package/lib/components/SidebarSearch.js +6 -6
- package/lib/components/SidebarSearch.js.map +1 -1
- package/lib/components/navbar/index.d.ts.map +1 -1
- package/lib/components/navbar/index.js +38 -7
- package/lib/components/navbar/index.js.map +1 -1
- package/lib/compute.d.ts +1 -0
- package/lib/compute.d.ts.map +1 -1
- package/lib/compute.js +9 -0
- package/lib/compute.js.map +1 -1
- package/lib/config.d.ts +6 -0
- package/lib/config.d.ts.map +1 -1
- package/lib/config.js +66 -0
- package/lib/config.js.map +1 -0
- package/lib/pages/About/index.d.ts +1 -1
- package/lib/pages/About/index.d.ts.map +1 -1
- package/lib/pages/About/index.js +54 -55
- package/lib/pages/About/index.js.map +1 -1
- package/lib/pages/Blog/index.d.ts.map +1 -1
- package/lib/pages/Blog/index.js +26 -17
- package/lib/pages/Blog/index.js.map +1 -1
- package/lib/pages/BlogPost/index.d.ts.map +1 -1
- package/lib/pages/BlogPost/index.js +5 -5
- package/lib/pages/BlogPost/index.js.map +1 -1
- package/lib/pages/CategoryCollection/index.d.ts.map +1 -1
- package/lib/pages/CategoryCollection/index.js +54 -51
- package/lib/pages/CategoryCollection/index.js.map +1 -1
- package/lib/pages/Contact/index.d.ts.map +1 -1
- package/lib/pages/Contact/index.js +96 -14
- package/lib/pages/Contact/index.js.map +1 -1
- package/lib/pages/Feedback/index.d.ts +3 -0
- package/lib/pages/Feedback/index.d.ts.map +1 -0
- package/lib/pages/Feedback/index.js +261 -0
- package/lib/pages/Feedback/index.js.map +1 -0
- package/lib/pages/GetStarted/components/ExampleCard.d.ts.map +1 -1
- package/lib/pages/GetStarted/components/GetStartedHero.d.ts.map +1 -1
- package/lib/pages/GetStarted/components/TipCard.d.ts.map +1 -1
- package/lib/pages/GetStarted/index.d.ts +1 -1
- package/lib/pages/GetStarted/index.d.ts.map +1 -1
- package/lib/pages/GetStarted/index.js +129 -332
- package/lib/pages/GetStarted/index.js.map +1 -1
- package/lib/pages/HelpCenter/components/BookStack.d.ts.map +1 -1
- package/lib/pages/HelpCenter/components/HelpCategoryCard.d.ts.map +1 -1
- package/lib/pages/HelpCenter/components/HelpCategoryCard.js +54 -132
- package/lib/pages/HelpCenter/components/HelpCategoryCard.js.map +1 -1
- package/lib/pages/HelpCenter/components/PopularArticle.d.ts.map +1 -1
- package/lib/pages/HelpCenter/components/PopularArticle.js +21 -26
- package/lib/pages/HelpCenter/components/PopularArticle.js.map +1 -1
- package/lib/pages/HelpCenter/index.d.ts.map +1 -1
- package/lib/pages/HelpCenter/index.js +85 -223
- package/lib/pages/HelpCenter/index.js.map +1 -1
- package/lib/pages/HelpCenter/mockData.js +1 -19
- package/lib/pages/HelpCenter/mockData.js.map +1 -1
- package/lib/pages/LandingPage/components/ArticleCard.d.ts.map +1 -1
- package/lib/pages/LandingPage/components/ArticleCard.js +22 -28
- package/lib/pages/LandingPage/components/ArticleCard.js.map +1 -1
- package/lib/pages/LandingPage/components/CategoriesSection.d.ts.map +1 -1
- package/lib/pages/LandingPage/components/CategoriesSection.js +11 -15
- package/lib/pages/LandingPage/components/CategoriesSection.js.map +1 -1
- package/lib/pages/LandingPage/components/CategoryCard.d.ts.map +1 -1
- package/lib/pages/LandingPage/components/CategoryCard.js +23 -32
- package/lib/pages/LandingPage/components/CategoryCard.js.map +1 -1
- package/lib/pages/LandingPage/components/FeaturedSection.d.ts.map +1 -1
- package/lib/pages/LandingPage/components/FeaturedSection.js +10 -15
- package/lib/pages/LandingPage/components/FeaturedSection.js.map +1 -1
- package/lib/pages/LandingPage/components/HeroSection.d.ts +4 -0
- package/lib/pages/LandingPage/components/HeroSection.d.ts.map +1 -1
- package/lib/pages/LandingPage/components/HeroSection.js +53 -108
- package/lib/pages/LandingPage/components/HeroSection.js.map +1 -1
- package/lib/pages/LandingPage/components/ResourceCard.d.ts +0 -1
- package/lib/pages/LandingPage/components/ResourceCard.d.ts.map +1 -1
- package/lib/pages/LandingPage/components/ResourceCard.js +16 -23
- package/lib/pages/LandingPage/components/ResourceCard.js.map +1 -1
- package/lib/pages/LandingPage/components/ResourcesSection.d.ts +0 -1
- package/lib/pages/LandingPage/components/ResourcesSection.d.ts.map +1 -1
- package/lib/pages/LandingPage/components/ResourcesSection.js +10 -16
- package/lib/pages/LandingPage/components/ResourcesSection.js.map +1 -1
- package/lib/pages/LandingPage/index.d.ts.map +1 -1
- package/lib/pages/LandingPage/index.js +122 -236
- package/lib/pages/LandingPage/index.js.map +1 -1
- package/lib/pages/Markdown/MarkdownPageLayout.d.ts.map +1 -1
- package/lib/pages/Markdown/MarkdownPageLayout.js +10 -10
- package/lib/pages/Markdown/MarkdownPageLayout.js.map +1 -1
- package/lib/pages/ReleaseNotes/index.d.ts.map +1 -1
- package/lib/pages/ReleaseNotes/index.js +14 -11
- package/lib/pages/ReleaseNotes/index.js.map +1 -1
- package/lib/pages/StatusPage/index.d.ts.map +1 -1
- package/lib/pages/StatusPage/index.js +17 -12
- package/lib/pages/StatusPage/index.js.map +1 -1
- package/lib/routes.json +11 -0
- package/lib/slot-fill/LogoFill.js +1 -1
- package/lib/slot-fill/LogoFill.js.map +1 -1
- package/lib/templates/content/account-management/account-setup.md +3 -3
- package/lib/templates/content/account-management/delete-account.md +3 -3
- package/lib/templates/content/connectors/connector-triggers.md +76 -0
- package/lib/templates/content/connectors/creating-connector-triggers.md +121 -0
- package/lib/templates/content/connectors/managing-connector-triggers.md +125 -0
- package/lib/templates/content/connectors/subscribing-to-connector-events.md +162 -0
- package/lib/templates/content/content-manifest.json +194 -0
- package/lib/templates/content/data-privacy/privacy-policy.md +4 -4
- package/lib/templates/content/data-subject-privacy/data-access.md +1 -1
- package/lib/templates/content/data-subject-privacy/data-portability.md +1 -1
- package/lib/templates/content/data-subject-privacy/privacy-requests.md +3 -3
- package/lib/templates/content/getting-started/getting-started-guide.md +2 -2
- package/lib/templates/content/product-features/ai-models.md +1 -1
- package/lib/templates/content/scope-api/api-overview.md +2 -2
- package/lib/templates/content/security-compliance/compliance.md +1 -1
- package/lib/templates/content/security-compliance/security-overview.md +2 -2
- package/lib/templates/content/student-hub/student-overview.md +1 -1
- package/lib/templates/content/subscription-billing/billing-overview.md +2 -2
- package/lib/templates/content/subscription-billing/billing-support.md +8 -8
- package/lib/templates/content/subscription-billing/enterprise-pricing.md +1 -1
- package/lib/templates/content/subscription-billing/invoice-management.md +2 -2
- package/lib/templates/content/subscription-billing/promotional-offers.md +3 -3
- package/lib/templates/content/subscription-billing/refund-policy.md +2 -2
- package/lib/templates/content/subscription-billing/tax-information.md +3 -3
- package/lib/templates/content/technical-questions/api-technical.md +1 -1
- package/lib/templates/content/troubleshooting/common-issues.md +2 -2
- package/lib/utils/sendContactEmail.d.ts +18 -0
- package/lib/utils/sendContactEmail.d.ts.map +1 -0
- package/lib/utils/sendContactEmail.js +38 -0
- package/lib/utils/sendContactEmail.js.map +1 -0
- package/package.json +3 -3
|
@@ -296,6 +296,54 @@
|
|
|
296
296
|
"author": "Yantra Team"
|
|
297
297
|
}
|
|
298
298
|
},
|
|
299
|
+
{
|
|
300
|
+
"contentId": "connectors-connector-triggers",
|
|
301
|
+
"slug": "connector-triggers",
|
|
302
|
+
"filePath": "/content/connectors/connector-triggers.md",
|
|
303
|
+
"relativePath": "connectors/connector-triggers.md",
|
|
304
|
+
"categoryId": "connectors",
|
|
305
|
+
"title": "Connector Triggers",
|
|
306
|
+
"description": "",
|
|
307
|
+
"author": "Documentation",
|
|
308
|
+
"updatedAt": "Recently",
|
|
309
|
+
"frontmatter": {}
|
|
310
|
+
},
|
|
311
|
+
{
|
|
312
|
+
"contentId": "connectors-creating-connector-triggers",
|
|
313
|
+
"slug": "creating-connector-triggers",
|
|
314
|
+
"filePath": "/content/connectors/creating-connector-triggers.md",
|
|
315
|
+
"relativePath": "connectors/creating-connector-triggers.md",
|
|
316
|
+
"categoryId": "connectors",
|
|
317
|
+
"title": "Creating Connector Triggers",
|
|
318
|
+
"description": "",
|
|
319
|
+
"author": "Documentation",
|
|
320
|
+
"updatedAt": "Recently",
|
|
321
|
+
"frontmatter": {}
|
|
322
|
+
},
|
|
323
|
+
{
|
|
324
|
+
"contentId": "connectors-managing-connector-triggers",
|
|
325
|
+
"slug": "managing-connector-triggers",
|
|
326
|
+
"filePath": "/content/connectors/managing-connector-triggers.md",
|
|
327
|
+
"relativePath": "connectors/managing-connector-triggers.md",
|
|
328
|
+
"categoryId": "connectors",
|
|
329
|
+
"title": "Managing Connector Triggers",
|
|
330
|
+
"description": "",
|
|
331
|
+
"author": "Documentation",
|
|
332
|
+
"updatedAt": "Recently",
|
|
333
|
+
"frontmatter": {}
|
|
334
|
+
},
|
|
335
|
+
{
|
|
336
|
+
"contentId": "connectors-subscribing-to-connector-events",
|
|
337
|
+
"slug": "subscribing-to-connector-events",
|
|
338
|
+
"filePath": "/content/connectors/subscribing-to-connector-events.md",
|
|
339
|
+
"relativePath": "connectors/subscribing-to-connector-events.md",
|
|
340
|
+
"categoryId": "connectors",
|
|
341
|
+
"title": "Subscribing To Connector Events",
|
|
342
|
+
"description": "",
|
|
343
|
+
"author": "Documentation",
|
|
344
|
+
"updatedAt": "Recently",
|
|
345
|
+
"frontmatter": {}
|
|
346
|
+
},
|
|
299
347
|
{
|
|
300
348
|
"contentId": "data-privacy-data-collection",
|
|
301
349
|
"slug": "data-collection",
|
|
@@ -1794,6 +1842,50 @@
|
|
|
1794
1842
|
}
|
|
1795
1843
|
]
|
|
1796
1844
|
},
|
|
1845
|
+
"connectors": {
|
|
1846
|
+
"id": "connectors",
|
|
1847
|
+
"title": "Connectors",
|
|
1848
|
+
"description": "Connectors documentation",
|
|
1849
|
+
"iconType": "Documentation",
|
|
1850
|
+
"articles": [
|
|
1851
|
+
{
|
|
1852
|
+
"id": "connectors-connector-triggers",
|
|
1853
|
+
"title": "Connector Triggers",
|
|
1854
|
+
"description": "",
|
|
1855
|
+
"slug": "connector-triggers",
|
|
1856
|
+
"author": "Documentation",
|
|
1857
|
+
"updatedAt": "Recently",
|
|
1858
|
+
"categoryId": "connectors"
|
|
1859
|
+
},
|
|
1860
|
+
{
|
|
1861
|
+
"id": "connectors-creating-connector-triggers",
|
|
1862
|
+
"title": "Creating Connector Triggers",
|
|
1863
|
+
"description": "",
|
|
1864
|
+
"slug": "creating-connector-triggers",
|
|
1865
|
+
"author": "Documentation",
|
|
1866
|
+
"updatedAt": "Recently",
|
|
1867
|
+
"categoryId": "connectors"
|
|
1868
|
+
},
|
|
1869
|
+
{
|
|
1870
|
+
"id": "connectors-managing-connector-triggers",
|
|
1871
|
+
"title": "Managing Connector Triggers",
|
|
1872
|
+
"description": "",
|
|
1873
|
+
"slug": "managing-connector-triggers",
|
|
1874
|
+
"author": "Documentation",
|
|
1875
|
+
"updatedAt": "Recently",
|
|
1876
|
+
"categoryId": "connectors"
|
|
1877
|
+
},
|
|
1878
|
+
{
|
|
1879
|
+
"id": "connectors-subscribing-to-connector-events",
|
|
1880
|
+
"title": "Subscribing To Connector Events",
|
|
1881
|
+
"description": "",
|
|
1882
|
+
"slug": "subscribing-to-connector-events",
|
|
1883
|
+
"author": "Documentation",
|
|
1884
|
+
"updatedAt": "Recently",
|
|
1885
|
+
"categoryId": "connectors"
|
|
1886
|
+
}
|
|
1887
|
+
]
|
|
1888
|
+
},
|
|
1797
1889
|
"data-privacy": {
|
|
1798
1890
|
"id": "data-privacy",
|
|
1799
1891
|
"title": "Data Privacy & Security",
|
|
@@ -2986,6 +3078,10 @@
|
|
|
2986
3078
|
"browser-extension-how-it-works": "/content/browser-extension/how-it-works.md",
|
|
2987
3079
|
"browser-extension-troubleshooting-extension": "/content/browser-extension/troubleshooting-extension.md",
|
|
2988
3080
|
"browser-extension-use-cases-workflows": "/content/browser-extension/use-cases-workflows.md",
|
|
3081
|
+
"connectors-connector-triggers": "/content/connectors/connector-triggers.md",
|
|
3082
|
+
"connectors-creating-connector-triggers": "/content/connectors/creating-connector-triggers.md",
|
|
3083
|
+
"connectors-managing-connector-triggers": "/content/connectors/managing-connector-triggers.md",
|
|
3084
|
+
"connectors-subscribing-to-connector-events": "/content/connectors/subscribing-to-connector-events.md",
|
|
2989
3085
|
"data-privacy-data-collection": "/content/data-privacy/data-collection.md",
|
|
2990
3086
|
"data-privacy-privacy-policy": "/content/data-privacy/privacy-policy.md",
|
|
2991
3087
|
"data-subject-privacy-data-access": "/content/data-subject-privacy/data-access.md",
|
|
@@ -3478,6 +3574,73 @@
|
|
|
3478
3574
|
}
|
|
3479
3575
|
]
|
|
3480
3576
|
},
|
|
3577
|
+
{
|
|
3578
|
+
"type": "directory",
|
|
3579
|
+
"name": "connectors",
|
|
3580
|
+
"path": "connectors",
|
|
3581
|
+
"children": [
|
|
3582
|
+
{
|
|
3583
|
+
"type": "file",
|
|
3584
|
+
"name": "connector-triggers",
|
|
3585
|
+
"title": "Connector Triggers",
|
|
3586
|
+
"path": "connectors/connector-triggers.md",
|
|
3587
|
+
"contentId": "connectors-connector-triggers",
|
|
3588
|
+
"slug": "connector-triggers",
|
|
3589
|
+
"categoryId": "connectors",
|
|
3590
|
+
"filePath": "/content/docs/connectors/connector-triggers.md",
|
|
3591
|
+
"relativePath": "connectors/connector-triggers.md",
|
|
3592
|
+
"description": "",
|
|
3593
|
+
"author": "Documentation",
|
|
3594
|
+
"updatedAt": "Recently",
|
|
3595
|
+
"frontmatter": {}
|
|
3596
|
+
},
|
|
3597
|
+
{
|
|
3598
|
+
"type": "file",
|
|
3599
|
+
"name": "creating-connector-triggers",
|
|
3600
|
+
"title": "Creating Connector Triggers",
|
|
3601
|
+
"path": "connectors/creating-connector-triggers.md",
|
|
3602
|
+
"contentId": "connectors-creating-connector-triggers",
|
|
3603
|
+
"slug": "creating-connector-triggers",
|
|
3604
|
+
"categoryId": "connectors",
|
|
3605
|
+
"filePath": "/content/docs/connectors/creating-connector-triggers.md",
|
|
3606
|
+
"relativePath": "connectors/creating-connector-triggers.md",
|
|
3607
|
+
"description": "",
|
|
3608
|
+
"author": "Documentation",
|
|
3609
|
+
"updatedAt": "Recently",
|
|
3610
|
+
"frontmatter": {}
|
|
3611
|
+
},
|
|
3612
|
+
{
|
|
3613
|
+
"type": "file",
|
|
3614
|
+
"name": "managing-connector-triggers",
|
|
3615
|
+
"title": "Managing Connector Triggers",
|
|
3616
|
+
"path": "connectors/managing-connector-triggers.md",
|
|
3617
|
+
"contentId": "connectors-managing-connector-triggers",
|
|
3618
|
+
"slug": "managing-connector-triggers",
|
|
3619
|
+
"categoryId": "connectors",
|
|
3620
|
+
"filePath": "/content/docs/connectors/managing-connector-triggers.md",
|
|
3621
|
+
"relativePath": "connectors/managing-connector-triggers.md",
|
|
3622
|
+
"description": "",
|
|
3623
|
+
"author": "Documentation",
|
|
3624
|
+
"updatedAt": "Recently",
|
|
3625
|
+
"frontmatter": {}
|
|
3626
|
+
},
|
|
3627
|
+
{
|
|
3628
|
+
"type": "file",
|
|
3629
|
+
"name": "subscribing-to-connector-events",
|
|
3630
|
+
"title": "Subscribing To Connector Events",
|
|
3631
|
+
"path": "connectors/subscribing-to-connector-events.md",
|
|
3632
|
+
"contentId": "connectors-subscribing-to-connector-events",
|
|
3633
|
+
"slug": "subscribing-to-connector-events",
|
|
3634
|
+
"categoryId": "connectors",
|
|
3635
|
+
"filePath": "/content/docs/connectors/subscribing-to-connector-events.md",
|
|
3636
|
+
"relativePath": "connectors/subscribing-to-connector-events.md",
|
|
3637
|
+
"description": "",
|
|
3638
|
+
"author": "Documentation",
|
|
3639
|
+
"updatedAt": "Recently",
|
|
3640
|
+
"frontmatter": {}
|
|
3641
|
+
}
|
|
3642
|
+
]
|
|
3643
|
+
},
|
|
3481
3644
|
{
|
|
3482
3645
|
"type": "directory",
|
|
3483
3646
|
"name": "data-privacy",
|
|
@@ -5418,6 +5581,37 @@
|
|
|
5418
5581
|
],
|
|
5419
5582
|
"isFile": false
|
|
5420
5583
|
},
|
|
5584
|
+
{
|
|
5585
|
+
"title": "Connectors",
|
|
5586
|
+
"path": null,
|
|
5587
|
+
"children": [
|
|
5588
|
+
{
|
|
5589
|
+
"title": "Connector Triggers",
|
|
5590
|
+
"path": "/help-center/connectors/connector-triggers",
|
|
5591
|
+
"children": [],
|
|
5592
|
+
"isFile": true
|
|
5593
|
+
},
|
|
5594
|
+
{
|
|
5595
|
+
"title": "Creating Connector Triggers",
|
|
5596
|
+
"path": "/help-center/connectors/creating-connector-triggers",
|
|
5597
|
+
"children": [],
|
|
5598
|
+
"isFile": true
|
|
5599
|
+
},
|
|
5600
|
+
{
|
|
5601
|
+
"title": "Managing Connector Triggers",
|
|
5602
|
+
"path": "/help-center/connectors/managing-connector-triggers",
|
|
5603
|
+
"children": [],
|
|
5604
|
+
"isFile": true
|
|
5605
|
+
},
|
|
5606
|
+
{
|
|
5607
|
+
"title": "Subscribing To Connector Events",
|
|
5608
|
+
"path": "/help-center/connectors/subscribing-to-connector-events",
|
|
5609
|
+
"children": [],
|
|
5610
|
+
"isFile": true
|
|
5611
|
+
}
|
|
5612
|
+
],
|
|
5613
|
+
"isFile": false
|
|
5614
|
+
},
|
|
5421
5615
|
{
|
|
5422
5616
|
"title": "Data Privacy",
|
|
5423
5617
|
"path": null,
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Privacy Policy Summary
|
|
2
2
|
|
|
3
|
-
This is a human-readable summary of Yantra's Privacy Policy. For the full legal text, visit [yantra.
|
|
3
|
+
This is a human-readable summary of Yantra's Privacy Policy. For the full legal text, visit [yantra.app/privacy](https://help.yantra.app/privacy).
|
|
4
4
|
|
|
5
5
|
---
|
|
6
6
|
|
|
@@ -95,6 +95,6 @@ You'll always have at least 30 days' notice before changes take effect.
|
|
|
95
95
|
|
|
96
96
|
## Contact
|
|
97
97
|
|
|
98
|
-
**Data Protection Officer:**
|
|
99
|
-
**General inquiries:** support@yantra.
|
|
100
|
-
**Mailing address:** Available in the full privacy policy at [yantra.
|
|
98
|
+
**Data Protection Officer:** support@yantra.app
|
|
99
|
+
**General inquiries:** support@yantra.app
|
|
100
|
+
**Mailing address:** Available in the full privacy policy at [yantra.App/privacy](https://yantra.app/privacy)
|
|
@@ -35,7 +35,7 @@ If you prefer a formal process or need data not available through self-service:
|
|
|
35
35
|
|
|
36
36
|
### How to submit
|
|
37
37
|
|
|
38
|
-
Email **
|
|
38
|
+
Email **support@yantra.app** with:
|
|
39
39
|
|
|
40
40
|
- Subject line: "Data Access Request"
|
|
41
41
|
- Your registered email address
|
|
@@ -84,7 +84,7 @@ JSON exports follow a documented schema:
|
|
|
84
84
|
}
|
|
85
85
|
```
|
|
86
86
|
|
|
87
|
-
Full schema documentation is available in the [API Reference](https://
|
|
87
|
+
Full schema documentation is available in the [API Reference](https://help.yantra.app/help-center/scope-api).
|
|
88
88
|
|
|
89
89
|
---
|
|
90
90
|
|
|
@@ -35,7 +35,7 @@ Most requests can be handled directly in the app:
|
|
|
35
35
|
|
|
36
36
|
For requests that can't be handled via self-service, or if you prefer a formal process:
|
|
37
37
|
|
|
38
|
-
1. Email **
|
|
38
|
+
1. Email **support@yantra.app** with:
|
|
39
39
|
- Subject line: the type of request (e.g., "Deletion Request")
|
|
40
40
|
- Your registered email address
|
|
41
41
|
- Specific description of what you're requesting
|
|
@@ -90,6 +90,6 @@ Yantra can only delete data we hold directly. For data held by integration partn
|
|
|
90
90
|
|
|
91
91
|
## Contact
|
|
92
92
|
|
|
93
|
-
- **Data Protection Officer:**
|
|
94
|
-
- **General support:** support@yantra.
|
|
93
|
+
- **Data Protection Officer:** support@yantra.app
|
|
94
|
+
- **General support:** support@yantra.app
|
|
95
95
|
- **Supervisory authority:** If you're unsatisfied with our response, you have the right to lodge a complaint with your local data protection authority.
|
|
@@ -6,7 +6,7 @@ Welcome to Yantra — your AI-powered search and research assistant. This guide
|
|
|
6
6
|
|
|
7
7
|
## Step 1 — Create Your Account
|
|
8
8
|
|
|
9
|
-
1. Visit [yantra.
|
|
9
|
+
1. Visit [yantra.app](https://yantra.app) and click **Get Started**.
|
|
10
10
|
2. Sign up with email, Google, or GitHub.
|
|
11
11
|
3. Verify your email and complete your profile.
|
|
12
12
|
|
|
@@ -85,4 +85,4 @@ If you're using Yantra with AI Employees, connect your work tools for proactive
|
|
|
85
85
|
|
|
86
86
|
- **Help Center** — You're here! Browse articles by category in the sidebar.
|
|
87
87
|
- **In-app chat** — Click the chat widget in the bottom-right corner.
|
|
88
|
-
- **Email** — support@yantra.
|
|
88
|
+
- **Email** — support@yantra.app (response within 2 hours).
|
|
@@ -86,4 +86,4 @@ Yantra regularly updates to the latest model versions:
|
|
|
86
86
|
|
|
87
87
|
- **Automatic upgrades** — When providers release improved versions, Yantra transitions within 2 weeks after internal quality validation.
|
|
88
88
|
- **Version pinning** — Enterprise customers can pin specific model versions for stability.
|
|
89
|
-
- **Changelog** — All model changes are documented in the [Product Changelog](https://yantra.
|
|
89
|
+
- **Changelog** — All model changes are documented in the [Product Changelog](https://yantra.app/changelog).
|
|
@@ -27,7 +27,7 @@ The Scope API is Yantra's programmatic interface. Anything you can do in the Yan
|
|
|
27
27
|
### 2. Make your first request
|
|
28
28
|
|
|
29
29
|
```bash
|
|
30
|
-
curl -X POST https://api.yantra.
|
|
30
|
+
curl -X POST https://api.yantra.app/v1/search \
|
|
31
31
|
-H "Authorization: Bearer YOUR_API_KEY" \
|
|
32
32
|
-H "Content-Type: application/json" \
|
|
33
33
|
-d '{"query": "best practices for microservices architecture", "mode": "pro"}'
|
|
@@ -101,4 +101,4 @@ All SDKs include TypeScript types, automatic retry logic, and rate limit handlin
|
|
|
101
101
|
|
|
102
102
|
## Full Documentation
|
|
103
103
|
|
|
104
|
-
For detailed endpoint documentation, request/response schemas, error codes, and examples, visit the [API Reference](https://
|
|
104
|
+
For detailed endpoint documentation, request/response schemas, error codes, and examples, visit the [API Reference](https://help.yantra.app/help-center/scope-api).
|
|
@@ -117,4 +117,4 @@ Enterprise customers can request:
|
|
|
117
117
|
- Security architecture white paper
|
|
118
118
|
- Sub-processor list
|
|
119
119
|
|
|
120
|
-
Contact your account manager or email
|
|
120
|
+
Contact your account manager or email support@yantra.app to request any compliance documentation.
|
|
@@ -172,7 +172,7 @@ Audit logs are available in your Yantra dashboard and can be exported for compli
|
|
|
172
172
|
|
|
173
173
|
If you discover a security vulnerability, please report it responsibly:
|
|
174
174
|
|
|
175
|
-
- Email:
|
|
175
|
+
- Email: supoort@yantra.app
|
|
176
176
|
- We take all reports seriously and respond within 24 hours
|
|
177
177
|
- Responsible disclosure timeline: 90 days
|
|
178
178
|
- Recognition for valid vulnerability reports
|
|
@@ -181,6 +181,6 @@ If you discover a security vulnerability, please report it responsibly:
|
|
|
181
181
|
|
|
182
182
|
For questions about our security practices:
|
|
183
183
|
|
|
184
|
-
- Email:
|
|
184
|
+
- Email: support@yantra.app
|
|
185
185
|
- Review our [Privacy Policy](/help-center/data-privacy/privacy-policy)
|
|
186
186
|
- Contact your account manager for enterprise security discussions
|
|
@@ -68,7 +68,7 @@ For full details, see [Student Discounts](/help-center/subscription-billing/stud
|
|
|
68
68
|
|
|
69
69
|
## Getting Started
|
|
70
70
|
|
|
71
|
-
1. **Create your account** at [yantra.
|
|
71
|
+
1. **Create your account** at [yantra.app](https://yantra.app).
|
|
72
72
|
2. **Verify student status** in Settings > Billing > Student Discount.
|
|
73
73
|
3. **Try your first search** — ask any academic question.
|
|
74
74
|
4. **Save your research** — bookmark results to collections organized by class or project.
|
|
@@ -67,6 +67,6 @@ Go to **Settings > Billing** to see:
|
|
|
67
67
|
|
|
68
68
|
## Need Help?
|
|
69
69
|
|
|
70
|
-
- **Billing questions** — Contact
|
|
71
|
-
- **Enterprise inquiries** — Email
|
|
70
|
+
- **Billing questions** — Contact support@yantra.app or use the in-app chat.
|
|
71
|
+
- **Enterprise inquiries** — Email support@yantra.app for custom pricing and volume discounts.
|
|
72
72
|
- **Refunds** — See our [Refund Policy](/help-center/subscription-billing/refund-policy).
|
|
@@ -22,11 +22,11 @@ Most billing issues can be resolved in **Settings > Billing**:
|
|
|
22
22
|
|
|
23
23
|
For issues that require human assistance:
|
|
24
24
|
|
|
25
|
-
| Channel
|
|
26
|
-
|
|
|
27
|
-
| **In-app chat**
|
|
28
|
-
| **Email** (
|
|
29
|
-
| **Phone**
|
|
25
|
+
| Channel | Best for | Response time |
|
|
26
|
+
| ------------------------------ | ------------------------------------------- | ------------- |
|
|
27
|
+
| **In-app chat** | Quick questions, payment issues | < 2 minutes |
|
|
28
|
+
| **Email** (support@yantra.app) | Detailed inquiries, disputes, documentation | < 4 hours |
|
|
29
|
+
| **Phone** | Urgent billing issues (Enterprise only) | Immediate |
|
|
30
30
|
|
|
31
31
|
---
|
|
32
32
|
|
|
@@ -47,7 +47,7 @@ If you see a charge you don't recognize:
|
|
|
47
47
|
|
|
48
48
|
1. Check **Settings > Billing > Invoice History** for the charge details.
|
|
49
49
|
2. Common causes: plan upgrade (pro-rated), annual renewal, tax applied.
|
|
50
|
-
3. If it's still unclear, contact
|
|
50
|
+
3. If it's still unclear, contact support@yantra.app with the charge date and amount.
|
|
51
51
|
|
|
52
52
|
### Double charge
|
|
53
53
|
|
|
@@ -58,7 +58,7 @@ Double charges are rare but can happen if a payment is retried. They are automat
|
|
|
58
58
|
If your invoice details are incorrect (wrong company name, missing tax ID):
|
|
59
59
|
|
|
60
60
|
1. Update your invoice settings at **Settings > Billing > Invoice Settings**.
|
|
61
|
-
2. Contact
|
|
61
|
+
2. Contact support@yantra.app to request a corrected invoice for a past transaction.
|
|
62
62
|
|
|
63
63
|
---
|
|
64
64
|
|
|
@@ -66,7 +66,7 @@ If your invoice details are incorrect (wrong company name, missing tax ID):
|
|
|
66
66
|
|
|
67
67
|
If you disagree with a charge:
|
|
68
68
|
|
|
69
|
-
1. Contact
|
|
69
|
+
1. Contact support@yantra.app within 30 days of the charge.
|
|
70
70
|
2. Include: your account email, charge date, amount, and reason for dispute.
|
|
71
71
|
3. We'll investigate and respond within 2 business days.
|
|
72
72
|
4. If valid, a refund or credit is issued within 5-7 business days.
|
|
@@ -46,7 +46,7 @@ Enterprise pricing is based on:
|
|
|
46
46
|
|
|
47
47
|
## Getting a Quote
|
|
48
48
|
|
|
49
|
-
1. Visit [yantra.
|
|
49
|
+
1. Visit [yantra.app/enterprise](https://yantra.app/pricing) or email **support@yantra.app**.
|
|
50
50
|
2. Share your team size, required features, and integration needs.
|
|
51
51
|
3. We'll schedule a 30-minute discovery call.
|
|
52
52
|
4. Receive a custom proposal within 2 business days.
|
|
@@ -43,7 +43,7 @@ Add your company details so invoices are ready for your accounting team:
|
|
|
43
43
|
|
|
44
44
|
Update at: **Settings > Billing > Invoice Settings**.
|
|
45
45
|
|
|
46
|
-
> **Retroactive changes:** Updated company details apply to future invoices only. To get a corrected past invoice, contact
|
|
46
|
+
> **Retroactive changes:** Updated company details apply to future invoices only. To get a corrected past invoice, contact support@yantra.app.
|
|
47
47
|
|
|
48
48
|
---
|
|
49
49
|
|
|
@@ -83,4 +83,4 @@ All invoices include:
|
|
|
83
83
|
|
|
84
84
|
## Need Help?
|
|
85
85
|
|
|
86
|
-
If an invoice is incorrect, missing, or you need a custom format, contact **
|
|
86
|
+
If an invoice is incorrect, missing, or you need a custom format, contact **support@yantra.app** with your account email and the invoice date.
|
|
@@ -13,7 +13,7 @@ Take advantage of special pricing, discounts, and promotions to get more out of
|
|
|
13
13
|
| **Startup program** | Free Team plan for 6 months | Startups with < 20 employees and < $5M funding |
|
|
14
14
|
| **Nonprofit discount** | 30% off any paid plan | Verified 501(c)(3) or equivalent |
|
|
15
15
|
|
|
16
|
-
_Promotions are subject to change. Check [yantra.
|
|
16
|
+
_Promotions are subject to change. Check [yantra.app/pricing](https://yantra.app/pricing) for the latest offers._
|
|
17
17
|
|
|
18
18
|
---
|
|
19
19
|
|
|
@@ -65,7 +65,7 @@ Eligible startups get the **Team plan free for 6 months**:
|
|
|
65
65
|
|
|
66
66
|
### How to apply
|
|
67
67
|
|
|
68
|
-
1. Visit [yantra.
|
|
68
|
+
1. Visit [yantra.app/startups](https://yantra.app/startups).
|
|
69
69
|
2. Fill out the application (company details, founding date, team size, funding).
|
|
70
70
|
3. Applications are reviewed within 5 business days.
|
|
71
71
|
4. If approved, the Team plan is activated immediately for 6 months.
|
|
@@ -76,6 +76,6 @@ Eligible startups get the **Team plan free for 6 months**:
|
|
|
76
76
|
|
|
77
77
|
Verified nonprofit organizations receive **30% off** any paid plan:
|
|
78
78
|
|
|
79
|
-
1. Email **support@yantra.
|
|
79
|
+
1. Email **support@yantra.app** with your organization's name and proof of nonprofit status (501(c)(3) letter, equivalent certification, or charity registration number).
|
|
80
80
|
2. We'll verify within 3 business days.
|
|
81
81
|
3. The discount is applied to your account and renews automatically.
|
|
@@ -36,7 +36,7 @@ Yantra's refund policy is designed to be fair and straightforward.
|
|
|
36
36
|
|
|
37
37
|
### Via support
|
|
38
38
|
|
|
39
|
-
Email **
|
|
39
|
+
Email **support@yantra.app** with:
|
|
40
40
|
|
|
41
41
|
- Your account email
|
|
42
42
|
- Date and amount of the charge
|
|
@@ -53,7 +53,7 @@ Email **billing@yantra.ai** with:
|
|
|
53
53
|
| Bank transfer | 10–15 business days |
|
|
54
54
|
| Account credit | Instant |
|
|
55
55
|
|
|
56
|
-
|
|
56
|
+
**Where does the refund go?** Refunds are returned to the original payment method used for the charge.
|
|
57
57
|
|
|
58
58
|
---
|
|
59
59
|
|
|
@@ -50,13 +50,13 @@ If you're a VAT-registered business in the EU purchasing from outside your count
|
|
|
50
50
|
|
|
51
51
|
### US tax-exempt organizations
|
|
52
52
|
|
|
53
|
-
1. Email **
|
|
53
|
+
1. Email **support@yantra.app** with your tax exemption certificate.
|
|
54
54
|
2. We'll verify and apply the exemption within 3 business days.
|
|
55
55
|
3. Future invoices will not include sales tax.
|
|
56
56
|
|
|
57
57
|
### Other jurisdictions
|
|
58
58
|
|
|
59
|
-
Contact **
|
|
59
|
+
Contact **support@yantra.app** with your exemption documentation. We'll review and apply applicable exemptions.
|
|
60
60
|
|
|
61
61
|
---
|
|
62
62
|
|
|
@@ -83,4 +83,4 @@ Tax regulations change as jurisdictions update their digital services tax rules.
|
|
|
83
83
|
Taxes collected and remitted to authorities cannot be refunded by Yantra. If you qualify for a tax exemption, apply it proactively for future invoices.
|
|
84
84
|
|
|
85
85
|
**What if my tax ID isn't accepted?**
|
|
86
|
-
Ensure you're entering the correct format for your region. If it's still not accepted, contact
|
|
86
|
+
Ensure you're entering the correct format for your region. If it's still not accepted, contact support@yantra.app with your tax ID and country.
|
|
@@ -16,7 +16,7 @@ If your searches aren't returning any results, try these steps in order:
|
|
|
16
16
|
4. **Switch browsers** — Test in Chrome, Firefox, or Safari to rule out a browser-specific bug.
|
|
17
17
|
5. **Verify your account** — Make sure your subscription is active under **Settings > Billing**.
|
|
18
18
|
|
|
19
|
-
|
|
19
|
+
**Still stuck?** Contact our support team with the exact search query you used and any error messages you saw.
|
|
20
20
|
|
|
21
21
|
### Search results are slow
|
|
22
22
|
|
|
@@ -112,4 +112,4 @@ If a connected service (Slack, GitHub, Jira, etc.) stops working:
|
|
|
112
112
|
- **Enable notifications** in your account settings to receive proactive alerts about issues affecting your account.
|
|
113
113
|
- **Check the Help Center** — many common questions are answered in our guides.
|
|
114
114
|
|
|
115
|
-
|
|
115
|
+
**Need more help?** Reach out to support via the chat widget (bottom-right corner) or email **support@yantra.app**. We typically respond within 2 minutes.
|
|
@@ -0,0 +1,18 @@
|
|
|
1
|
+
export type ContactEmailPayload = {
|
|
2
|
+
serviceId: string;
|
|
3
|
+
templateId: string;
|
|
4
|
+
publicKey: string;
|
|
5
|
+
/** Recipient — use {{support_email}} in the EmailJS template "To email" field */
|
|
6
|
+
supportEmail: string;
|
|
7
|
+
fromName: string;
|
|
8
|
+
fromEmail: string;
|
|
9
|
+
subject: string;
|
|
10
|
+
message: string;
|
|
11
|
+
/** When set, includes feedback_type and feedback_topic; message should be the Details field only. */
|
|
12
|
+
feedbackStructured?: {
|
|
13
|
+
typeLabel: string;
|
|
14
|
+
topic: string;
|
|
15
|
+
};
|
|
16
|
+
};
|
|
17
|
+
export declare function sendContactEmail(payload: ContactEmailPayload): Promise<void>;
|
|
18
|
+
//# sourceMappingURL=sendContactEmail.d.ts.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"sendContactEmail.d.ts","sourceRoot":"","sources":["../../src/utils/sendContactEmail.ts"],"names":[],"mappings":"AASA,MAAM,MAAM,mBAAmB,GAAG;IAC9B,SAAS,EAAE,MAAM,CAAC;IAClB,UAAU,EAAE,MAAM,CAAC;IACnB,SAAS,EAAE,MAAM,CAAC;IAClB,iFAAiF;IACjF,YAAY,EAAE,MAAM,CAAC;IACrB,QAAQ,EAAE,MAAM,CAAC;IACjB,SAAS,EAAE,MAAM,CAAC;IAClB,OAAO,EAAE,MAAM,CAAC;IAChB,OAAO,EAAE,MAAM,CAAC;IAChB,qGAAqG;IACrG,kBAAkB,CAAC,EAAE;QACjB,SAAS,EAAE,MAAM,CAAC;QAClB,KAAK,EAAE,MAAM,CAAC;KACjB,CAAC;CACL,CAAC;AAEF,wBAAsB,gBAAgB,CAAC,OAAO,EAAE,mBAAmB,GAAG,OAAO,CAAC,IAAI,CAAC,CA8BlF"}
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* Sends a message via EmailJS REST API (no SDK dependency).
|
|
3
|
+
* Base template parameters: support_email, from_name, from_email, subject, message.
|
|
4
|
+
* Feedback template adds: feedback_type, feedback_topic (set via feedbackStructured).
|
|
5
|
+
* Paste-ready HTML: templates/emailjs/contact-template.html, templates/emailjs/feedback-template.html
|
|
6
|
+
* @see https://www.emailjs.com/docs/rest-api/send/
|
|
7
|
+
*/
|
|
8
|
+
const EMAILJS_SEND_URL = 'https://api.emailjs.com/api/v1.0/email/send';
|
|
9
|
+
async function sendContactEmail(payload) {
|
|
10
|
+
const template_params = {
|
|
11
|
+
support_email: payload.supportEmail,
|
|
12
|
+
from_name: payload.fromName,
|
|
13
|
+
from_email: payload.fromEmail,
|
|
14
|
+
subject: payload.subject,
|
|
15
|
+
message: payload.message
|
|
16
|
+
};
|
|
17
|
+
if (payload.feedbackStructured) {
|
|
18
|
+
template_params.feedback_type = payload.feedbackStructured.typeLabel;
|
|
19
|
+
template_params.feedback_topic = payload.feedbackStructured.topic.trim() || '—';
|
|
20
|
+
}
|
|
21
|
+
const body = {
|
|
22
|
+
service_id: payload.serviceId,
|
|
23
|
+
template_id: payload.templateId,
|
|
24
|
+
user_id: payload.publicKey,
|
|
25
|
+
template_params
|
|
26
|
+
};
|
|
27
|
+
const res = await fetch(EMAILJS_SEND_URL, {
|
|
28
|
+
method: 'POST',
|
|
29
|
+
headers: {
|
|
30
|
+
'Content-Type': 'application/json'
|
|
31
|
+
},
|
|
32
|
+
body: JSON.stringify(body)
|
|
33
|
+
});
|
|
34
|
+
if (!res.ok) {
|
|
35
|
+
const text = await res.text().catch(() => '');
|
|
36
|
+
throw new Error(text || `Email send failed (${res.status})`);
|
|
37
|
+
}
|
|
38
|
+
}export{sendContactEmail};//# sourceMappingURL=sendContactEmail.js.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"sendContactEmail.js","sources":["../../src/utils/sendContactEmail.ts"],"sourcesContent":[null],"names":[],"mappings":"AAAA;;;;;;AAMG;AACH,MAAM,gBAAgB,GAAG,6CAA6C;AAmB/D,eAAe,gBAAgB,CAAC,OAA4B,EAAA;AAC/D,EAAA,MAAA,kBAAgD;iBAC/B,EAAA,OAAS,CAAA,YAAa;aAC1B,EAAA,OAAS,CAAA,QAAS;cACjB,EAAA,OAAS,CAAA,SAAU;WACtB,EAAA,OAAS,CAAA,OAAQ;WACjB,EAAA,OAAS,CAAA;;AAEpB,EAAA,IAAA,OAAW,CAAA,kBAAmB,EAAA;mBACX,CAAA,uBAAiB,CAAA,kBAA0B,CAAA;AAC1D,IAAA,eAAA,CAAA,cAAgB,GAAA,OAAiB,CAAA,kBAAQ,CAAA,KAAmB,CAAA,IAAM,EAAA,IAAM,GAAA;;AAG5E,EAAA,MAAA,OAAa;cACC,EAAA,OAAS,CAAA,SAAU;eAClB,EAAA,OAAS,CAAA,UAAW;WACxB,EAAA,OAAS,CAAA,SAAU;;;AAI9B,EAAA,MAAA,MAAY,MAAA,KAAW,CAAA,kBAAiB;AACpC,IAAA,MAAA,EAAA,MAAc;AACd,IAAA,OAAA,EAAA;AACA,MAAA,cAAoB,EAAA;AACvB,KAAA;AAED,IAAA,IAAI,EAAC,IAAI,CAAE,SAAG,CAAA,IAAA;AACV,GAAA,CAAA;UACM,CAAA,EAAA,EAAA;IACV,MAAC,IAAA,GAAA,MAAA,GAAA,CAAA,IAAA,EAAA,CAAA,KAAA,CAAA,MAAA,EAAA,CAAA;AACL,IAAC,MAAA,IAAA,KAAA,CAAA,IAAA,IAAA,CAAA,mBAAA,EAAA,GAAA,CAAA,MAAA,CAAA,CAAA,CAAA,CAAA;;"}
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@adminide-stack/yantra-help-browser",
|
|
3
|
-
"version": "12.0.
|
|
3
|
+
"version": "12.0.19-alpha.1",
|
|
4
4
|
"description": "Sample core for higher packages to depend on",
|
|
5
5
|
"license": "ISC",
|
|
6
6
|
"author": "Yantra App",
|
|
@@ -29,7 +29,7 @@
|
|
|
29
29
|
"openai": "^4.52.0"
|
|
30
30
|
},
|
|
31
31
|
"devDependencies": {
|
|
32
|
-
"common": "12.0.16"
|
|
32
|
+
"common": "12.0.16-alpha.20"
|
|
33
33
|
},
|
|
34
34
|
"peerDependencies": {
|
|
35
35
|
"@admin-layout/core": "../../../packages/core",
|
|
@@ -71,5 +71,5 @@
|
|
|
71
71
|
"typescript": {
|
|
72
72
|
"definition": "lib/index.d.ts"
|
|
73
73
|
},
|
|
74
|
-
"gitHead": "
|
|
74
|
+
"gitHead": "ad5a751a77bc0ef33eea1b2e0f4df7a2340cb0ac"
|
|
75
75
|
}
|