Support
Linked Microsoft accounts
For: Members and external admins
Work inside a customer’s Microsoft 365? Link that account so the OneShift agent can also read it when it proposes your day. This page is for the member who links it and for the customer’s admin who approves it.
What linking does
A linked account is a second Microsoft 365 account, usually one a customer gave you in their own tenant. OneShift reads it in addition to your own workspace account.
- You do not need it for your own account. When your workspace admin has connected Microsoft 365, the agent already reads your account there. See Connect Microsoft 365. Link only accounts from other organizations.
- It is private. A link belongs to you and to the workspace you made it in. Your colleagues cannot see it, and a link made in one workspace is not used in another.
- It shapes the day review. The agent reads the linked account’s calendar, sent mail, Teams chats and channel posts. How that shows up in the agent’s messages is in the Agent guide.
Link an account
Linking takes a minute and happens in your own browser, signed in as the account you link.
- Open Account and find the Connected accounts section. Check that it names the workspace the customer’s work belongs to.
- On the Microsoft 365 row (“Calendar, sent mail, Teams chats and channel posts from another Microsoft 365 account.”), select Connect account.
- Microsoft opens and asks which account to use. Sign in with the customer account, not your own workspace account.
- Read the permissions and accept them (see the next section).
- You return to OneShift with “Account connected.” and the account appears in the list with a green Connected pill.
If the button is disabled, its hint says “Not available in this environment”.
If it does not work
| Message | Meaning |
|---|---|
| You cancelled the Microsoft sign-in. | You declined at Microsoft. Select Connect account again. |
| Your organisation’s administrator must approve OneShift Connect first. | The customer’s tenant does not let users consent on their own. Ask its admin to approve OneShift Connect; see the approval section. |
| Microsoft sign-in failed. | Any other failure at Microsoft. Try again; if it repeats, contact your workspace admin. |
An error appears in a message that begins “Could not connect the account.”, followed by one of the lines above.
What you and the other admin approve
Two things are consented to. You approve the first yourself; the customer’s admin approves the second once for the whole tenant.
Delegated permissions: you approve them as you link
OneShift Connect asks for these on the Microsoft sign-in screen. They let it read only what you can read.
| Permission | What it is for |
|---|---|
| User.Read | Identifies the linked account: its object id, sign-in name and tenant. |
| Calendars.Read | Reads calendar events of the linked account. |
| Mail.Read | Reads sent mail of the linked account. |
| Chat.Read | Reads the linked account’s Teams chats until the tenant’s admin approves the app roles. |
| offline_access | Lets OneShift refresh the sign-in so you do not sign in again every time. |
Application roles: the tenant’s admin approves them once
Channel posts, and complete coverage of chats, cannot be read with a user’s own permission. They need a tenant-wide approval by an administrator of the customer’s Microsoft 365. One approval covers every consultant who links an account in that tenant.
| Application role | What it is for |
|---|---|
| User.Read.All | Finds the member’s account in that tenant. |
| Chat.Read.All | Reads the Teams chats the member wrote. |
| Team.ReadBasic.All | Lists the teams the member belongs to. |
| ChannelMessage.Read.All | Reads the channel posts the member wrote. |
| Channel.ReadBasic.All | Reads channel names to title the activity. |
OneShift reads Teams only for the person who linked the account, matched by their own account id. It never writes anything.
Get the other tenant’s admin to approve
Until the customer’s admin approves, the agent reads your calendar and sent mail, and your Teams chats with your own permission, but no channel posts. To get the full read, send the admin an approval link.
Under the linked account, the line below the name tells you where it stands:
| Button | State |
|---|---|
| Get approval link | No approval has been requested. Chats are read with your own permission; channel posts are not read. |
| Copy link again | Waiting for the tenant admin to approve Teams chats and channel posts. |
| Re-request approval | Teams chats and channel posts approved by the tenant admin. The button stays available in case approval is later withdrawn. |
As the member
- Under the linked account select Get approval link. OneShift copies the link and says “Approval link copied. Send it to the tenant admin.” If your browser blocks the copy, it shows the link in a box titled “Copy this link”.
- Or select Email the admin. This opens a new email in your mail program with the subject “Please approve OneShift Connect for Teams access”, an explanation of what is read, and the link. No recipient is filled in; choose your admin.
- After the admin says they approved, select Check approval. OneShift asks Microsoft whether every role above is granted in that tenant.
| Check approval says | What to do |
|---|---|
| Teams chats and channel posts are approved in the tenant. | Done. The line says approved. |
| Approval incomplete. Missing: … | Some roles are not granted in the tenant. Ask the admin to approve again. |
| Approval check failed. … | Microsoft could not issue a token for the tenant, with Microsoft’s error code. Ask the admin to open the link again. |
As the customer’s admin
- Open the link from the member. Sign in with an account that can grant tenant-wide admin consent.
- Review the permissions OneShift Connect asks for, the five application roles above, and accept.
- You land on a OneShift page headed Approval recorded: “OneShift Connect can now read Teams chats and channel posts for the people in your organisation who linked their account.” You can close the tab. You do not need a OneShift account.
If you decline or the roles are not all granted, the page says Approval not completed and may add “The administrator did not grant access.” or “Microsoft admin consent failed.” Nothing is recorded as approved.
Reconnect and re-approve
A link can need attention later: your sign-in may stop being valid, or OneShift may start asking for a new permission. Approval can also be withdrawn in the customer’s tenant.
- Needs reconnect. The pill turns amber. Hover or focus it for the reason; for a new permission it reads “New permissions required: …”. The Connect accountbutton changes to Reconnect (“Reconnect: sign in again to refresh a linked account that needs attention.”). Select it and sign in again; the account’s sign-in is replaced in place and you do not lose the link.
- Approval no longer valid. If the customer’s admin removes OneShift Connect, or a role is missing after an update, the line reads “The tenant admin’s approval is no longer valid; ask for it again.” Use Get approval link or Email the admin again, then Check approval. The admin must also approve again whenever OneShift adds a role.
Until you reconnect, the agent skips that account. Your workspace account and other linked accounts keep working.
Disconnect an account
You can disconnect any account at any time from the same list.
- Under Connected accounts select Disconnect next to the account.
- Confirm “Disconnect this account?” (“The agent will stop reading it.”) with Disconnect. You see “Account disconnected.”
This removes your link and OneShift’s copy of your sign-in. It does not remove the customer tenant’s approval: that stays in the customer’s Microsoft Entra, for any other consultant who linked an account there. To withdraw it, the customer’s admin removes OneShift Connect from their tenant’s enterprise applications.
What is read
Reads are limited to you, to the day being reviewed, and to proposing time to you.
- Calendar events, sent mail. Read with your own delegated permission.
- Teams chats. Read with your own permission until the admin approves, and afterwards with the approved role, still only the messages you wrote.
- Channel posts. Only after the admin approves. They are not read with a member’s permission alone.
It does the same as for your workspace account: it proposes time entries to you, you confirm them, and the activity is held in memory for up to five minutes. In the day review, an unmatched line whose items all come from one linked account ends with the account’s address. The sign-in OneShift keeps for a linked account is stored encrypted. The privacy policy describes what is read and how it is used.