Support

Roll out the Teams agent

For: Microsoft 365 admins

Get the OneShift app into your Microsoft 365 organization, let OneShift install it for members who need a message, and check what to do when a reminder does not arrive.

01

Before you start

The agent is a Teams app that people use in a one-to-one chat. You add it to your organization once, and each person signs in to OneShift the first time they use it.

You need:

  • A OneShift workspace with at least one person who can sign in.
  • The workspace connected to your Microsoft 365 tenant. The connector reads each person’s day for suggestions and sends the agent’s messages. Set it up first inConnect Microsoft 365.
  • Access to the Teams admin center for your organization.

What the app declares

These values come from the app’s manifest, so you can check them against what you see in the store.

ItemValue
NameOneShift (full name OneShift Agent)
PublisherNavtech Group Ltd.
Where it worksPersonal scope only: a one-to-one chat with the agent. It is not added to teams, channels or group chats. The same app also has the copilot scope, see Copilot and AI tools.
Permissionsidentity, messageTeamMembers
Valid domaintoken.botframework.com, used for the sign-in
Privacy and termsoneshift.ai/agents/privacy and oneshift.ai/agents/terms
02

Get the app from the Teams store

OneShift is published in the Teams app store. Anyone your organization allows can add it themselves.

  1. In Teams, open Apps.
  2. Search for OneShift. Check the publisher is Navtech Group Ltd.
  3. Select Add.

The agent opens a one-to-one chat and asks the person to sign in. If Teams says the app is blocked or not available, your administrator needs to allow it, as described next.

03

Allow the app in your organization

If your organization restricts third-party apps, allow OneShift in the Teams admin center before people look for it.

  1. Sign in to the Teams admin center as an administrator who can manage apps.
  2. Open Manage apps and find OneShift.
  3. Allow the app for your organization.

Admin center menus are Microsoft’s. OneShift does not document them because Microsoft changes their names and layout. Use Microsoft’s own Teams admin center help for the exact clicks. If the app does not behave as this article describes,contact OneShift.

04

Make it available, pin or pre-install

Teams policies decide who may use an app and whether it appears in the app bar. Check them for the people who will use OneShift.

  • App permission policy. Make sure OneShift is allowed for these people. A policy that blocks the app also blocks the automatic install in the next section.
  • App setup policy. Optional. Use it to install and pin OneShift for a group so people find it without searching. It is not required: OneShift can install the app for a person when it has a message for them.
05

Automatic install for members

The agent writes to people first: a start-of-day message, the end-of-day review, project checklist reminders, and a notice when a timesheet is rejected or resubmitted. For that it needs a one-to-one chat with each person, and the workspace’s Microsoft 365 connector can set one up.

When OneShift has a message for a member, the connector does this in your tenant:

  1. Finds the person in Microsoft Entra ID by their email address.
  2. Finds the OneShift app in your Teams app catalog.
  3. Installs the app for that person if it is not installed yet.
  4. Finds the person’s chat with the agent, or creates it when there is none.
  5. Sends the message.

This relies on three application permissions that you grant the connector with admin consent. The full list is in Connect Microsoft 365.

PermissionWhat OneShift uses it for
AppCatalog.Read.AllFind the OneShift app in your tenant’s app catalog.
TeamsAppInstallation.ReadWriteForUser.AllFind or install the app for a member, and read the member’s chat with it.
Chat.CreateCreate the one-to-one chat with the agent when none exists.

Resolving the person from their email also needs User.Read.All. Without these permissions OneShift cannot start a conversation with a member.

06

Each person’s first sign-in

Nobody can use the agent before signing in to OneShift. Each person does this once, in the chat.

  1. The person opens the chat with the agent, or receives its first message. It shows a card asking them to sign in.
  2. They tap Sign in and use their OneShift account.
  3. They pick the workspace while signing in. The agent works in that workspace until they sign out.

The sign-in cards and what the agent says are in the Agent guide, underSigning in.

Daily messages need a sign-in too. If a person has not signed in, or their sign-in expired, the start-of-day, end-of-day and checklist messages are replaced by a short prompt with a Sign in button. Notices that a timesheet was rejected or resubmitted are not held back.
07

When messages do not arrive

If someone does not get the agent’s messages, work down this list. The first rows affect everybody, the later ones a single person.

What you seeWhat to check
Nobody gets messagesThe workspace is not connected to Microsoft 365, or admin consent for the connector’s permissions is missing. Check the connector in Connect Microsoft 365, including the three Teams permissions above.
OneShift cannot find the app in your tenantThe app is blocked in the Teams admin center or not available to your organization. Allow OneShift in Manage apps, as described above.
One person gets nothingTheir email address in OneShift must match their Microsoft Entra ID account, because the person is looked up by email. Also check that your policies allow the app for them, and that the app can be installed for them.
A sign-in prompt instead of the usual messageThe person is signed out or their sign-in expired. They tap Sign in in the chat.
Someone who was signed in gets a sign-in promptAfter the agent restarts it finds a person’s Teams id from the chat roster. If the roster does not return their email, they get a sign-in prompt instead of the message. Signing in again fixes it.
Messages arrive at the wrong timeThe times for start and end of the day are set in the workspace, not in Teams.

Not verified in a customer tenant yet. Messages sent to signed-in users have not been exercised in a real tenant yet. If a step behaves differently in yours, contact OneShift.