The Perceptyx App for Microsoft Teams notifies employees when their organization launches a new survey, when they are invited to take a 360 Assessment, or when new tasks or reports are posted to their Perceptyx account. For customers with an Activate license, employees can also chat directly with their personal AI coach in Teams.
The Perceptyx Teams App is used to:
Send survey invitations and reminders to employees.
Notify managers when they have been invited to take a 360 Assessment.
Inform employees when new reports, tasks, or insights are posted to their account.
Deliver Activate nudges and coaching conversations in real time.
This article walks through:
- Prerequisites
- Choosing Your Installation Path
- For End Users — Self Install
- For IT Administrators — Tenant-Wide & Group Deployment
- Sending Messages
- Troubleshooting
- Appendix A — Quick Reference
- Appendix B — Customer Onboarding Questionnaire
- Appendix C — Glossary
Prerequisites
Prior to app installation, Perceptyx must:
Create your company’s Teams account, associated with the company email domain
Enable the ability to send Teams notifications for your company’s self-led listening events
Important: If you try to install the app before the prerequisites are completed, you will receive an error and will need to install the app again after Perceptyx creates your company’s account.
Choosing Your Installation Path
There are three ways the Perceptyx app can land on a user’s Microsoft Teams client. Choose the one that fits your organization’s rollout plan. The rest of this document walks through each one in detail.
For End Users — Self Install
Any employee can install the Perceptyx app for themselves from the Microsoft Teams Store. This is the fastest path for pilots and individual users; for production rollouts your IT team will typically handle this for everyone (see “For IT Administrators”).
Step 1: Open the Perceptyx listing in the Microsoft Teams Store
Open the Perceptyx Teams listing in your browser, or search the Teams app store for “Perceptyx.”
Click Get it now on the listing.

If prompted, allow your browser to open Microsoft Teams.

Microsoft Teams will open and present the Perceptyx app card.

Step 2: Add the app inside Microsoft Teams
Click Add to install.
If your organization requires admin approval for new apps, follow the prompt to request access; once approved, repeat this step.
Step 3: Confirm installation
When the install completes, you will receive a “Welcome to Perceptyx for Teams” message. No further action is required. You will start to receive Perceptyx notifications when your organization launches surveys or when new tasks become available.

For IT Administrators — Tenant-Wide & Group Deployment
A Microsoft Teams Administrator can install the Perceptyx app for all employees, or for a specific group of employees (useful for phased rollouts and pilots). Microsoft has been on a rolling migration of admin UIs, so tenants today are on one of three paths. Choose the one that matches what you see in your Teams Admin Center:
Modern path — App-Centric Management. Each app has its own detail page with an Edit installs action under "Users and groups." Most tenants are on this UI today.
Legacy path — App Setup Policies. Installs and pins live as separate lists inside a Setup policy. Older tenants that have not yet migrated.
Newest path — Unified App Management. App management is consolidated across Teams, Outlook, and M365 Copilot, accessible from either Teams Admin Center or Microsoft 365 Admin Center. Tenants opt in via a banner shown at the top of the Manage apps page.
All three paths produce the same end result for the Perceptyx bot — a per-user personal-scope install — and all three are documented below. The conceptual model is identical regardless of UI: pinning makes the icon visible, installing makes the bot reachable, and both are typically needed.
Permissions Required
The Perceptyx Teams app uses the following permissions:
The Perceptyx app does not request elevated tenant-wide permissions and does not read message contents from other channels or chats. If your tenant requires admin consent before allowing custom apps, an admin will be prompted on first install or when reviewing pending requests in the Teams Admin Center.
Allowing the App in Your Tenant
Sign in to the Microsoft Teams Admin Center as a Teams Service Admin or Global Admin.
Navigate to Teams apps → Manage apps.
Search for “Perceptyx” and confirm the status is “Allowed”. If it is blocked, click the row, then click Allow in the top right.

