Manage HiveOrbit configuration¶

Use this guide to review contribution settings, prepare role expectations, assign people and administer recognition campaigns. The intended navigation and controls follow the final product designs. The frontend remains in progress, and the backend and design differences described here must be resolved before these journeys can be treated as a working deployed experience.

Before you begin¶

Confirm that you are in the correct organization and have permission to manage HiveOrbit configuration. Agree the business purpose and effective date of a change with its owner. For a campaign, agree the benefit, resource limit and responsible person. For a profile or assignment, confirm the actual work expectations with the relevant manager.

Read configuration concepts and limits first if you are unfamiliar with profiles, effective periods or recognition policies. A missing model, policy or calendar is a setup issue; do not use an unrelated edit to manufacture an initial configuration.

Before the first activation, the newer backend provides separate setup preparation and choices; its final-screen journey still needs reconciliation. This guide retains the previously inspected ordinary configuration sequence. After HiveOrbit has been enabled or scheduled, authorized configuration repairs may remain available while scoring is paused if the organization still has active product access. A cancelled scheduled start retains that history. Saving a repair does not restart scoring; review setup before making a new activation decision.

Open and review configuration¶

1. Open HiveOrbit for the organization and select Configuration under Administration.
2. Start with Overview. Review the calendar and the returned settings, profiles, assignments and campaigns.
3. Open the relevant section: Scoring & recognition, Role profiles, People assignments or Campaigns.
4. Read the selected item's current or scheduled status and effective dates before choosing an action.

If Configuration is absent, resolve access with your administrator. Another HiveOrbit view being available does not grant configuration access. The overview is not an assessment that every dependency is ready. Missing or unavailable sections must remain distinguishable from legitimate empty collections.

The design shows summary counts and example scores. Use returned collection totals and actual definitions in the implemented experience; do not treat example numbers, a count of mapping records or a filtered page as a complete organization count.

Review the model and catalog¶

In Scoring & recognition, review the applicable model, priority adjustments, bonus rules, badge families and recognition visibility. Check the effective date and any scheduled successor. Model and catalog details are reference information; the available edit controls cover permitted tenant settings.

If the installed model or catalog is unsupported or inconsistent with its release definition, ask support to investigate. Ordinary tenant settings do not install a replacement scoring model.

Use the organization's returned choices and limits. The standard bonus cap is 25%, although the current design example says 20%. The standard dimensions and badge families also differ from several design examples. A displayed example called Quality or Delivery excellence must not be treated as a new badge family. If the choices are unavailable, resolve the underlying setup instead of typing an invented replacement into a closed choice list.

Change the first weekday¶

1. From Overview, choose Edit calendar when available.
2. Review the organization's timezone and select the intended First weekday.
3. Confirm when the change should become effective with the administrator responsible for the change.
4. Choose Save calendar only in an implemented flow that supplies and confirms that effective start.
5. Reload the calendar and verify the returned week start and effective dates.

Current design gap: the dialog offers an editable timezone and omits the required effective-start control. The implemented change accepts a first weekday and effective start, retaining the existing timezone. This guide cannot verify a timezone-edit or complete scheduling journey from that dialog. Ask support to resolve organization timezone changes through their actual owner. A successful save can schedule a change; it does not necessarily apply it immediately.

Update priorities and bonus rules¶

1. Open Scoring & recognition and choose Update priorities.
2. Enter Effective from for the policy.
3. Review each dimension and its percentage-point adjustment. Use Add dimension when needed. Keep each adjustment between −5 and +5 and avoid duplicate dimensions.
4. Review each bonus rule's name, eligibility, percentage, proof requirement and start. An end is optional; when present it must follow the start. Use Add bonus rule for another condition.
5. Choose suggestions, or use custom values only where the available authoring controls permit them. A custom condition still needs an agreed meaning and a supported implementation.
6. Resolve validation feedback, then choose Save changes. Reload the policy and confirm which version is current or scheduled.

Each bonus rule requires a positive percentage no greater than 25%. Rules with the same identity cannot have overlapping effective windows. A rule's start/end and the containing policy's start are distinct; verify both. The configuration save does not establish that the combined bonuses, all referenced conditions or a historical recalculation have been validated. Do not copy the design's 20% example as a universal limit.

If a successor is already scheduled, the old policy may have no further edit action. A scheduled policy is not an editable draft. Do not repeatedly submit against the old item; review the returned versions and ask support when another correction is needed.

Change a badge policy¶

1. In Scoring & recognition, find the returned badge family and open its edit action.
2. Set whether the family is enabled and whether its awards are intended to be publicly visible within the organization.
3. Enter only the thresholds offered for that family. Follow their units, lower bounds, maximum values and increments.
4. Set Effective from, then choose Save badge settings.
5. Reload and check the saved version and timing. Check recognition separately; saving the policy does not issue an award or prove its visibility has changed.

Threshold changes can tighten the catalog rules, not relax them. Whole-number counts and decimal thresholds are different inputs. A validation error about a known family or threshold requires checking the returned catalog, not renaming a field to match a design example. If the displayed maximum and saved validation disagree, report both values to support.

Change recognition visibility¶

1. Open Edit visibility in Scoring & recognition.
2. Select the default audience and the audiences the organization allows. Keep private sharing available; the default must belong to the allowed set.
3. Review the switches for high-impact contributions, team achievements and cohort achievements.
4. Set the effective start and choose Save visibility.
5. Confirm the saved policy and review the recognition view with appropriate access checks.

The design uses Self for the private choice. The complete supported audience set includes organization sharing as well as private, team and department. Do not assume a configured audience is an enforced confidentiality boundary: the current recognition limitations remain unresolved. The private fallback definition also does not prove that a new organization already has a persisted visibility policy.

