Secret-access exceptions and follow-up¶
A Secret-access exception records a limited decision allowing a named person or governed group to use particular Secret information through HiveAI. It identifies the information, business purpose, justification and a finite access window. It is useful when someone needs narrowly scoped assistance with sensitive work.
For example, an authorized administrator may grant a colleague access to one incident record for a defined investigation period. That decision does not grant access to every incident, make the colleague an administrator, or approve a business action.
Availability¶
The backend implements creation, current-access lists, known-record details, expiry checks and revocation. Current 06 Final Screens describe Secret access in Tenant Admin and guidance from HiveAI. The inspected frontend does not yet implement this experience. The task guide describes the intended screens and marks unfinished steps; it does not establish deployment.
Creating access is not yet a complete guided journey: the inspected setup screen requires an exact person or group and source to be supplied from the work context. A separate conditional review screen shows how a prepared grant would be confirmed. There is no verified picker or connected preparation flow to bridge them.
Who is involved¶
| Reader | Responsibility |
|---|---|
| Colleagues and external participants | Explain the need and use only information available to their identity and workspace |
| Managers | Identify the exact work, intended recipient, purpose and appropriate access period |
| Executives | Assign accountable decision makers and review business necessity; titles alone do not confer product authority |
| Authorized tenant administrators | Inspect and, where permitted, grant or revoke an exact exception |
| Support and platform staff | Distinguish access decisions, unavailable screens and uncertain outcomes without disclosing sensitive material |
| Engineers, designers and operators | Maintain current authority checks, decision evidence and recovery boundaries in the private reference |
A person may be permitted to inspect relevant decisions while lacking authority to change them. Creation and revocation require additional organization-head or delegated tenant-administrator authority. A platform support role is not automatic authority inside every tenant.
What a decision contains¶
A grant binds one named person or governed group, one exact information source, Secret classification, purpose, justification, start time and end time. The current governed-group model uses organization units and positions; it does not mean any informal mailing list or chat group.
Supported classified source checks cover records, memos and official letters. An arbitrary reference saved by a management integration is not proof that HiveAI supports or can read that source. The administrator must establish the actual source and the recipient's current authority.
Secret and Confidential are distinct classifications. A request phrased as “confidential information” does not automatically require or justify a Secret exception.
Access changes over time¶
| Situation | Meaning |
|---|---|
| Starts later | The decision exists, but its access window has not opened |
| Active | Its time window is open and it has not been revoked; other access checks still apply |
| Expired | Its end time has passed; the decision can remain available for inspection through a known record |
| Revoked | An authorized decision ended this exception; the same grant cannot be restored |
The active list is a view of currently eligible decisions visible to the reader. It excludes future, expired and revoked grants. It is not a complete historical register, and an empty list does not prove that nobody ever received access.
The inspected implementation does not support editing or extending an existing grant, or cancelling a future-start grant before its start. Seek authorized follow-up if such a decision needs correction; do not treat the absence of a revoke button as proof the decision disappeared.
A grant and usable information¶
A saved exception is one part of access. HiveAI still checks the current identity, group membership where relevant, source, purpose, time window, source permissions and organizational scope. Current licensing, Advanced capability, governance settings, classified provider approvals and operational controls also matter. A changed policy or unavailable source may prevent use while the grant record still exists.
An organization head has a separate classified-access authority path subject to the applicable controls. The exception list therefore cannot serve as an inventory of every possible route to Secret information.
Giving permission does not guarantee an answer, complete an action, or bypass action review. If HiveAI uses paid processing, normal credits and usage controls still apply. This feature makes no promise of a separate price, unlimited processing or automatic activation of infrastructure.
Evidence and retention¶
The record retains who granted access, the subject's validated identity information at creation, the reason, time window and decision reference. Revocation records its actor, time, reason and reference. A historical display name does not establish the person's current name or employment status.
Expiry and revocation end eligibility under this exception; they do not erase its decision history, retract information already seen, delete source records or guarantee cancellation of work already underway. Broader data export, deletion and retention remain separate organizational processes.
See the task guide for inspection, conditional grant review, revocation and recovery. Operational action stop/retry belongs to the action guide; shared organizational guidance has its own work-memory lifecycle.
Escalate a concern about access¶
Use the governance and incident guide when an access decision raises a wider concern. Revoking an exception, suspending a capability and closing an incident are separate actions with different authority and evidence.