Modern path — App-Centric Management
If your tenant has migrated to App-Centric Management, you will see an “Edit installs” action on each app’s detail page. This is the simplest way to install Perceptyx for all users or a subset.
In the Microsoft Teams Admin Center, navigate to Teams apps → Manage apps.
Search for “Perceptyx” and click the app name to open its detail page.
Click the Users and groups tab.
Click Install app (or Edit installs if some users already have it).

In the “Install app” dialog, choose one of the following:
All users in your organization — install Perceptyx tenant-wide.
Specific users or groups — select a security group, distribution list, or Microsoft 365 group (e.g. “Perceptyx Pilot”).
Click Apply.
Microsoft propagates the install to each user’s Teams client over the next 1–6 hours.

Legacy path — App Setup Policies
If your tenant has not yet migrated to App-Centric Management, you will configure installs through App setup policies. Historically, a setup policy had two distinct lists:
Installed apps — the apps that are added to a user’s Microsoft Teams account when the policy applies. This is what makes proactive notifications work.
Pinned apps — the apps that appear in the user’s Teams sidebar. Pinning alone does not install.
See the screenshot at the end of this section — the same banner is visible at the top of the policy editor view and points back to Manage apps for installs.
In the Microsoft Teams Admin Center, navigate to Teams apps → Setup policies.
Open the policy that targets the users you want to install Perceptyx for (typically “Global (Org-wide default)” for tenant-wide rollouts, or a custom policy for a pilot group).
Under “Installed apps”, click Add apps, search for “Perceptyx”, select it, and click Add. (Skip this step if the “Installed apps” section is no longer present — it has moved to Manage apps; install Perceptyx there using the Modern path above.)
Under “Pinned apps”, click Add apps, search for “Perceptyx”, select it, and click Add. Drag it to the position you want it pinned in the user’s sidebar.
Click Save at the bottom of the policy.

If the policy is not the Global default, also assign the policy to the right users / groups under “Group policy assignment” in the same Setup policies area.
Newest path — Unified App Management
Microsoft is rolling out Unified App Management as the next-generation admin experience. It consolidates app management across Microsoft Teams, Outlook, and Microsoft 365 Copilot into a single surface that is accessible from either Teams Admin Center or Microsoft 365 Admin Center. App and agent availability stays consistent across both portals.
You will know your tenant is eligible for unified app management when you see a banner at the top of the “Manage apps” page reading “Simplify how you manage apps and agents” with a “Move to unified app management” button on the right.

Before you migrate (one-time decision)
Sign in to the Microsoft Teams Admin Center as a Global Administrator and navigate to Teams apps → Manage apps.
Click the Learn about unifying app management link in the banner and review Microsoft’s notes.
When ready, click the Move to unified app management button in the banner.
A consent dialog titled “Introducing a new unified app management experience” appears.

Read the explanation, then tick the I have read the information and understand the effects of this change checkbox to enable the action button.
Click Move to unified app management inside the dialog to apply the migration.
Microsoft applies the migration. Most tenants land directly in the unified UI; some are routed through the org-wide settings alignment or review summary flows described above before reaching it.
If your tenant lands in the org-wide settings alignment branch (described in the warning above), you will see a screen like the one below before the migration finalizes — Microsoft asks you to reconcile differences between your Teams and Microsoft 365 app settings.

