Personal and team insights¶
HiveOrbit brings recorded work contributions, recognition and supporting context into two read-only views. My Orbit helps a person understand their own recorded contribution. Team Orbit helps a manager discuss patterns across their current direct reports. The views support an evidence-led conversation; a score alone does not explain a person's circumstances or determine an employment decision.
The intended screens have been inspected in 06 Final Screens. The current frontend contains a workspace entry and unfinished feature areas. The backend supplies personal and team reads, with material gaps in calculation details, coverage context and the points-history connection. These guides describe the intended journey and the current limits, not a deployed feature guarantee. Confirm availability in your workspace.
Start with the personal and team guide. Engineering and operational references are delivered separately through the private documentation repository.
Use recognition and supporting evidence to interpret badge sharing, recorded claims, proof access and later corrections. Those readers have separate permissions and unresolved delivery/visibility limits; an insight preview does not grant access to evidence.
Use contribution and recognition configuration to understand role expectations, policy versions, sharing choices and campaigns. The administration guide explains intended changes and their current limits; reading insights or evidence does not grant permission to change settings.
Use contribution sources and reconciliation to understand where evidence comes from and what source health proves. The inspected normal processing path updates periods from individual claims and derives source confidence from the current proof; complete period accumulation and independently reconciled coverage remain unresolved. Read values together with those limits rather than treating a Complete label as certification of all work.
What each view answers¶
| View | Useful questions | Limits |
|---|---|---|
| My Orbit | What contribution measure was recorded for me? Which dimensions and periods support it? What points and recognition are available? | Missing evidence remains unavailable. The measure, recognition points and awards are different things. |
| Points history | Which awarded or correcting entries were issued in the chosen history window? | Detailed calculation evidence is incomplete; the current connection requires repair. A page of entries does not prove a whole-window total. |
| Team Orbit | Who reports to me now? What recorded measures and supported signals are available for them? | Historical charts use the current reporting roster. Team signal counts cover the visible page. Private recognition and evidence links remain restricted. |
Contribution, points and recognition¶
A contribution measure is a recorded analytical result with dimensions, weights, a period and evidence context. It is not a balance to spend. A missing dimension is not a zero, and an absent period is not evidence that no work took place.
Recognition points are signed entries: awards can add points and corrections can change the net amount. The selected-period points total covers issue dates in that period. Lifetime points and contribution-category totals cover retained ledger history; they need not equal the selected-period total.
Recognition includes badges, milestones, recognition levels and achievement titles. My Orbit presents a bounded recent selection and milestone progress when the effective visibility policy permits the read. Recent recognition can come from outside the selected history window. A progress value and its target describe recorded progress; they do not predict an award date or promise a benefit.
For example, a contribution measure of 85.5, 88 points issued during a month and 640 lifetime points describe three different quantities. Those numbers are illustrative, not product defaults or a promised outcome.
Who can see what¶
Personal access and team access are separate permissions within the workspace's HiveOrbit access. A manager's organizational title alone does not grant every view. Team Orbit resolves the people currently reporting to that manager; it does not open every employee in the organization.
The current team read withholds member recognition when historical award visibility cannot be verified. It also omits private evidence links from member signals and team summaries. An optional View action needs additional access to the employee view; team access alone does not guarantee it.
If access is missing, ask the workspace administrator to check your product access, permissions and employee/reporting record. Do not interpret an access failure as an empty team or no contribution. Subscription and licensing administration remain part of workspace product access; this feature introduces no documented price or purchase promise.
Access and readiness¶
Available views depend on your workspace's HiveOrbit access and your permissions. The first permitted view in the platform's fixed order is the default; it is not a personal preference or a recommendation about what needs attention. Permission to enter a view does not guarantee that its information is ready.
Readiness distinguishes whether the required contribution sources have supported contracts and whether today's required source-health records are complete and free of recorded blockers. It also checks whether the organization has an active, applicable HiveOrbit setup and can currently process contributions. A healthy daily check does not certify every historical score, and unavailable health information is not the same as a confirmed healthy result.
An incomplete or paused setup can keep the views unavailable even when source health is otherwise healthy. Read when recorded work can be scored and preparing HiveOrbit to understand which work periods are eligible and what activation requires.
These results do not establish whether a frontend has been deployed to your workspace. Administrators and support should check access, current setup, source health and actual service availability separately; opening or refreshing a view does not complete those checks automatically.
Department selection follows your permitted scope. Ordinary department viewers receive their current department; an organization head with department access can receive organization choices. A listed department does not guarantee that it has eligible people or available contribution records. See department and organization insights for those distinctions.
How to interpret time and history¶
The workspace calendar determines the meaning of a day, week, month or year. Check its displayed timezone before comparing an issue date with a work date. History ends at the selected period and includes the preceding requested periods. Changing the history length can change the entries included in points history and the context available for a comparison.
An open period can still receive more evidence. A gap stays a gap: do not estimate a missing score from neighboring bars. A positive or negative change is descriptive; supported signal labels have additional evidence and comparison requirements.
Team history averages the available recorded measures of current direct reports for each period. People without an available measure do not contribute a zero. Consequently, the included people can differ between periods even when the current roster count is unchanged. The view does not provide a complete historical staffing reconstruction or a reliable headcount-adjusted performance comparison.
Decisions for managers and executives¶
Use the views to identify questions worth discussing: whether evidence is complete, which work was included, what changed in role or reporting context, and whether a dependency affected an outcome. Confirm the period, available measures and scope before comparing figures.
Team averages are not rankings, percentiles or a fair comparison between different roles by themselves. The current service does not prove a common model and weighting across every member of an aggregate. Page-level signal counts are not a percentage of the whole department or organization. Under recognized is a review signal, not entitlement to an award; Overload compares recorded work with a configured standard, not a diagnosis of health, effort or personal capacity.
Use department and organization insights for their intended scope when available, including the Licensed People directory and Employee Contribution. Recognition administration, evidence investigation, configuration and source reconciliation retain their separate documentation ownership. Shared team/department/organization database compatibility also needs repair and verification; a designed view does not establish successful loading.
Availability and information quality¶
The current source can return a stored confidence label while detailed source coverage, role context or cohort comparison remains unavailable. Do not replace missing information with the populated design examples, infer 100% coverage from a label, or display an unavailable numerical placeholder as a measured zero. The guide explains the intended evidence panels and their present limits.
Administrators and support should distinguish missing product access, missing reporting records, incomplete evidence, missing configuration and an unavailable service. Refreshing a read requests current information; it does not rebuild historical scores, issue recognition, repair a source or change a person's reporting line.
This is a reviewable draft for users, managers, executives and administrators. Technical reconciliation, connected frontend behavior, environment delivery and the initial reader walkthrough remain distinct acceptance steps.
Access through the assistant¶
HiveAI includes a separate assistant connection for requesting HiveOrbit information, including personal, team, department and organization insights, recognition, evidence and configuration information. Access and reliable delivery through this connection still need verification. These guides do not establish that the assistant can retrieve these results in your workspace. Confirm the connected experience before relying on it.
An assistant response cannot expand your workspace, people or evidence access. Check the selected period, filters, where the information came from and whether more results remain. A short answer is not a complete directory or export, and a response time alone does not prove that all its underlying information was refreshed together. The same recognition and evidence limits and department and organization limits still apply.
An available-operation label or an authorization message does not mean that a setting was saved. Changes requested through the assistant require the separate governed review and confirmed result, along with the source application's current rules. When an outcome is unclear, preserve the original request rather than repeating a change to obtain a clearer response.
HiveAI organization intelligence¶
HiveAI organization intelligence provides a separate view of AI use, quality indicators and service controls. Its reader guide explains scope, privacy and unavailable measures. Its bounded work-metric tools do not replace HiveOrbit's documented contribution views or establish individual productivity.