Microsoft Teams (Myca)

Access Myca (My Content Assistant) directly inside Microsoft Teams

The Masset Microsoft Teams integration grants access to Myca (My Content Assistant) directly inside Microsoft Teams. Myca is Masset’s personalized content assistant, giving Teams users a natural-language way to search, answer questions, analyze content usage, create shareable rooms, and manage supported Masset workflows without leaving Teams.

Myca runs as the Masset user associated with the Teams account making the request. That means the same Masset permissions, asset access controls, and workspace policies apply whether a user asks Myca from Teams, the Masset app, or another connected assistant surface.

Using Myca in Teams, you can:

  1. Get grounded answers to questions answered by your company’s approved content.
  2. Search and inspect assets using keyword search, semantic search, metadata lookup, extracted text, previews, and taxonomy context.
  3. Analyze asset activity such as views, downloads, shares, and top-performing content when the user has analytics permissions.
  4. Create and update content rooms that package assets or boards into shareable links, including CRM-linked rooms when available.
  5. Submit content requests for new assets or changes to existing assets.
  6. Manage training workflows such as discovering sessions, reading leaderboards and user stats, and creating or updating training content when the user has training permissions.

The tools Myca can use in Teams mirror the Masset toolset available through the MCP Server. Individual tool access depends on the mapped Masset user’s role, permissions, and Masset configuration. For a detailed tool reference, see the MCP Server tools page.

Teams features

Interacting with Myca in Microsoft Teams is done in the following ways:

  1. Personal conversations: Message the Masset app directly in Teams to have a one-on-one Myca conversation.
  2. Mention @Masset in team channels: Myca will respond in a team channel thread when the Masset app is directly mentioned.
  3. Threaded follow-ups: Follow-up mentions in the same Teams channel thread continue the same Myca conversation, so replies stay attached to the original discussion.
  4. Adaptive Cards: Supported Masset workflows can use Teams Adaptive Cards for interactive responses, feedback, or training interactions.
  5. Notifications and training delivery: When Teams delivery is configured for the user, Masset can send supported notifications and training messages in Teams.

Masset does not use the Teams integration for ambient channel monitoring. In channels, Myca responds to direct mentions of the Masset app.

Installation

Microsoft Teams setup has two independent customer-facing steps:

  1. A Microsoft tenant administrator grants Microsoft Entra admin consent for Masset’s application permissions.
  2. A Teams administrator installs or approves the Masset Teams app package in Microsoft Teams.

This is different from a Slack OAuth installation. Microsoft admin consent authorizes Masset to use Microsoft Graph application permissions in the customer’s tenant. Teams app installation adds the Masset bot/app to a personal, team, or supported chat scope. Masset does not receive or store a per-customer Teams bot token.

As someone that is both a Masset admin and a Microsoft tenant administrator:

1

Login to the Masset app

2

Go to the Admin section

3

Go to Integrations

4

Click 'Add Account'

5

Click the Teams icon

7

Upload or approve the Masset Teams app package

Use Teams admin center > Manage apps > Upload to add the Masset Teams app package shared by your Masset CSM, unless your tenant can install Masset directly from the Teams Store.

8

Verify the Teams app package

After the package is uploaded and approved in Teams admin center, Masset can verify that the expected Teams app package is visible in your tenant app catalog.

9

Install the Masset app in Teams

Install the Masset app for the required users or teams. When Teams reports the install event, Masset creates or updates the Teams integration for your company.

Manual manifest upload alone does not identify which Masset company owns the Microsoft tenant. The admin consent step ties the tenant to your Masset company, and the Teams install event creates the integration record Masset uses for conversations and delivery.

Admin management

After setup, Masset admins can manage the Teams integration from the Microsoft Teams integration details page.

The Teams overview shows:

  1. Integration status and Microsoft tenant ID
  2. User auto-association status
  3. Active install counts for personal, team, and group chat scopes
  4. Consent, verification, and sync timestamps
  5. App catalog status, detected app version, and expected app version
  6. Microsoft Graph and Teams permissions approved during admin consent

Admins can also:

  1. Sync now to refresh Teams user mapping data from Microsoft Graph.
  2. Disconnect the Teams integration when Teams delivery should stop.
  3. View installs reported by Teams, including scope, Teams target, status, installed time, and lifecycle events.
  4. Manage user mapping by auto-associating Teams users to Masset users with matching email addresses or manually assigning a Teams user to a Masset user.
  5. Send test messages to mapped Teams users to validate delivery.
  6. Review sync history including users seen, team installs attempted, team installs skipped, and sync status.

FAQ

What permissions does the integration require?

In order to provide the desired functionality, the Teams integration requires the following Microsoft Graph application permissions during admin consent.