Installing Perceptyx in Unified App Management
Once your tenant is on Unified App Management, the install steps for the Perceptyx app are functionally the same as the Modern (App-Centric Management) path above — find the app, open its detail page, choose who to install for, apply. The two practical differences are:
You can do the install from either Teams Admin Center OR the Microsoft 365 Admin Center (admin.microsoft.com → Settings → Integrated apps). Changes propagate to both portals.
The same install applies to Teams and any other Microsoft 365 surface the app supports. (Today the Perceptyx app is Teams-only, so this is forward-looking; once we ship Outlook or Copilot integrations the unified install will reach those automatically.)
Open Manage apps from either Teams Admin Center or Microsoft 365 Admin Center.
Search for “Perceptyx” and click the app name to open its detail page.
On the “Users and groups” (or equivalent) tab, click Install app / Edit installs.
Choose All users in your organization or Specific users or groups.
Click Apply.
Microsoft propagates the install over the next 1–6 hours, just as in the other paths.
Verification (next section) is identical to the other two paths: confirm the test user receives the “Welcome to Perceptyx for Teams” card.
Verifying the Rollout
Microsoft propagates installs and policy assignments asynchronously. It can take anywhere from ~15 minutes to a few hours. To verify:
Wait at least 30 minutes after saving the policy.
Pick a test user, sign in to their Microsoft Teams client (web or desktop), and look for the Perceptyx app in their Teams sidebar.
Click the Perceptyx icon. They should see the “Welcome to Perceptyx for Teams” card automatically.
If they do not see the welcome card within an hour, see the Troubleshooting section.
(Optional, admin-only) For definitive confirmation of a specific user’s install state — particularly when a single user reports a problem — see “Confirming an install via Microsoft Graph” below.
Confirming an install via Microsoft Graph
For a definitive answer on whether a specific user’s Teams client has the Perceptyx app installed in personal scope, Microsoft Graph is the source of truth. This is the same diagnostic the Perceptyx Engineering team runs internally when investigating escalations — surfacing it here lets your IT team verify state without filing a support ticket.
To check a single user:
Open Microsoft Graph Explorer at https://developer.microsoft.com/en-us/graph/graph-explorer.
Sign in (top-right corner) as a tenant administrator with Teams admin permissions. If you see the orange banner “You are currently using a sample account,” that means you have not signed in yet.
Find the affected user’s Entra Object ID: Entra Admin Center → Users → search for the user → copy the Object ID value (an immutable GUID like 00000000-0000-0000-0000-000000000000).
Paste this URL into the Graph Explorer query bar (replacing {user-object-id} with the GUID from the previous step) and make sure the HTTP verb dropdown is set to GET:
Click Run query.
Read the JSON response. The “value” array lists every Teams app installed in that user’s personal scope. The single field that matters for diagnosis is teamsAppDefinition.displayName — look for "Perceptyx."
Troubleshooting Graph Explorer
If the query does not return the expected response, the most common causes and fixes:
“You are currently using a sample account. Sign in to access your own data.”
Graph Explorer opens in sample-account mode by default. Click the sign-in button in the top-right corner and authenticate with your tenant admin account. The orange banner should disappear and you should see your own avatar in the top-right.
HTTP 403 / “Forbidden — Insufficient privileges to complete the operation” or “permission TeamsAppInstallation.ReadForUser.All required.”
Your admin account is signed in but Graph Explorer has not yet been granted the specific permission needed to read another user’s installed apps:
In the response pane (below the query bar), click the Modify permissions tab.
In the list, find TeamsAppInstallation.ReadForUser.All. If your organization requires admin consent for new permissions, you may see a Consent button or a Request admin consent link.
Click Consent and complete the Microsoft prompt that pops up. If your admin account does not have permission to grant tenant-wide consent, ask a Global Administrator to do this step once for your tenant — it is a one-time setup.
Re-run the query.
HTTP 404 / “Resource not found.”
The most likely cause is a typo in the Object ID. Double-check the GUID in Entra Admin Center → Users → the user → Object ID. Object IDs are case-insensitive but must match the GUID exactly with no extra spaces.
Empty value: [] array (request succeeded but returned no apps).
The user has no Teams apps installed at all, which is itself a finding (it means even Microsoft’s built-in default apps did not propagate to this user, suggesting a broader account issue). Worth raising with Microsoft support.
Sending Messages
Once the Perceptyx app is installed for your users, your Perceptyx Program Manager can enable Teams notifications on a per-survey basis.
Self-Led Surveys
When scheduling a self-led survey invitation or reminder, check the Include Chat Notification checkbox. Teams notifications are sent at the same time as the email reminders.

