- What connecting enables
- Tasks that read or act on your Instagram account the kind of work that otherwise means opening the app and doing it by hand.
- Governed by
- Meta, under the terms already covering your Instagram account. No company boundary is crossed, because the data was already inside Meta.
- Revoked in
- Your Instagram account settings, not in Muse and not on your Mac.
Account-level · authorised separately · revoked elsewhere
A standing connection, not a permission.
Granting Muse a folder on your Mac is bounded and reversible from inside the app. Connecting an account is neither. It creates a link to something that lives somewhere else, governed by that service’s rules, which survives you deleting the app and has to be switched off where it was switched on.
If you only read one bit
Granted individually, revoked somewhere else
The short version
Four accounts, two kinds, one trap
Muse connects to Instagram, Facebook and WhatsApp Meta’s own services plus Google Workspace, which is external. Each is authorised on its own and none is required to use the agent on your Mac. The trap is revocation: an integration lives in the account that granted it, so removing Muse from your Mac leaves it connected. Integrations also roll out region by region on top of Muse’s own availability.
Authorise one at a time
None is required
Revoke in the account
Uninstalling does not revoke
This page covers connections to accounts elsewhere. For the areas Muse works in on your Mac files, mail, calendar, notes, forms see what it can reach and the three permission layers.
Supported accounts
The four connections, and who governs each
Three sit inside Meta’s own perimeter. One does not, and that difference matters more than any feature comparison between them.
- What connecting enables
- The same shape of thing for your Facebook account, including any pages or business identity attached to it worth noticing if yours is not purely personal.
- Governed by
- Meta. The consideration here is scope rather than boundary: one account can carry several identities.
- Revoked in
- Facebook’s own settings, under connected apps.
- What connecting enables
- Reaching your messages for tasks that need them. Muse on WhatsApp covers this one in its own right.
- Governed by
- Meta but this is the connection most worth pausing over, because a messaging history is the most personal thing on the list by some distance.
- Revoked in
- WhatsApp’s own settings.
Google Workspace
External service- What connecting enables
- Tasks reaching your Workspace documents, mail and calendar the most useful connection here for work, and the most consequential.
- Governed by
- Google’s terms and Meta’s. This connection crosses a company boundary, and Meta’s stated position is that it draws on information from accounts you connect. What that means.
- Revoked in
- Your Google account’s third-party access settings and on a work account, your administrator may control whether it can be granted at all. See below.
These are the connections established as of September 2026. Integrations expand and roll out per region, so treat this as a snapshot and Meta’s own list as authoritative and note that the agent can be present where a given connection is not yet enabled. How regional rollout works.
The distinction that matters
An integration is not a bigger permission
People treat the two as points on one scale grant a folder, grant more folders, grant an account and they are not on one scale at all.
A Mac area is bounded by your machine. Meta and Apple both sit between it and your data, you can see what is in it, and you switch it off in Muse or in System Settings. It ends when you say so.
An integration is a standing authorisation held by another service. It persists after the task, after you close the app, and after you drag the app to the bin. It is governed by that service’s terms as well as Meta’s, and on a work account it may not be yours to grant in the first place.
You do not revoke an integration by uninstalling Muse, any more than you cancel a subscription by deleting the app you bought it in.
Which leads to the only rule on this page worth memorising: connect when a task needs it, not when setup offers it. Setup screens present every available connection at the moment you are least equipped to judge them before you have run a single task and discovered which ones you actually use. An unconnected account is the only kind that cannot be reached, and reconnecting later costs about forty seconds.
The same asymmetry explains why the task examples on this site lean on Mac areas rather than integrations. Most everyday agent work filing, extracting, checking never needs an account connection at all.
Setup
Connecting one properly, in six steps
The steps themselves take a minute. The order is what keeps you from connecting four accounts you never use.
Wait until a task needs it
Run Muse on Mac areas alone for a week or two first. Most everyday agent work never touches an account connection, and you will know which one you actually want.
Check it is available where you are
Integrations roll out per service and per region on top of Muse’s own rollout. A connection that is absent is usually not enabled yet rather than broken. Regional gates.
Know which account you are connecting
Especially for Facebook and Google, where one login can carry a personal identity and a work one. Check which is active before you authorise, not after.
Read the authorisation screen properly
It is the one place the actual scope is stated, and it is shown by the service rather than by Meta. If it asks for more than the task needs, that is worth a pause.
Run the task and see what it actually used
Read the plan before the run. If the connection turns out to be unnecessary, revoke it the same day an unused authorisation is pure standing exposure.
Write down where you granted it
Sounds trivial; it is the difference between revoking in thirty seconds and not finding it at all in six months. Note the service and the settings page.
Revoking: three places, not one
To be genuinely disconnected you have to check Muse’s own settings, macOS System Settings under Privacy & Security, and each connected account’s own connected-apps page. That last one is per account, so three integrations means three separate visits and it is the one uninstalling the app cannot do for you.
If the lists disagree, the account’s own list is the one that governs access. The three permission layers in full · Removing the app cleanly.
Work and managed accounts
When the decision is not yours
The Google Workspace connection is the one most people want and the one most likely to be out of their hands.
A Workspace account issued by an employer or a school is administered. Whether third-party applications may connect to it at all is a setting held by whoever runs that domain, and it is frequently set to deny by default not as a judgement about Meta, but as the ordinary posture for any external application.
The practical consequence is that the connection may simply refuse, or never appear as an option. That is policy, not a fault, and it is the kind of thing people spend an afternoon reinstalling an app over. If you are on a managed account and the connection will not go through, the next step is a conversation with whoever administers it, not troubleshooting.
A connection that works today can also stop working tomorrow, because the administrator changed a policy rather than because anything on your Mac changed.
There is a second consideration that has nothing to do with whether it works. Connecting a work account routes work data through a connection you authorised personally, which may sit awkwardly with obligations your employer has to clients or to a regulator. That is not a privacy question about Meta specifically it would apply to any agent but it is a question worth asking before connecting rather than after.
If in doubt, the conservative route is available and costs little: use Muse on your personal machine areas, keep work data in the tools your employer sanctions, and leave the Workspace connection unmade.
FAQ
Integration questions
Which accounts does Muse connect to?
The connections established so far are Instagram, Facebook and WhatsApp all Meta’s own services plus Google Workspace, which is external. Each is authorised individually, and the list changes as integrations roll out, so Meta’s own is authoritative. The four.
Is an integration the same as granting a Mac area?
No, and conflating them is the commonest mistake. A Mac area grant is bounded by your machine and revoked in Muse or macOS. An integration is a standing connection to an account elsewhere, governed by that service’s terms and revoked in its own settings. The difference.
Does uninstalling Muse revoke my integrations?
No this is the trap. An integration you authorised lives in the account that granted it, not on your Mac, and deleting the app has no effect on it. Revoke it in that account’s connected-apps settings. Removing cleanly.
What is the difference between a Meta service and an external one?
Connecting Instagram, Facebook or WhatsApp gives Muse reach into data already inside Meta’s perimeter. Connecting Google Workspace moves data across a company boundary, is governed by Google’s terms as well as Meta’s, and may be controlled by your employer rather than by you.
Can my employer block the Google Workspace connection?
Yes. On a managed Workspace account, third-party app access is an administrator setting. If the connection refuses or never appears, that is policy rather than a fault, and no amount of reinstalling changes it. Managed accounts.
Do integrations work everywhere Muse does?
Not necessarily. Integrations roll out per service and per region on top of Muse’s own availability, so the agent can be present while a particular connection is not yet enabled where you are. Regional gates.
Should I connect everything during setup?
No. Connect one when a task genuinely needs it. An unconnected account is the only kind that cannot be reached, and setup screens are designed to make connecting everything feel like the default. The six steps.
Does connecting an account affect what Meta trains on?
Meta’s stated position is that it draws on information from outside Meta, including accounts you connect such as Google Workspace. That makes connecting a decision about model training as well as convenience, so read Meta’s current terms first. How we treat Meta’s claims.
How do I check what is currently connected?
Check in two places, because they can disagree: inside Muse, and in each account’s own connected-apps or security settings. The account’s list is the one that actually governs access.
What if an integration stops working?
Check whether the authorisation is still present in that account’s settings before troubleshooting the app. Authorisations can be ended by a password change, an administrator or the service itself, none of which is a Muse fault. The triage ladder.
Connect when a task needs it
Not because the setup screen offered.
Most everyday agent work never touches an account connection at all and an unconnected account is the only kind that cannot be reached.
Independent guide not affiliated with Meta. Supported connections are described as of September 2026 and expand over time; statements about what Meta draws on are Meta’s own, and Google Workspace behaviour depends on your account’s administrator.