Create or edit a role profile¶

1. Open Role profiles. Search the collection or use its next/previous controls, then choose Create role profile or select a draft and choose Edit draft.
2. Enter a clear profile name and select compatible activities, work types and complexity.
3. Enter the optional expected standards that matter for this role: effort, cycle time, completion count, response time and enabling work. Keep entered values nonnegative.
4. Define contribution dimensions, their positive weights and whether they are required. The required weights must total exactly 100%, with at least one required dimension.
5. Define source coverage: the source, activity, work type, required or advisory coverage and a readable label. Each source/activity/work-type combination must be distinct.
6. Review the collaboration expectation and comparison cohort. Use suggestions or supported custom entry, with an agreed interpretation.
7. Choose Save draft, then reopen the returned draft to review it.

Saving a draft is not activation. A profile needs at least one required source rule before activation. The design's selected-profile example totals only 85% across its required dimensions; that example must be reconciled with the enforced rule. A profile cannot be assigned merely because its draft appears in a list.

Activate a profile¶

1. Select the intended draft in Role profiles and review its details.
2. Choose Activate profile and read the confirmation.
3. Confirm the intended effective start through the implemented flow before activating.
4. After success, reload and verify the saved version and whether it is current or scheduled.

Activation makes the version immutable. Existing assignments retain their recorded profile version; activation does not automatically move everyone to the new version. The current confirmation design does not show how the required effective start is chosen, so that part of the flow still needs implementation/design reconciliation. Do not assume “activate” means “replace all current assignments now.”

Assign or change a person's profile¶

1. Open People assignments. Choose Needs assignment for people without a current or scheduled mapping, or Assigned people to review existing mappings.
2. Search the relevant list. Each view keeps its own search and paging context.
3. Choose Assign role profile for an unresolved person, or Change profile for a current mapping that offers that action.
4. Confirm the person's identity, select the intended profile version and enter Effective from. The profile must be activated and effective at that start, and the person must be active then.
5. Choose Assign profile or Save assignment, as shown by the action.
6. Reload the affected lists. Confirm the selected version, start and current/scheduled status.

A scheduled mapping appears in Assigned people and removes the person from Needs assignment even before its start. An assigned-list count can include current and future mapping records for the same person. It is not necessarily a count of unique people with a currently effective profile.

Current design gap: assignment dialogs show an optional Effective to field. The implemented action accepts only the profile and effective start; it does not accept that end. A successor closes the prior mapping at the new start. Do not rely on a typed end date or an automatic profile recommendation. These administration screens save changes one person at a time.

Create or edit a campaign¶

1. Open Campaigns and choose Create campaign, or select an editable draft.
2. Enter the campaign name, duration, period and eligibility condition.
3. Enter the qualification start and exclusive end. The interval must be nonempty and lie inside the configured period; it may be shorter than the whole period.
4. Define the objective criterion, target measure, basis and supporting meaning. Use suggestions or supported custom criteria.
5. Review the fixed qualification order. It cannot be rearranged.
6. Select a supported benefit, enter its description and any nonnegative value, and provide a nonnegative budget or inventory limit. Both limits may be supplied.
7. Select the responsible person from the available owner choices. Confirm that the person has the practical authority and access to carry out fulfilment.
8. Choose Save draft, then reopen and review the saved details.

Quarterly campaigns shown in an example are unsupported. Currency symbols in examples do not establish a stored currency: confirm the business units separately. An owner choice represents a person, not a department-wide permission grant. Entering a budget does not purchase credits, reserve funds or schedule a payment.

Start and close a campaign¶

Select a draft, review its saved criteria and choose the returned activation action. Read the confirmation and confirm only when the intended programme and timing are correct. Activation is rejected once the configured period has ended; an expired draft can still be editable.

The intended interface offers a close action on an active campaign after its configured period ends. Review the campaign and choose Close campaign when that action is available. Closing records the exact configured period end and prevents the closed campaign from accepting further qualifications. Existing awards remain available for fulfilment.

Activation records a state change. Automatic candidate evaluation, ordered allocation and award creation have not been verified as a connected production flow. Do not tell participants that a benefit has been awarded merely because the campaign is active. Closure's time enforcement also needs backend verification; the interface's offered action is not sufficient proof of server enforcement.

Review awards and record fulfilment¶

1. From Campaigns, switch to Awards, or open the selected campaign's award action.
2. Use the campaign and status filters, search and next/previous controls to find the award. These controls have their own context and do not change the campaign list.
3. Review the recipient, campaign, reserved value or units, reservation time and latest progress.
4. Choose Record progress only where offered. Select In progress or Delivered as the next status.
5. Enter a proof reference. For Delivered, also enter the delivery reference for the completed benefit.
6. Choose Save progress, then reload and confirm the recorded status and latest reference.

The next status must differ from the current status. An award already in progress therefore needs its permitted next transition, not another in-progress save. Delivered awards have no further progress action. The current design's in-progress companions incorrectly show delivery-reference guidance as required; it is required for Delivered only.

A reference is text identifying evidence in the organization's fulfilment process. It is not a proof upload or an automatically checked payment receipt. Verify the real delivery before marking an award Delivered. If that final status was recorded incorrectly, contact the responsible administrator/support; this surface provides no reversal.

Recover from conflicts and failed saves¶

For support, provide the organization, section, item name, intended change, effective date, observed message and whether a reload shows the change. Share only the minimum necessary information through the organization's support channel. A screenshot or note should not expose unrelated employees or confidential evidence.