Your CRM, in the conversation.

Install

Add 4Degrees to Microsoft Teams.

The Microsoft Teams Store listing is coming soon. In the meantime, a Teams administrator installs 4Degrees manually with our app package (a one-time sideload), grants admin consent, and then each teammate links their own 4Degrees account on first use.

Step 1 — a Teams admin uploads the app package

1. Request the 4Degrees app package (a .zip Teams app bundle) from support@4degrees.ai. We'll send you the exact package we submitted to Microsoft, along with its SHA‑256 checksum so you can verify it (see below), while the Microsoft Store listing is in review.
2. Open Microsoft Teams → Apps (left rail) → Manage your apps → Upload an app → Upload an app to your org's app catalog. (This option is visible to Teams administrators with custom-app upload enabled.)
3. Select the .zip package. Teams validates it and adds 4Degrees to your organization's app catalog so anyone in the org can add it.

Verify the package is genuine

When you receive the .zip from 4Degrees, confirm it's the authentic, untampered app before uploading. The app identifiers below are baked into the package manifest — Teams shows them at upload time — and the checksum we send with the package lets you verify the exact bytes.

Publisher	4Degrees
App ID	5ca848f2-82fb-40ba-b553-f1a006b4d2aa
Bot ID	5ea66976-8be5-4ec7-8662-87a8170615a9

Run this against the file we sent — the output must match the SHA‑256 4Degrees provided alongside it:

# macOS / Linux
shasum -a 256 4degrees-teams.zip

# Windows (PowerShell)
Get-FileHash 4degrees-teams.zip -Algorithm SHA256

Step 2 — grant admin consent for your organization

1. Click Connect Teams. You'll be asked to sign in to 4Degrees if you aren't already.
2. Approve the Microsoft consent screen for your organization. 4Degrees requests only "Sign in and read user profile" — the minimum needed to identify who's talking to the bot.
3. You're done with the admin step. 4Degrees confirms your Microsoft tenant is connected and the bot can now reply for your organization.

Step 3 — teammates link their 4Degrees account

1. Open the 4Degrees app in Teams (or @mention it in a channel it's in) and send any message.
2. Tap the "Connect 4Degrees" card the bot replies with, sign in to 4Degrees, and approve the link. It takes about 30 seconds.
3. Done. The bot now answers questions and runs CRM actions on your behalf, with your permissions.

Troubleshooting

The most common install snags and how to fix them:

“Upload a custom app” is greyed out or missing

Custom-app upload is disabled for your org. A Teams admin enables it in the Teams admin center → Teams apps → Setup policies (Global or the relevant policy) by turning on “Upload custom apps.” Policy changes can take up to a few hours to propagate. This is a standard, reversible setting.

“Invalid Bot” when you click Add

Teams could not match the app's bot to a registered bot with the Teams channel enabled. This means you're using an outdated or altered app package — always upload the exact .zip from this page (verify its SHA‑256 above). Don't edit the manifest.json inside it.

Consent screen shows “AADSTS1003031” / “Misconfigured required resource access”

A transient Azure AD propagation issue after the app was first registered. Wait 2–3 minutes and click Connect Teams again. If it persists for more than ~15 minutes, contact support — the app registration's API permissions may need a refresh on our side.

“A Teams admin must approve the install” / consent was cancelled

The org-wide install (Step 2) requires a Teams / Azure AD administrator. If you're not an admin, ask one to complete the Connect Teams step once for your organization. After that, every teammate self-links (Step 3) with no admin involvement.

The bot replies with a “Connect your 4Degrees account” card every time

Your Microsoft identity isn't linked to a 4Degrees account yet. Tap Connect 4Degrees on the card, sign in, and approve the link (about 30 seconds). If you just linked and still see the card, send one more message — the first message after linking refreshes your session.

The bot doesn't reply at all

Your organization hasn't completed the admin install (Step 2) — until a Teams admin grants consent, the bot can't reply for anyone in your tenant. Confirm Step 2 was completed, then message the bot again.

The bot answers, but with fewer records than you expect

The bot respects your 4Degrees permissions — it returns only what your account can see in the web app (org-contact visibility, per-contact overrides, owner defaults). This is by design, not a bug.

Write actions

Act on what you find — safely.

Reads are always on. Writes are opt-in per surface and almost always undoable in one click. 4Degrees never performs destructive operations — no bulk deletes, no permission changes, no irreversible mutations.

1. Log interactions — capture a meeting, call, or note against a contact or deal from the chat you're already in.
2. Create & update — spin up a contact, company, or deal; move a deal stage; set a follow-up.
3. One-click undo — almost every write the bot makes comes back with an Undo button.

Security & privacy

Built for the firms that need it most.

Minimal permissions, per-seat identity, encryption in transit and at rest, and no model training on your data.

• Least-privilege Microsoft permissions — the app requests only "Sign in and read user profile". It does not read your mail, files, calendar, or chats.
• No standing credential for your tenant — the bot authenticates with 4Degrees' own single application identity; no secret, token, or credential specific to your tenant is created or stored.
• Your data is yours — never used to train models. See the privacy policy, terms of service, and DPA.