Account and billing
Microsoft permissions and data access
The exact Graph permissions Twintual requests for email, chat and calendar, what each one does, and how your admin can restrict or review them.
Twintual connects to Outlook, Teams and Microsoft 365 Calendar the same way any Microsoft sign-in works. Each person signs in once, approves the access Twintual asks for, and Twintual then acts only for that one person. This article lists the exact Microsoft Graph permissions Twintual uses, what each one does, and how an administrator can review or restrict them.
What kind of access does Twintual request?#
Every Microsoft connection Twintual makes is delegated and per user. Delegated means the permission only works while acting as the signed-in person, scoped to their own mailbox, calendar or chats. Twintual never requests Application permissions, the kind that work tenant-wide with no signed-in user and no multi-factor check.
A Microsoft administrator can confirm this directly in Microsoft Entra. Every permission on Twintual's app registration's API permissions page shows Delegated in the Type column, never Application.
Because access is always tied to one person's own sign-in, restricting which people may connect Twintual also restricts which mailboxes it can ever reach. There is nothing further to scope per mailbox, since Twintual never holds a tenant-wide credential that could reach one in the first place.
Which permissions does Twintual use, and what does each one do?#
Twintual asks for only the Microsoft Graph permissions each feature needs, and nothing it does not use.
- Mail (Twintual Outlook Bridge):
Mail.Readreads your mail so Twintual can show it, summarize it and search it.Mail.Sendsends the replies you approve.Mail.ReadWritelets Twintual mirror actions back to Outlook, such as archiving or deleting a message you handled in Twintual. - Calendar (same registration as Mail):
Calendars.Readreads your events for your daily brief and meeting prep.Calendars.ReadWritecreates or updates events Twintual schedules on your behalf. - Sign-in and session:
User.Readreads your basic profile, name and email, to identify you.offline_accesskeeps you signed in without asking you to sign in again every time. - Contacts, optional:
Contacts.Readis requested only if you turn on contact import. Twintual uses it to build your address book from the people you already email. - Teams (Twintual Teams Bridge, a separate registration):
Chat.Readreads your chats.ChatMessage.Sendsends the chat replies you approve.Chat.Createstarts a new chat you ask for.Files.ReadWriteopens a file someone shared with you in a chat. - Teams directory import, optional:
User.ReadBasic.Allis requested only if you turn on importing names from your organization's directory, so Twintual can show real names instead of email addresses. - Meeting transcripts, optional:
OnlineMeetings.ReadandOnlineMeetingTranscript.Read.Allare requested only if you turn on importing Teams meeting transcripts tied to your calendar.
Why do some permissions ask for administrator approval?#
A small number of permissions above, User.ReadBasic.All and the meeting-transcript pair, are classified by Microsoft itself as needing a tenant administrator's approval, regardless of which app requests them. They stay off by default. Twintual only asks for them the moment you turn on the feature that needs them. It never asks for them as part of signing in, or connecting Mail, Calendar or basic Teams chat.
Twintual never calls Microsoft's organization-wide admin-consent flow as part of a normal connection. That flow only appears as a fallback link. It shows up only when an organization has blocked individual consent entirely, so a person can forward the request to their own IT admin instead of being stuck. It is never the default path, and it is never used to request Application permissions.
How can an administrator restrict or review this access?#
In Microsoft Entra, under Enterprise applications, your administrator can find Twintual's app registrations (named Twintual Outlook Bridge and Twintual Teams Bridge) and:
- Open Permissions to see the exact list above, confirmed as Delegated.
- Use User consent settings to require administrator approval before any user in the organization can connect Twintual at all, or to allow only specific permission classifications.
- Use a Conditional Access policy to limit which users or groups may sign in to Twintual's connection at all.
- Revoke anything your organization consented to in the past that no longer appears on that list. Removing a permission from Twintual's own registration does not erase a consent your organization already granted; your admin clears that from the same Permissions page.
Restricting sign-in this way is the effective equivalent of restricting Twintual to specific mailboxes. Every connection is tied to one person's own sign-in, so a person who cannot sign in cannot be reached at all.
How does Twintual protect the credential behind these app registrations?#
The app registration itself, not your personal account, proves its own identity to Microsoft with a certificate, not a shared password. Twintual holds the private half of that certificate in its own secret store; Microsoft holds only the public half, uploaded to the app registration.
Twintual rotates this certificate on a yearly schedule, and immediately if an incident ever calls for it. The old and new certificate overlap briefly, so a rotation never interrupts a live connection.
Next steps#
- Connect your channels to see how you approve access the first time.
- Privacy basics for what Twintual reads and keeps private.
Need help?#
Select Help in the corner of any screen, then Contact support. For a question specific to your organization's security review, ask your workspace admin to contact Twintual support directly with the details.