Enterprise side · Data access and OData services
- Connect sources and define business metrics
- Provide queryable data through OData
- Verify user identity and data permissions
Business systemsWarehouseFiles
EngineHub/WorkBuddy
Give WorkBuddysecure access toenterprise data.
Enterprise data analysis in WorkBuddy, wherever you work.
EngineHub turns enterprise data into governed OData services. Query authorized data in your own WorkBuddy client, without connecting the agent directly to source databases.
WorkBuddy, wherever you work. One governed enterprise data service.
EngineHub provides an OData service layer between enterprise data and the agent. Database connections stay under enterprise management; employees analyze authorized results through the service.
User side · WorkBuddy across locations
- Analyze in your own WorkBuddy client
- Retrieve authorized results over HTTPS
- Ask follow-up questions and create reports
Access across locations requires reachable EngineHub and OData endpoints for authorized users. Source databases need not be exposed to user networks. Internal-only deployments still require an appropriate network path. Explore the OData standard
Three ways to connect an agent to enterprise data.
Swipe sideways to see the full comparison.
| Dimension | EngineHub + WorkBuddy | Direct database agent | Vendor web agent |
|---|---|---|---|
| Data connection | OData services provided by EngineHub | A source database or a database-connected execution tool | The vendor agent backend connects to data sources |
| Agent runtime | The user's own WorkBuddy environment, separate from the source database network | An execution environment that can reach the source database | A vendor-hosted or privately deployed agent backend |
| Travel and remote work | Keep using WorkBuddy wherever the services are reachable and access is authorized | Internal-only databases require an internal runtime, VPN or another controlled network path | Remote use through the available web entry point, with the experience provided by that interface |
| Everyday interface | WorkBuddy is recommended; data services can also support other adapted agents | Depends on the chosen agent's database connectivity | Primarily the vendor web interface; other clients depend on available APIs |
This compares deployment patterns, not every vendor. Some products also offer APIs, connectors or hybrid deployments; assess their specific versions and configurations.
Prepare the data
Discover sources and plan cleaning and joins with AI-ETL. Retain quality checks and exceptions that need human review.
Sources / AI-ETL / Data assetsDefine the business meaning
Bring metric definitions, field descriptions and provenance into your data services, grounded in your business conventions.
Metadata / Definitions / LineageControl access centrally
Verify identity and data permissions on the server. Use short-lived credentials for read-only queries and retain relevant records.
Identity / Authorization / AuditThe same question. Access comes before answers.
Explore how WorkBuddy accesses data through EngineHub with a business analysis example.
Choose a user and query scope, then run the example.
Try a national query as a regional manager to explore the access boundary.
Interactive illustration using built-in sample data. No connection to WorkBuddy, enterprise data or a model service.
Useful data. Clearly defined boundaries.
Secure access depends on identity, credentials, queries and result handling. Validate the available controls and configuration in your deployment.
Source data
EngineHubIdentity / Permissions / Read-only service
WorkBuddyAuthorized results reach the client and configured model environment
Verify the person before providing data
Browser sign-in and device approval establish identity. Request short-lived analysis credentials; the data service checks the user's permitted scope.
Keep source credentials on the server
WorkBuddy queries EngineHub OData services without a source connection string or network access to the database. Enterprise-side services manage the database connections.
Understand where results go
Authorized results reach the client and may be used by a model. Confirm query scope, model providers, retention and deployment boundaries before connecting.
Make data access reviewable
Review available records to understand data access. Validate allowed queries, denied requests and permission changes during your connection pilot.
Source credentials ≠ device credentials ≠ short-lived analysis credentials
Start with one business question. Connect it to WorkBuddy.
Your administrator prepares the data service. Employees approve their device, then use authorized data in WorkBuddy.
Prepare the data service
Agree on sources, metric definitions and permissions. Your administrator configures EngineHub.
Install the connection skill
Install the EngineHub connection Skill provided for your enterprise environment in WorkBuddy.
Sign in and approve the device
Follow the Skill to your enterprise sign-in page, verify the device and approve access to your available skills.
Ask your first business question
Describe the analysis in WorkBuddy. Verify the allowed scope, then review the result and its supporting data.
Already have EngineHub?
Use the connection skill and platform URL supplied by your administrator, then follow the prompt to make your first connection.
Use my installed enterprise connection Skill to connect to EngineHub. Open the browser for sign-in and device approval. Once connected, list the data I can access and wait for my business question.
Before you connect.
How does OData separate the agent from the database?
OData is a standard data access protocol built on HTTP. EngineHub exposes enterprise data through OData services, which WorkBuddy queries using service URLs and authorization credentials. The agent therefore needs no direct source database connection. EngineHub and the data service enforce access; remote use depends on service reachability and enterprise authorization, not automatic network access from the protocol.
Why recommend WorkBuddy?
WorkBuddy provides natural-language interaction, tool execution and work product creation. EngineHub recommends it as the client for employees, with data preparation and access governance centrally managed by the enterprise.
WorkBuddy has connectors. Why add EngineHub?
Connectors make tools reachable. EngineHub additionally organizes cross-system data, business definitions, permissions and relevant audit records into reusable enterprise data services. Validate its value against your own use case.
Does data leave our environment?
Source storage and query result handling are different boundaries. Authorized results reach WorkBuddy and may enter the selected model service. Confirm networking, models and retention for your deployment; a private source database alone does not keep every result in your network.
Does installing the skill give access to all enterprise data?
Your administrator first configures services, accounts and permissions. Employees use only data allowed for their identity. Verify the client version, runtime dependencies and connection method in your environment.
Can other agents connect?
Other agents can be adapted through suitable Skills, OData and open interfaces. WorkBuddy is our recommended client; data services remain independent. Validate each client's capabilities and version separately.
Connect on WeCom. Let's talk about your enterprise data.
Scan with WeChat to contact EngineHub sales support. Tell us about your business and explore how WorkBuddy can securely use your enterprise data.
- Discuss business questions and existing data systems
- Define access permissions and deployment needs
- Arrange a product demo and connection pilot
EngineHub sales
WeCom · WeChat Customer Service
Scan with WeChat to chat with our sales support team.
On mobile, open the enlarged QR code and save a screenshot, then select it from your photos in WeChat Scan.