Administration & integrations
Prepare knowledge for AI assistance
Keep source material current, test answers against your records, and define when a person must review the result.
3 min read·Reviewed
On this page
The Knowledge Base connects organisational material with the information an assistant can retrieve. REX-OPS supports internal articles and document-grounded AI workflows. The quality of an answer depends on the material, its relevance and the controls around the specific workflow.
Select authoritative material
Start with documents and guidance that your team is authorised to use: project information, approved policies, procedures and frequently asked questions. Identify an owner for each source and distinguish current guidance from superseded material.
- Prefer an approved source over several conflicting copies.
- Keep dates, project references and document titles meaningful.
- Remove unnecessary personal or confidential information before ingestion.
- Confirm which people and AI workflows may use each source.
The public documentation on this website is separate from your company's Knowledge Base. Uploading internal material should follow your workspace's administration and data-handling process.
Prepare readable sources
Review the source document before ingestion. Scanned tables, ambiguous headings and conflicting figures may need clarification. A document being accepted by an upload flow does not establish that every page or number can be retrieved accurately.
After processing, test whether the important information is represented correctly. Use questions that require the exact project, policy or numerical context rather than only asking for a general summary.
Evaluate answers with real scenarios
Choose a small set of questions your team frequently needs to answer. Include ordinary questions, incomplete requests and cases where the available material does not contain an answer.
- Check whether the response uses the correct project and current source.
- Compare factual details and amounts with the original record.
- Check any source references exposed by the workflow.
- Confirm that uncertainty leads to review rather than an invented answer.
Set review boundaries
Decide which outputs can support internal work and which require human approval. Pricing commitments, contractual interpretation and financial decisions need the responsible person's judgement. Do not assume that a fluent answer is an approved statement to a buyer.
For an automated action, confirm the role, permitted operations and review process of that particular workflow. Visibility of a source and permission to change an operational record are separate decisions.
Maintain the knowledge lifecycle
When a policy, project document or price reference changes, update the authoritative source and review how the knowledge workflow handles the old version. Re-run the questions affected by the change. Keep a route for staff to report inaccurate or incomplete answers.
See Knowledge Base, AI Layer and roles and access. Ask the team which AI capabilities are available in your configured workspace.