Managed Surveys and 360 Assessments
For managed surveys and 360 Assessments, ask your Perceptyx Program Manager to enable Teams notifications. They will configure the “Allow bot survey invitations” survey setting on your behalf.
Activate Nudges and AI coaching
Customers with an Activate license get nudges and AI coaching conversations delivered through the same Teams app — no additional configuration needed beyond installing the app. Users type “Hi,” “Hello,” or “Help” in the bot chat to start a conversation with their personal AI coach.
Troubleshooting
“You cannot send messages to this bot”
This is the most common issue with admin-deployed installs. The user sees the Perceptyx icon in their Teams sidebar, but when they click it the message composer is greyed out with the text “You cannot send messages to this bot.”
What it means
The Perceptyx app is pinned to the user’s Teams client (so they see the icon) but not actually installed in their personal scope (so the bot cannot send or receive messages). This is a Microsoft-side state, not a Perceptyx outage. Survey invitations and AI coaching messages cannot be delivered to users in this state.
How to fix (admin action required)
A Microsoft Teams Administrator at your organization needs to add Perceptyx to the Installed apps list (in addition to Pinned apps), or use the modern “Edit installs” flow:
Modern path (App-Centric Management): Teams Admin Center → Manage apps → Perceptyx → Users and groups → Install app → select all users (or affected group).
Legacy path (App Setup Policies): Teams Admin Center → Setup policies → the affected policy → Installed apps section → Add apps → Perceptyx → Save.
Newest path (Unified App Management): Either Teams Admin Center → Manage apps → Perceptyx → Users and groups → Install app, OR Microsoft 365 Admin Center → Settings → Integrated apps → Perceptyx → Edit installs.
After saving, Microsoft needs 1–6 hours to propagate. Once propagated, affected users will automatically receive the welcome card on their next Teams client refresh, and notifications will resume.
Microsoft’s own documentation:
• Send proactive messages — explains the personal-scope install requirement
• Preinstall Teams apps for your organization
“Some employees get notifications, others do not”
A common pattern is that long-tenured employees receive Perceptyx notifications fine, but newer employees or specific departments do not. This usually means the company’s Setup policy installs Perceptyx only for the original cohort (when the policy was first applied) or via Pinned apps only — newer employees never trigger a real personal-scope install.
Apply the same fix as the previous section: ensure Perceptyx is in the Installed apps list (or use Edit installs in the modern UI) and assign the policy to all relevant users.
“Thanks for your interest in the Perceptyx Microsoft Teams application!”

