Ask Microsoft Copilot for the Report Instead of Building It
Copilot reads the same WebWork data such as tracked hours, attendance records, billable totals, project budget figures and activity levels and answers in the chat.
Microsoft Copilot Time Tracking Integration
Microsoft Copilot time tracking connects the hours your team logs to Copilot Chat, Copilot in Excel, Researcher and Cowork. Copilot reaches your documents, your calendar and your mail, and the time tracker has been the one system still sending you to a separate dashboard. WebWork's MCP connector closes that distance: Copilot gets the reports, timesheets, leave requests and approvals in your workspace, at the permission level your WebWork role already carries. Microsoft 365 Copilot reads them, a Copilot Studio agent acts on them, and both run inside Microsoft 365.
Integrate Copilot with WebWork
MCP Documentation
No credit card Cancel anytime
What You Can Run From a Microsoft Copilot Conversation
When you integrate WebWork with Microsoft Copilot, directly in the chat you can get what you would otherwise go to the dashboard for. Copilot reads the WebWork workspace live at the moment you ask, so the answer reflects what is in the workspace now.
Questions That Cross Several Reports Come Back as One Answer
Some questions need the attendance report, the pending timesheet list and the project budget at the same time. Copilot calls each WebWork tool in sequence and gives you one answer, instead of three reports to line up side by side.
Workspace Administration Runs Through the Copilot MCP Connector
Teams that track time with Copilot reach the administrative side of WebWork through the same connection. The Copilot MCP connector publishes timesheet and leave approvals, time requests, member and team changes, shifts, job titles, contracts, custom fields and expenses. Microsoft 365 Copilot reads all of it, and an agent built in Copilot Studio runs the actions. Every call runs as the signed-in person at that person's WebWork role and no higher, and deletions and archiving need an explicit confirmation before anything happens.
- Timesheets
- Leave Approvals
- Time Requests
Copilot MCP
- Team Changes
- Shift Schedules
- Contracts & Expense
What the WebWork MCP Connector Gives Microsoft Copilot
| Area | What your Copilot agent can do |
|---|---|
| Timesheets | View, submit, unsubmit, approve, and reject |
| Time requests | Request missed time, approve or reject requests |
| Leave | Request leave, approve or reject, check balances and policies |
| Reports | Time, activity, activity descriptions, apps and websites, daily attendance, daily timeline, real-time, GPS, and task reports |
| Timers | Start, stop, and check the running timer |
| Time entries | Add, view, edit, and delete tracked time |
| Members | Invite, update, archive, and restore |
| Teams | Create teams, add and remove members |
| Job titles | Create titles and assign them to members |
| Shifts | Create shifts, assign and unassign members |
| Contracts | Create, view, update, and delete |
| Projects | Create, view, update, and archive |
| Project groups | Group projects, add or remove projects from groups |
| Tasks | Create, assign, update, delete, and see assignees |
| Task comments | Add, edit, and delete comments on tasks |
| Expenses | Add, edit, and delete expenses, browse categories |
| Client access | Give outside viewers read access to chosen projects |
| Custom fields | Create and manage custom data fields |
| Workspace | List workspaces, workspace info, connection health |
| Screenshots | List and review captured screenshots |
| Job sites (GPS) | Define and manage locations for on-site tracking |
The table covers what the WebWork MCP connector publishes to any client that connects to it. Microsoft 365 Copilot reads this data in real time through its federated connector, and the actions like approvals, edits and workspace changes, run through an agent you build in Copilot Studio and publish to the Microsoft 365 Copilot and Teams channel.
Who Can Set Up the Microsoft Copilot Time Tracking Integration
Connecting Microsoft Copilot to WebWork Time Tracker takes an approval on each side.
On the WebWork side, only a Workspace Owner or an Executive Manager with a verified email address can create the connection. On the Microsoft side, a federated connector is configured by an administrator in the Microsoft 365 admin center, so an individual Copilot user cannot add WebWork on their own.
Once it is connected, Copilot inherits the WebWork role of the person signing in and sees nothing above it. A tool that role does not permit returns a permission error rather than a result.
How to Connect Microsoft Copilot to Your Time Tracker
There are two ways to connect Copilot to a time tracker, depending on whether you are adding WebWork to Microsoft 365 Copilot itself or building your own agent. Microsoft 365 Copilot reads the workspace through its federated connector, and approvals and other changes run through the Copilot Studio agent in Method 2.
Method 1
Microsoft 365 Copilot
In the Microsoft 365 admin center, an administrator adds WebWork under Copilot > Connectors. Copilot reads the workspace in real time from then on, using each person's own WebWork sign-in.
Method 2
Copilot Studio
In Copilot Studio, you add WebWork as a tool on an agent, pointing it at the MCP server URL https://mcp.webwork-tracker.com/mcp. The agent runs the actions as well as the reads, and you can publish that agent to the Microsoft 365 Copilot and Teams channel.
Both methods use an OAuth2 app created in WebWork under Settings > REST API > OAuth2 Apps, and each connection gets its own app.
Approvals and Reports Without Leaving Microsoft 365
Connecting the two produces three things:
- Pending timesheets reviewed and closed out in Microsoft 365, with the hours and activity descriptions attached to the answer
- Numbers returned in whatever shape the question asked for, rather than the shape the report builder produces
- Member, project and team changes made in the same exchange as the question that raised them
Approvals and workspace changes run through an agent built in Copilot Studio and published to the Microsoft 365 Copilot and Teams channel, so they happen in the same place as the reports.
24/7 Global Customer Support
Ranked Top Quality on G2
99.9% Uptime in the Last 90 Days
Advanced Security and Data Privacy
What Operations Teams Say About WebWork
Practical productivity insights for teams
Before using WebWork Time Tracker, we struggled with lack of visibility into how time was actually being spent, especially across multiple tasks and team members. It was difficult to identify where delays were happening, and a lot of decisions were based on assumptions rather than real data. After implementing it, we now have a clear, structured view of daily work activity, including time spent on tasks, productivity levels, and overall team performance. This has made it much easier to track progress, identify bottlenecks, and improve accountability without constant follow-ups.
Easy to use with clear productivity tracking
Overall, my experience with WebWork Time Tracker has been positive. It has been reliable for daily use, accurate in tracking time, and helpful for managing workflow. It's a solid upgrade after transitioning from other platforms, and it fits well for remote work environments.
Works With Every MCP Client, Not Just Microsoft Copilot
WebWork's MCP connector is not specific to Microsoft. Any assistant that supports the Model Context Protocol connects to the same server at the same URL, so the WebWork and Copilot integration publishes the same tools a team connecting from Claude or ChatGPT receives. What differs between them is the setup screen each client puts in front of you.
Explore Full MCP ServerFAQ
Microsoft Copilot time tracking means running your time tracking workspace from Microsoft 365 rather than a separate dashboard. WebWork's MCP connector gives Copilot access to the workspace data and actions your role already covers, so reports, timesheet checks, leave balances and approvals are handled by describing what you want. Microsoft 365 Copilot reads the workspace directly, and approvals and other changes run through an agent you build in Copilot Studio.
It works with two Copilot surfaces. Microsoft 365 Copilot connects to WebWork as a federated connector, configured by an administrator in the Microsoft 365 admin center. Agents built in Copilot Studio connect to the same server through the Studio onboarding wizard, with generative orchestration turned on. Both reach the same set of WebWork tools. The federated connector reads the workspace, and a Copilot Studio agent also runs the actions, including timesheet and leave approvals. You can publish that agent to the Microsoft 365 Copilot and Teams channel so both work in the same place.
On the WebWork side, a Workspace Owner or Executive Manager with a verified email address can connect. On the Microsoft side, a Microsoft 365 administrator configures the federated connector for the tenant, so an individual Copilot user cannot add it alone.
It sees what the connecting account sees based on its role permissions, and nothing beyond that. You grant read, write and administrative access during sign-in, deletions and archiving require explicit confirmation, some actions send real email and the assistant says so first, and the connector keeps no separate copy of your workspace data. Disconnecting revokes access immediately.
Microsoft uses "Copilot connectors" for its own feature that links Copilot to outside services. WebWork supplies the other end: a standard Model Context Protocol server that Copilot connects to, publishing WebWork's timers, reports, timesheets, approvals, projects, tasks and member management as tools Copilot can call.
Voted Top Time Tracking Software of 2026
Put Your Time Tracker Inside Microsoft 365
Integrate Copilot with WebWork
No credit card Cancel anytime