Handling Sensitive Information with Sera

Handling Sensitive Information with Sera

Some of what flows through your organization is not meant for everyone. Sera is built to notice that automatically and to keep it separate, private, and accountable. This article explains how.

---

Where sensitive items live

The Sensitive Review database is admin-only and lives in a separate Notion teamspace outside your main workspace. This separation is structural, not just a permission setting. Ordinary members of your organization cannot see it at all, so a sensitive flag never leaks into shared views.

What Sera flags as sensitive

Sera watches for genuinely sensitive material and flags it for admin review. This includes:

• Personal disclosures shared in confidence
• Safety and conflict matters between people
• Specific financial amounts or disputes
• Legal matters
• Confidential data shared in error
• Genuine harm risk

When any of these is detected, Sera creates a Sensitive Review record and does not expose the content anywhere team-visible.

What Sera deliberately ignores

Just as important is what Sera does not flag. To keep the Sensitive Review queue meaningful, she auto-excludes ordinary noise:

• Formatting errors
• Technical glitches
• Routine logistics
• Anything already captured in the Risks database

This means the items that reach Sensitive Review are the ones that truly warrant a careful, private read.

---

The notification

When a sensitive item is flagged, Sera sends an email to the admin notification address. Whoever holds that inbox is alerted immediately, so time-sensitive matters are not waiting to be discovered on someone's next login.

The review workflow

Sensitive items follow a clear, accountable lifecycle:

1. Pending Review — newly flagged, waiting for an admin
2. Reviewed — an admin has read it and added Review Notes
3. Dismissed — reviewed and found not to be a concern
4. Escalated — reviewed and raised to the appropriate people

Every reviewed item records Reviewed By and Reviewed Date. That accountability trail matters: it shows who saw a sensitive matter and when, which is exactly what you want when the content is delicate.

---

How sensitive and restricted content is kept out of sight

There are two layers of protection, and they work differently:

• Sensitive and Restricted records never appear in team-visible queues. They are confined to the admin-only teamspace.
• Restricted content is removed before it even reaches Sera. The most protected material is stripped upstream, so Sera never stores, processes, or logs it in the first place.

Together these mean the more sensitive something is, the less of the system ever touches it.

---

The confidentiality levels

The system uses exactly three confidentiality levels, and it is worth knowing them precisely:

• Standard — ordinary content, visible in normal team views
• Sensitive — flagged for admin review, kept out of team-visible queues
• Restricted — the most protected tier, removed before Sera processes it

The level is always one of these three. The word Confidential is not a level in this system, so if you see it used, it does not map to anything Sera enforces. Use Standard, Sensitive, or Restricted.

---

The principle behind it

Sensitive handling in your Living Memory Hub follows a single principle: the more private the content, the earlier and more completely it is contained. Ordinary members never see it, admins are notified and held accountable for reviewing it, and the most restricted material never enters the system at all.

Key points

The Sensitive Review database is admin-only and lives in a separate Notion teamspace outside the main workspace. Sera flags personal disclosures, safety and conflict matters, specific financial amounts or disputes, legal matters, confidential data shared in error, and genuine harm risk, while auto-excluding formatting errors, glitches, logistics, and anything already captured in Risks. Each flagged item triggers an email to the admin notification address and moves from Pending Review to Reviewed with review notes, then to Dismissed or Escalated, with Reviewed By and Reviewed Date recorded for accountability. Sensitive and Restricted records never appear in team-visible queues, Restricted content is removed before it even reaches Sera, and the confidentiality levels are exactly Standard, Sensitive, and Restricted, never Confidential.