This message means the Perceptyx system was not yet able to associate the user’s Microsoft Teams account with their employee record in Perceptyx. This typically happens when the Teams app is installed before Perceptyx has finished configuring the account for your organization.
Contact your Perceptyx Program Manager or Customer Success Manager and provide the email address of the affected employee. Once configuration is complete on our side, the user will automatically receive the standard “Welcome to Perceptyx for Teams” message and future notifications will arrive normally.
“I do not see the Perceptyx app at all in Teams”
If a user cannot find the Perceptyx app in their Teams client — not pinned in the sidebar, not in Apps → Search — there are four things to check, in order:
Has the user signed out and back in to Teams since the policy was applied? Microsoft does not always push policy changes to a running Teams client; sign-out + sign-in forces a refresh.
Is the user assigned to a Teams app permission policy that blocks custom apps? In Teams Admin Center → Permission policies, confirm “Custom apps” is allowed for their assigned policy.
Has the policy itself been applied to the user? In Teams Admin Center → Users → the affected user → Policies, confirm the App setup policy column shows the policy that includes Perceptyx.
(Definitive check) Confirm the install state directly via Microsoft Graph. See “Confirming an install via Microsoft Graph” in the Verifying the Rollout section. The presence or absence of Perceptyx in the user’s installedApps response is the authoritative signal — it tells you exactly whether the personal-scope install completed, regardless of what the Teams Admin Center policy view shows.
Where to get help
For installation questions, contact your Perceptyx Program Manager or Customer Success Manager. For escalations or technical issues that involve message delivery, the Perceptyx Engineering team can investigate the bot side; please include the affected user’s email address and the approximate time the issue was observed in your support ticket.
Appendix A — Quick Reference
Decision tree for IT admins
Appendix B — Customer Onboarding Questionnaire
Use this questionnaire when planning a Perceptyx Teams app rollout with a new customer. Walk through it on the kickoff call, or send it to the customer’s IT contact ahead of time. Each answer maps to a specific path in this document, so the rollout plan falls out of the responses.
1. Rollout scope
Who at your organization should receive Perceptyx Teams notifications?
☐ All employees in the tenant
☐ A specific group only (provide group name): _____________________________________
☐ Phased: pilot group first, then expand. Pilot group: _____________________________
☐ Self-install (employees opt in individually from the Microsoft Teams Store)
2. Installation method
How will the app reach end users?
☐ Admin push (recommended) — IT installs for users via Teams Admin Center
☐ Self-install — employees install themselves from the Teams Store
☐ Mix — admin push for some, self-install for others
☐ Unsure — we will schedule a follow-up with the IT team
3. Sidebar pinning
Should the Perceptyx icon be pinned to users’ Teams sidebars?
☐ Yes — pin for discoverability (recommended in addition to Install)
☐ No — install only; users will receive notifications without seeing the icon
4. Tenant management UI
Which admin UI does the customer’s tenant use? (Microsoft is migrating tenants over time; the customer’s IT admin can confirm by signing in to the Teams Admin Center.)
☐ App-Centric Management (modern: Teams Admin Center → Manage apps → Edit installs). Most tenants today.
☐ App Setup Policies (legacy: Teams Admin Center → Setup policies → Installed apps + Pinned apps). Older tenants.
☐ Unified App Management (newest: managed from Teams Admin Center OR Microsoft 365 Admin Center; cross-product). Tenants that have clicked the "Move to unified app management" banner.
☐ Unsure — IT will check before the policy change
5. License and feature scope
Which Perceptyx features will users have access to?
☐ Surveys and reports only
☐ Activate nudges
☐ Activate AI coaching
6. Admin consent for custom apps
Does the customer’s tenant require admin consent before allowing custom apps?
☐ Yes — IT will pre-approve Perceptyx in Teams Admin Center → Manage apps
☐ No — Perceptyx is already on the allow list / no consent needed
☐ Unsure — IT will check
7. Email domain registration
List every email domain Perceptyx should associate with this customer’s Teams installation. This is required for our backend to associate Microsoft Teams accounts with employee records in Perceptyx (without it, users will see the “Thanks for your interest” error message).
Domains (one per line, e.g. acme.com, acme.co.uk):
_____________________________________________________________________
_____________________________________________________________________
_____________________________________________________________________
8. Microsoft 365 tenant ID
Customer’s Microsoft 365 tenant ID. Find at https://admin.microsoft.com → Settings → Org settings → Organization profile, or via PowerShell: Connect-MgGraph; Get-MgOrganization | Select Id.
Tenant ID: _____________________________________________________________
9. Existing installations
Has anyone at the customer organization already installed the Perceptyx Teams app?
☐ No — fresh deployment
☐ Yes — some users have installed it organically. IT can verify the count in Teams Admin Center → Manage apps → Perceptyx → Users and groups → "Installed for: <count>".
☐ Unsure
10. Timeline and contacts
Target go-live date: ____________________________________________________
Primary IT / Teams admin contact (name, email): __________________________
Primary Perceptyx CSM contact (name, email): _____________________________
Appendix C — Glossary
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article






