Skip to content
This repository was archived by the owner on Aug 31, 2026. It is now read-only.

docs(libraries): replace platform by product - #60

Closed
jpkha wants to merge 1 commit into
mainfrom
jpkha-patch-1
Closed

docs(libraries): replace platform by product#60
jpkha wants to merge 1 commit into
mainfrom
jpkha-patch-1

Conversation

@jpkha

@jpkha jpkha commented Jul 16, 2026

Copy link
Copy Markdown
Member

Proposed changes

Related issues

  • Closes #

How to test this PR

Checklist

  • The PR title follows the Conventional Commits convention type(scope?): description (#issue)
  • I signed my commits
  • This PR is linked to an issue
  • I consider the submitted work as finished
  • I tested the code for its functionality
  • I added/updated the relevant documentation
  • Where necessary, I refactored code to improve the overall quality

Further comments

Copilot AI review requested due to automatic review settings July 16, 2026 09:50
@Filigran-Automation Filigran Automation (Filigran-Automation) changed the title Replace platform by product docs(libraries): replace platform by product Jul 16, 2026
@Filigran-Automation

Copy link
Copy Markdown
Member

🤖 [AI-generated]

Hey jpkha! 👋 Thanks a lot for opening PR #60 — really appreciate the contribution! 🙏

I just had a quick look and I think the description could be enhanced a little to help reviewers get through it faster. I haven't changed anything in your description — just a gentle suggestion:

Area What could help Suggestion
Proposed changes Left as two empty bullet points A short summary of what changed (e.g. "Replaced 'platform' with 'product' terminology across the custom-dashboards doc") would help reviewers scan the intent quickly
Related issues "Closes #" left empty Since this repo requires every PR to be linked to an issue, adding the actual issue number here (and in the title) would help close the loop
How to test this PR Left empty A quick note on how to verify the doc change (e.g. "Preview the custom-dashboards.md page and confirm terminology is consistent") would be useful
Checklist All items left unchecked Ticking off the relevant ones once verified helps reviewers trust the PR is ready

💡 If helpful, the CONTRIBUTING.md / PR template walk through what to include: https://github.com/FiligranHQ/xtm-hub-docs/blob/main/CONTRIBUTING.md

No rush at all — thanks again for contributing to the project! 🚀

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the Custom Dashboards documentation to replace references to “platform” with “product”, primarily in the context of OpenCTI deployment and registration wording.

Changes:

  • Rewords multiple sentences in the custom dashboards library docs to say “OpenCTI product(s)” instead of “OpenCTI platform(s)”.
  • Updates one-click deploy and registration-related phrasing accordingly.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

A comprehensive library of custom dashboards is now available on the XTM Hub,
providing seamless access to curated threat intelligence data.
Currently, the library focuses on custom dashboards that can be directly deployed to OpenCTI platforms and created by our Filigran Team.
Currently, the library focuses on custom dashboards that can be directly deployed to OpenCTI products and created by our Filigran Team.
Comment on lines +13 to +15
Organizations can benefit from one-click deployment capabilities that integrate directly with registered OpenCTI products,
while maintaining completely free access without any cost barriers.
Additionally, the platform supports public browsing, allowing users to explore available dashboards without requiring authentication.
Additionally, the product supports public browsing, allowing users to explore available dashboards without requiring authentication.
Authenticated access offers the complete feature set,
including the ability to browse and download custom dashboards,
deploy custom dashboards directly to OpenCTI platforms,
deploy custom dashboards directly to OpenCTI products,
Comment on lines +51 to +52
into their OpenCTI products. This process involves downloading the custom dashboard file,
navigating to your OpenCTI product, and using the standard Import functionality
Comment on lines +57 to +58
into your OpenCTI product (available from OpenCTI 6.7.10).
Before utilizing this functionality, your OpenCTI product must be properly registered in the XTM Hub (see [OpenCTI registration documentation](/user/opencti-registration)),
Comment on lines +61 to +62
choose your target product if multiple products are registered,
and wait a few seconds until successful integration is confirmed in your OpenCTI product. You will be redirected to the newly created dashboard.
Users deploying dashboards must maintain appropriate OpenCTI permissions,
including UPDATE/CREATE capability for custom dashboards.
Platform registration involves enrolling OpenCTI platforms in the XTM Hub. No newline at end of file
product registration involves enrolling OpenCTI products in the XTM Hub.
@jpkha jpkha closed this Jul 16, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants