Administer Knowledge and Asset reference settings

Knowledge and Asset settings support operational processes but do not grant every operator administration rights. Readers, authors, publishers, equipment managers and status administrators have different responsibilities.

Before you start

Confirm module availability, record ownership and action permissions. Use the current Knowledge/Asset guides for detailed workflows. Reference-list and publication rules take precedence over broad role summaries.

Steps

1. In Knowledge Management settings, maintain the relevant Knowledge Bases, access/visibility and publishing responsibilities.
2. Test Published public content with an ordinary user and internal content with appropriate staff. Editing an article alone does not grant publishing authority.
3. For AgentHub Service Desk Instructions, verify the separate Agent Supervisor authority and instruction lifecycle rather than assuming ordinary knowledge-manager/admin rights suffice.
4. In conditional Asset Management settings, review Categories and the available model/stockroom reference management, with the appropriate register-management rights.
5. Have an administrator maintain Asset lifecycle and operational status lists. Check ordering and supported flags before changing them.
6. Validate assignment, return, stock grouping, retirement/reactivation and disposal evidence after material reference changes.
7. Review how categories feed models, stock thresholds and employee-equipment profiles before changing shared values.

Asset permission nuance

Asset managers have broad operational/register privileges but do not write administrator-only status definitions. Category and reference-data permissions differ from status-list restrictions. Check the applicable action rather than extrapolating status restrictions to every reference record.

Lifecycle name checks

Active, Retired and Disposed participate in documented name-based transition checks. Some reconciliation rules also use status-name heuristics. Renaming or translating them can alter behaviour despite apparently unchanged flags.

Expected result

Knowledge reaches the right audience through authorized publication, and equipment reference data supports a coherent custody/lifecycle process.

Important behaviour

Knowledge publication, Service Desk Instruction governance and Asset status configuration are different controls. Asset pause-clock fields do not imply a ticket SLA for equipment. Reconciliation acknowledgement records review and does not automatically repair source data.

Related guides