PermissionDescription
AppCatalog.Read.AllRead the tenant Teams app catalog. Reason: Masset verifies that the expected Teams app package is visible in the customer tenant.
User.Read.AllRead user profile data. Reason: Masset syncs Teams users and maps them to Masset users.
Group.Read.AllRead group data. Reason: Masset resolves Teams and group context for installs and delivery.
Team.ReadBasic.AllRead basic team information. Reason: Masset identifies teams where the Masset app is installed.
TeamMember.Read.AllRead team membership information. Reason: Masset syncs team membership context for user mapping and delivery.
Channel.ReadBasic.AllRead basic channel information. Reason: Masset identifies channels where the app is installed or mentioned.
Chat.ReadBasic.AllRead basic chat information. Reason: Masset identifies supported chat scopes for app installation and delivery.
TeamsAppInstallation.ReadWriteSelfForUser.AllRead and install Masset’s own Teams app for users. Reason: This supports user-level app installation and proactive personal delivery when enabled.
TeamsAppInstallation.ReadWriteSelfForTeam.AllRead and install Masset’s own Teams app for teams. Reason: This supports team/channel app installation and channel mention delivery.
TeamsAppInstallation.ReadWriteSelfForChat.AllRead and install Masset’s own Teams app for chats. Reason: This supports supported chat-scope installation records and delivery.

What Masset data is shared with Teams?

When using the integration, the majority of Masset data never leaves the Masset system.

Myca may include Masset data in Teams messages when responding to a user-driven request. Depending on the request and the user’s Masset permissions, that can include:

  1. Asset names, descriptions, tags, metadata, and generated previews
  2. Excerpts, summaries, or answers grounded in approved asset content
  3. Asset activity or analytics summaries
  4. Content room names and public content room links
  5. Content request or training workflow status

The raw asset itself is never uploaded or shared to Teams directly. Links and downloads are routed through the Masset system to ensure that privacy and access controls are maintained. For example, a user may see a posted asset result in Teams, but will not be able to download it directly from Teams. Instead they will be routed to Masset where they will be required to log in to download the asset.

What Teams data does Masset have access to?

Masset only has access to data granted through Microsoft admin consent and Teams app installation.

When granted access, Masset has access to the following Teams data:

  1. Personal messages sent directly to the Masset app
  2. Team channel messages that directly mention the Masset app
  3. Follow-up messages in supported channel threads where the Masset app is mentioned
  4. Adaptive Card submissions for supported Masset workflows
  5. Teams app install, update, and remove lifecycle events
  6. Microsoft Graph user, team, channel, chat, membership, and app catalog metadata required for setup, mapping, and delivery

Masset does not use the Teams integration to monitor all channel traffic. In channels, Masset responds to direct mentions of the Masset app.

Why do Teams users need to be mapped to Masset users?

Teams messages are processed as the mapped Masset user. This ensures that every request uses the correct Masset identity, permissions, and asset access rules.

Masset can automatically associate synced Teams users to Masset users by matching email addresses. Admins can disable auto-association and manage mappings manually when needed.

If a Teams user is not mapped to an active Masset user, Masset will not process Myca requests or workflow submissions for that user.

Does the Teams integration use any sub-processors?

The Teams Integration does not currently use or require any additional sub-processors beyond the default set used by the Masset platform. We understand and respect the concerns that companies have about allowing third-party sub-processors access to your data.

If Masset introduces functionality requiring additional sub-processors, these features will be explicitly opt-in for all Masset customers to ensure that data is protected.

Does the Teams integration use my data for AI training?

No. The Masset for Teams Integration is meant to simplify the execution of Masset-related tasks by allowing them to be executed inside Teams. All LLMs used by Masset or its subprocessors are restricted to enterprise agreements restricting the use of data for training purposes.

Masset does not use Teams messages or data to train or fine tune any AI models.

Can I trust this?

We believe the answer to this question is a resounding yes. Masset has robust security practices to ensure the security, privacy, and trust of its customers.

Masset maintains a SOC 2 report and is periodically penetration tested by independent third parties. It also strictly adheres to cloud hosting best practices.

If you still have concerns, you are welcome to reach out to support@getmasset.com and they will get you in touch with a team member who can assist you.

Where can I submit feedback?

We love hearing from our customers and users. We strongly believe that we can only reach our goals through the feedback of people using our products. To reach out with feedback or bugs, simply send us an email at support@getmasset.com. If you prefer to have a live feedback session where you can talk to us on a call, we’d love to do that too.

If you wish to be notified of any updates to the Teams Integration, you can reach out to us at the same email and we’ll add you to our product update newsletter.