Runs in your environment
The customer operates the Docker deployment, network, monitoring and backups.
HR Companion Trust Center
HR Companion connects Microsoft Teams to Oracle HCM while preserving the customer’s control over identity, permissions, infrastructure and operations.
The customer operates the Docker deployment, network, monitoring and backups.
Oracle identities, roles and data permissions continue to determine what each user can access.
HR Companion is delivered under a perpetual licence included in the fixed-price engagement.
Fusioh is not granted production access by default. Any support intervention must be authorised by the customer.
Architecture
The interaction stays within services controlled by the customer or provided under its contracts. Fusioh does not operate a separate HR database.
01
Authenticated employee or manager
02
Identity verification and signed user context in the customer-operated runtime
03
Agent orchestration and approved MCP tool calls
04
User-context verification and delegated Oracle access
05
Authoritative data, roles and business rules
HR Companion presents Oracle data and prepares supported actions in Teams. It does not create a Fusioh-hosted copy of the customer’s HCM data.
Delivery model
HR Companion is delivered through a fixed-price implementation. Fusioh retains ownership of the product, while the customer receives a perpetual licence to deploy, operate and internally modify the delivered version, with source-code access subject to the signed agreement.
Included in the implementation engagement.
The delivered version can be adapted for internal needs.
Infrastructure remains under the customer’s control.
Maintenance and assistance are contracted separately.
Microsoft and Oracle services continue to be supplied under the customer’s own agreements.
Identity & access
HR Companion is designed to act within the user’s permissions, never beyond them. The customer’s Oracle configuration remains the source of authority.
Teams identity tokens are checked on the server before the user context is accepted.
Internal user context is signed, expires quickly and is not inferred from a display name.
The intended production configuration calls Oracle with the authenticated user’s delegated identity.
Available tools and queries are allowlisted, and manager actions are limited to authorised populations.
Data & retention
Each platform has a distinct role and lifecycle. The deployment-specific retention schedule is agreed with the customer rather than hidden behind a generic SaaS statement.
| Location | What may exist there | Retention owner |
|---|---|---|
| LocationOracle HCM | What may exist there Authoritative HR records and business data. | Retention owner Customer, according to its Oracle policy and agreement. |
| LocationOracle AI Agent Studio | What may exist there Authorised session and execution traces for monitoring and troubleshooting. | Retention owner Customer, according to its Oracle configuration and agreement; Oracle publishes no universal trace duration. |
| LocationCustomer HR Companion runtime | What may exist there Limited user, tenant and conversation-routing metadata required for Teams interactions. | Retention owner Customer, according to the deployment configuration and project retention schedule. |
| LocationMicrosoft Teams / OneDrive | What may exist there Messages and generated files delivered to the user. | Retention owner Customer, according to its Microsoft 365 retention policies. |
Oracle’s published AI assessment states that customer data does not persist in the underlying large language model after a prompt is processed, and that prompt data does not train that model. AI Agent Studio monitoring sessions and execution traces are a separate layer available to authorised administrators.
Oracle’s public monitoring documentation does not state a universal retention duration for those traces. The applicable lifecycle must be confirmed against the customer’s Oracle configuration and agreement.
Responsible AI
HR Companion helps employees and managers find information, prepare actions and complete authorised HR workflows. It is not intended to make autonomous decisions about recruitment, compensation, promotion, disciplinary action or termination.
Responses are constrained by the authenticated user’s Oracle access and the tools enabled for the delivery.
Supported write flows include a preview and an explicit, short-lived confirmation associated with the user.
Enabled capabilities, sensitive fields and confirmation controls are documented for each customer delivery.
Shared responsibility
HR Companion is not a Fusioh-operated SaaS. Product security and infrastructure operations are therefore assigned to different parties.
| Fusioh | Customer | Microsoft & Oracle |
|---|---|---|
| Fusioh Security of the delivered software | Customer Hosting, network and container platform | Microsoft & Oracle Security and availability of their cloud services |
| Fusioh Product code and deployment guidance | Customer Secrets, monitoring and backups | Microsoft & Oracle Tenant services under customer agreements |
| Fusioh Remediation of delivery non-conformities covered by the agreement | Customer User access and Oracle/Teams configuration | Microsoft & Oracle Their retention and service controls |
| Fusioh Optional maintenance and assistance | Customer Updates and operation of modified versions | Microsoft & Oracle Their contractual commitments |
Evidence
Evidence is shared at the level appropriate to the request. We do not present supplier certifications as Fusioh certifications.
Frequently asked questions
No. It is deployed and operated in the customer’s environment. There is no recurring Fusioh platform subscription.
Fusioh retains product ownership. The customer receives a perpetual licence, source-code access and internal modification rights under the signed agreement.
Not by default. Any support access must be specifically authorised, time-limited and controlled by the customer.
Oracle HCM remains the system of record. HR Companion does not maintain a central Fusioh-hosted copy of that data. Limited technical metadata may exist inside the customer-operated deployment, while AI Agent Studio may retain monitoring traces.
Fusioh does not set a single retention period for a customer-operated deployment. Retention depends on local configuration, Microsoft and Oracle services, and the project-specific schedule.
Fusioh does not train a separate model with production HR data. Oracle states that customer data does not persist in the underlying model after processing and that prompt data does not train that model; Oracle monitoring traces remain a separate consideration.
Delivery acceptance and agreed warranty obligations are defined in the project terms. Ongoing support, maintenance and compatibility updates are optional services contracted separately.
Security review
Tell us which evidence your team needs. We will map the delivered product, the customer-operated environment and the Oracle and Microsoft responsibilities instead of sending a generic SaaS security pack.
Commercial enquiries submitted through this site are covered by our privacy notice. Privacy & legal