UX writing: Enhance visibility for Export Objects feature

[ka0ula]

Context

In the Intelligence module, each Object page offers an Export button (top right) that allows users to export an object's full threat context — including all or a subset of its associated relationships (SROs).

This feature directly addresses a recurring client need: extracting a scoped, threat-specific dataset from the platform. However, it remains largely undiscovered — clients are not aware it exists, and the current entry point (a generic "Export" button) does not communicate what it actually does.

A client recently requested the ability to export data specific to a threat, including automatic updates when new relationships appear. While the automated/live sync is out of scope for now, the manual export feature already covers the core need, it just needs to be surfaced properly.

Problem

• The Export button label is too generic — it doesn't hint at the "threat context" scope of the export

• No in-product signposting guides users toward this capability

• In the modal, we talk about Categories, while in reality, we are talking about Relationships.

Acceptance criteria

• A user landing on an Object page for the first time can discover and understand the export feature without external guidance
• The export scope (object + relationships) is clearly communicated before and during the export flow

[alexane-bougeardbebin-sekoia]

@ka0ula

Suggestions:

- Button:
- Export threat context (based on the screenshot, we are not limited to enlarge the button)
- Export context (if space limitation do apply)
= > By adding "Context," we signal to the analyst that they aren't just getting the Object (e.g., an IP address), but the "who, what, and how" connected to it. And "Threat context" is the exact term clients use when they ask for this data, so mirroring it closes the gap between their mental model and the UI affordance. It also signals scope: this isn't a table export, it's a structured package around a specific object.

- Modal:
- Title : "Export threat context"
- subtitle: "Select the relationships to export for OBJECT_NAME - OBJECT_TYPE"
- Radio buttons:
- All threat context" -> "All relationships" + subtitle: "Includes all relationships linked to this object XXX total" with a total count (removing ambiguity)
- "Selected categories" -> "Selected relationship types" (it corrects the terminology inconsistency) + subtitle : "Choose which type to include in the export"
- Conditional relationship picker : "Categories" -> "Relationship types"
NB: Please do me some favors and 1. add Uppercase at the beginning of types titles (ie; "targets "-> "Targets") 2. add the number of relationships included in each type, 3. add the option to select all. 🥺
- Bonus: 🙏
- Live footer count: it would be great to have a footer: CTA stays disabled and shows "Select a scope to continue" until a valid selection is made. Once active, it shows exactly how many objects will be exported ("X objects will be exported"), making the consequence of each selection tangible before committing.

To address the client's request for live sync we can add a banner in the modal to set the right expectation: the export is a point-in-time snapshot, and re-exporting is the manual equivalent. My suggestion: "This export captures the current state of OBJECT_NAME's relationships. Re-export at any time to include newly added data."

To address the discoverability topic: it could be great if you could use a targeted tooltip (Feature Tour) for users who land on an Object page for the first time.

Headline: Export the full picture

Body: Need this threat data for an external report? You can now export this object along with all its related indicators and TTPs in a single bundle.

CTA: Got it

-> Maxime and Pierre are working on this kind of tuto for onboarding, they might be able to help (ot maybe even eager to try on an easy task)

PS: I don't get why we have an "*" after "Select a format": selecting a kind of export is also mandatory, isn't it?

[ka0ula]

@alexane-bougeardbebin-sekoia thank you for your help!
Did you design the mockup in your answer?

[alexane-bougeardbebin-sekoia]

@ka0ula Claude did with instructions. I didn't have Alexandre tuto at that time so I didn't know how to do the bridge with Figma :/