Content rules

By default, a document’s audience depends on where it came from: content from a shared integration is visible to everyone in the organization, and content from a personal integration is visible only to the person who connected it. Content rules let admins refine those defaults based on what a document actually says. There are two kinds of rules. Filter rules narrow. Sharing rules widen. Both are written by admins in Settings, and both are judged by the same machinery when content arrives.

​

Filter rules

Filter rules exist for the categories that must never spread: compensation, HR matters, legal disputes, credentials, whatever your company decides. They apply to any content that would otherwise reach more people than those who connected it. When a filter rule matches a document:

• If the document came in through a shared integration, nobody can see it.
• If it came in through a personal integration and a sharing rule would have widened it, it stays with the person who connected it.

Nothing is deleted. The content stays stored, held back from the company brain. Admins can review what a filter caught to check for false positives, and see which rule matched and why. They do not see the private content of others in the process. Filter rules are set up by admins and apply to everyone in the organization. Members cannot opt out of them.

​

Sharing rules

Content from personal integrations is private by default, which keeps a lot of useful knowledge out of reach: the customer call in one person’s Granola, the vendor negotiation in another’s inbox. Sharing rules are how that content reaches the team on purpose. A sharing rule says “content like this is meant for the whole organization”, for example conversations with customers, or meetings about product. Admins write the rules. Each person then decides, for their own connections, which rules to turn on. A rule that a person has not turned on is never even evaluated against their content. When a sharing rule a person turned on matches one of their documents, the document is offered to the organization. Whether it is shared automatically or after the owner confirms depends on how confident the match is, described below.

​

Writing a rule

A rule has a name and a description. The description is what Hyperspell uses to judge content, so write it the way you would explain the category to a new colleague. Vague descriptions produce vague matches. A few things to keep in mind:

• Rules are judged on content, not on titles. A document called “Q3 planning” that spends a paragraph on salary bands will match a compensation filter.
• One good example beats three adjectives. If you can, add a sentence or two of the kind of content you mean.
• Start with filter rules for the categories that would cause real harm if they spread. Add sharing rules once those are in place.

​

How rules are applied

Rules are evaluated when content arrives, not when someone asks a question. This keeps queries fast and makes every decision reproducible.

​

Confidence and review

Each match carries a confidence score. Where the score falls decides what happens:

• Above the automatic threshold, the rule acts on its own.
• In the middle band, the match is queued for the owner to review.
• Below the ignore threshold, nothing happens.

Filter rules act on any match. The admin who set them up already decided that the category should not spread, so there is nothing to ask. Sharing rules are more careful. New sharing rules start with automatic sharing turned off, so every match asks the owner first. Queued matches appear in that person’s Inbox, one card per document, showing the source, the title, the rule that matched, and the passage that triggered it. The owner clicks Share or Dismiss. Nothing leaves their view until they do. A document that matches both a sharing rule and a filter rule is never shown in the Inbox. The filter has already decided.

​

What changes when you change a rule

Sharing is sticky and filters are live. Once a document has been shared with the organization, it stays shared unless a filter rule narrows it. Filter rules are re-evaluated whenever they change, so removing one lets the content it was holding back widen again. The only way to take back something that was shared is a filter rule that matches it. This is deliberate: sharing should be a decision people can trust, not something that flickers as configuration changes.

​

What you will see in the dashboard

Admins find rules under Settings, in two lists: filter rules and sharing rules. Each rule can be created, edited, paused, or deleted. Configuration and content are kept apart on purpose, so this page never shows anyone’s documents. Each member has two personal surfaces:

• Sharing lists the admin’s sharing rules as toggles. Turning one on applies from that moment forward. A secondary action lets you check your existing content against the rule too.
• Inbox shows the documents waiting for your decision. Acting on a card brings the next one into view. When the queue is empty it says so.

Admins see only their own content in their Inbox.

​

Guarantees

These hold regardless of how rules are configured:

• Nothing widens past its defaults without a matching rule, the owner’s opt-in, and, when the match is uncertain, the owner’s approval.
• Filter rules beat sharing rules. Filtered content always stays with the people who connected it, or with nobody if it came from a shared integration.
• Sharing fails closed. If a rule cannot be evaluated, nothing is shared.
• Sharing never retracts by itself. Pausing or deleting a sharing rule leaves existing shares standing.
• Every grant is explainable: which connection, which rule, which version, who decided.
• A document outlives its first owner. As long as one active connection still holds it, it stays in the brain.
• Nobody, admins included, sees another person’s private content in the process of managing rules.

​

Related