Support

Copilot and AI tools

For: Admins and members

How the OneShift agent and the OneShift connector reach Microsoft 365 Copilot, how people sign in, and what to know before you connect another AI tool.

01

Two ways to use OneShift in Copilot

OneShift appears in Copilot in two ways. Both come in the same app as the Teams agent, so you add the app once.

WayWhat it is
The OneShift agentThe agent you chat with in Teams, available in Copilot. It has the same commands: Summarize day, Enter time and Submit timesheet.
The OneShift connectorA set of tools Copilot can call to log time and look up timesheets, projects, budgets and statements, and combine the answer with the rest of your Microsoft 365 work.

You need:

  • A Microsoft 365 Copilot license for each person who uses OneShift in Copilot.
  • A OneShift workspace and account for each person.
  • The OneShift app added to your organization. SeeRoll out the Teams agent.

The connector needs no extra step in your tenant beyond the app. Its sign-in registration is OneShift’s own.

02

Make the agent available

The agent is the Teams app, declared a second time for Copilot. Once the app is in your organization, the agent is available there.

  1. Add the app to your organization as described inAllow the app in your organization.
  2. Make sure your policies allow the app for the people who should use it in Copilot.
  3. Ask a member to open Microsoft 365 Copilot and use the OneShift agent. People see one OneShift agent, in Teams and in Copilot.

What the manifest says, so you can check the app:

Manifest entryValue
Bot scopespersonal and copilot
Copilot agentcopilotAgents.customEngineAgents, one entry of type bot with the app’s id

Preview feature, not verified in a customer tenant yet. Microsoft documents custom engine agents in Copilot as a preview, and availability can differ per tenant. OneShift has seen the agent answer in Copilot in its own test environment only. If the agent does not appear in yours, contact OneShift.

03

The OneShift connector

The connector lets Copilot call OneShift directly. It is part of the same app, as an agentConnectors entry.

Manifest entryValue
idoneshift
displayNameOneShift
descriptionLog time and look up timesheets, projects, budgets and statements in OneShift.
ServerA remote MCP server, https://api.oneshift.ai/mcp in the production app
AuthorizationOAuthPluginVault, an OAuth registration made by OneShift
ToolsDescribed in toolDescription.json in the app: six for every member and eleven read-only tools for managers

Copilot calls the tools as the signed-in person. A person with no management role gets none of the manager tools.

Not verified in a customer tenant yet. The connector in Copilot chat has not been exercised yet. If Copilot says it could not verify the connection, contact OneShift.

04

Signing in

Everyone signs in to OneShift with their own OneShift account. The sign-in is separate from their Microsoft 365 sign-in.

  • The agent asks the first time a person writes to it. The card and steps are the same as in Teams: Signing in.
  • The connector asks the first time Copilot needs OneShift. The person signs in with their OneShift account.

OneShift signs people in through WorkOS AuthKit. A person in several workspaces picks the workspace at sign-in, and the tools then work in that workspace only. Access tokens last five minutes and are refreshed in the background.

05

What members and managers can ask

What a person can do depends on their permissions in OneShift, not on Copilot.

WhoWhat they can ask
Every memberReview their day and the suggested entries, read their time entries, see their timesheet, log time, and submit their timesheet.
ManagersWhich timesheets wait for approval, how a project is tracking against its budget, what is on a customer’s latest statement. These tools only read; answers link to the page in OneShift where you act.

The full list of tools by role, and what they cannot do, is in the Agent guide underConnecting AI tools.

06

Connect other AI tools

OneShift is an MCP server (Model Context Protocol), so other AI tools can use the same tools. Today the API accepts only AI tools that OneShift has allowed.

SettingValue
Endpointhttps://api.oneshift.ai/mcp
TransportStreamable HTTP, without sessions
Sign-inOAuth through WorkOS AuthKit, as the person who connects
DiscoveryAn unauthenticated call answers 401 and points to /.well-known/oauth-protected-resource, which names the authorization server
ResourceThe tool must send resource (the endpoint URL) on both the authorize and the token request

Which tools can connect

The API accepts a token only when its OAuth application is on an allow-list that OneShift maintains. Today that is the OneShift bot’s application and the one used by the Copilot connector. A tool that brings its own application is rejected. OneShift uses fixed registrations, not automatic client registration. WorkOS also marks tokens issued to automated agents, and OneShift refuses those: a person signs in.

To use another AI tool, contact OneShift with the tool’s name. A connected tool acts as the person who signed in.

Not verified with other tools yet. OneShift has not exercised the endpoint with any MCP client other than its own bot and Copilot. Token refresh over time is also not exercised yet.

07

What is shared

A connected tool sees only what the person who signed in can already see in OneShift.

  • Permissions come from OneShift. Manager tools use the person’s permissions stored in OneShift, with the same rules as the matching page in the app. These can lag a role change made in WorkOS until the next sync.
  • No hints about other data. A key the person may not see answers like a key that does not exist, and the workspace is always the one chosen at sign-in.
  • No private content. A manager gets review flags and hours, never the contents of someone’s mail, meetings or chats.
  • Few changes. The only changes a tool can make are logging the person’s own time and submitting their own timesheet. Submitting locks the week, so clients are told to ask first.
  • It is recorded. Changes appear in History under the person’s name, marked as made via an AI tool. Each call also writes a log line with the tool, person, workspace, calling application and outcome, with no arguments, results or tokens.

What OneShift stores and sends to AI is in theprivacy policy.