🤝 What Are Connections?
Connections let Pulse nodes communicate and collaborate, peer-to-peer.
You can think of them like a friend request for your AI network.
When someone wants to connect with your node, you’ll see a pending connection in your UI. From there, it’s completely up to you:
- ✅ Know and trust the source? Click “Share Key” to approve the connection.
- ❌ Not interested? You can ignore or delete the request — no notifications sent, no awkward goodbyes.
Once approved, the connection becomes active, and you can start building rule-based relationships between your data and theirs.
🔐 Secure by Design
Connections are built with mutual encryption and verification — nothing is shared unless you explicitly allow it. You're always in control of what’s visible and what stays private.
📜 Use in ACL Rules
Once connected, you can assign your connections to Access Control List (ACL) rules, giving them:
- Search access to specific parts of your node
- The ability to generate highlights based on their searches
- Granular permissions — limited by content type, frequency, tags, and more
Want to allow a collaborator to run climate impact searches on your dataset but nothing else? Easy.
Want to let your other device act as a background agent? Done.
✨ Highlights from Connections
When a connected node runs a Quantum Search, your directives still apply.
If the search matches your criteria, Pulse will quietly generate a Highlight, just like it would for your own activity — but tagged with their identity.
This makes Pulse a powerful ambient collaboration layer — one where you stay in control, but never miss what matters.
🛠️ Manage With Ease
You can:
- See all pending and active connections at a glance
- Remove or disable connections at any time
- Apply ACL rules with point-and-click control in the UI