Support

Deploy the Outlook add-in

For: Microsoft 365 admins

Deploy the OneShift add-in to your organization, check that it works in your Outlook clients and find out why it is not working.

01

Before you start

The add-in inserts your workspace’s email signature in new messages, replies and forwards, and adds a Log time button to messages you read. A Microsoft 365 admin deploys it once for the organization; members do nothing.

What the add-in does is described in the Workspace guide, underEmail signature. This article covers getting it to your users.

You need:

  • A Microsoft 365 admin who can use Integrated apps in the Microsoft 365 admin center.
  • The workspace’s Microsoft 365 connector, set up for the same tenant as the mailboxes. OneShift matches the signed-in Outlook account to a member through the tenant and the email address, so without the connector in that tenant the add-in finds no member and inserts nothing. See Connect Microsoft 365.
  • A signature saved in the workspace under Branding, Signature. Without one there is nothing to insert.
  • Members whose OneShift email address matches their Outlook account. The add-in signs messages only when the From address is the member’s OneShift email.

Not verified in a customer tenant yet. The signature and Log time features have not been verified in a real Outlook tenant. If something behaves differently,contact OneShift.

02

Deploy from the admin center

You deploy through Integrated apps in the Microsoft 365 admin center, once for the whole organization or for the users and groups you choose.

  1. In the Microsoft 365 admin center go to Settings, thenIntegrated apps, then Get apps.
  2. Search for OneShift and select it.
  3. Assign it to the Entire organization or to specific users and groups.
  4. Review the permissions and accept them on behalf of the organization.
  5. Finish the deployment, then wait.
Allow for propagation. It can take several hours before the add-in appears in every mailbox.

The permissions are for the OneShift for Outlook app, which signs the add-in in to the OneShift API. It calls OneShift, not Microsoft Graph, so it has no Graph permissions and no application roles.

PermissionWhy
openid, profile, emailIdentity claims (tenant and email) that OneShift maps to a member.
offline_accessRefresh tokens, so the add-in can stay signed in.
access_as_userLets the add-in call the OneShift API for the signed-in person.

Individuals can also add the add-in from Outlook’s own add-in store if your organization allows it.

For the signature, deploy it as an admin. Outlook runs add-ins that act when a message is written only when an admin deploys them. Adding the add-in from the store yourself may not activate the signature.

03

Supported Outlook clients

The add-in runs in the Outlook clients below. Log time is on the ribbon of a message you read; it is not available on mobile.

Outlook clientNotes
Outlook on the webSignature and Log time.
New Outlook for WindowsSignature and Log time.
Classic Outlook for WindowsSignature and Log time, from build 2304.
Outlook for Mac (new UI)Signature and Log time, version 16.77 or later.
Outlook on iOS and AndroidSigning is declared there, but its sign-in is not verified on devices. Log time is not available on mobile.
04

Check that it works

The add-in has almost no screen of its own. A working install shows up in two places.

  1. Sign in to Outlook as a member and write a new message, a reply or a forward from their OneShift email address. The workspace signature appears in the body, filled in with their name, title and phone.
  2. Open a message you received. A Log time button in the OneShift group on the ribbon opens a pane with the customer, project and task suggested.

Wait for propagation first. If you change the From address to another account, the add-in removes the signature it inserted and leaves that account alone.

05

Updates

Updates reach your users without you doing anything.

  • New versions arrive from the marketplace automatically. If an update asks for new permissions, an admin approves them again.
  • Signature changes reach members within about an hour. The add-in keeps the last signature it received and asks OneShift again only when that copy is more than 60 minutes old.
06

Troubleshooting

If a member sees no signature or no Log time button, start with the cause that fits.

What you seeWhat to check
Nothing appears for anyonePropagation can take several hours. Then check the add-in is assigned to the user, and that the permissions were accepted on behalf of the organization.
No signature for one personThe From address must be their OneShift email address. The person must be an active member of a workspace whose Microsoft 365 connector is set up for this tenant. The workspace must have a main signature saved.
Signature only in some clientsCheck the client against the supported list: Mac needs version 16.77 or later and classic Windows build 2304 or later.
The signature is inserted twiceThe add-in is installed twice for the same mailbox, for example once by the person and once by your deployment. Remove one copy.
Log time says the account is not a OneShift memberThe pane answers this when the signed-in Outlook account maps to no member. Check the email address and the connector tenant as above.
Sign-in failsThe tenant may not have accepted the OneShift for Outlook permissions. Check the deployment in Integrated apps, or contact OneShift.

For a deeper look

In Outlook on the web, open the browser’s developer tools while you write a message. In the Network tab, autorun.html and autorun.js mean the add-in started. Then a request to the OneShift API at /outlook/signature answers with a code:

CodeMeaning
401Sign-in failed.
403The token does not carry the required scope.
404No matching member, or no signature saved.

In the Console, lines starting with OneShift: trace each step. Keep Preserve log on. The last line shows where it stopped. Send it to OneShift if you contact us.