Skip to main content

Meta integration permissions: what we request and why

Which Meta permissions Cuttable requests, what it enables, and what Cuttable does not access.

Written by Libby

Summary
When you connect Meta to Cuttable, Meta asks you to grant a set of permissions, and to some people that list can look broader than expected. This article explains what Cuttable actually does with the connection, what each permission is for, and just as importantly what Cuttable does not access. The short version: we only use your Meta connection to publish your ads, report on their performance, and improve the ads we generate for you. We do not read your Instagram or Facebook messages.


The short version

Cuttable uses your Meta connection for three things:

  • Publishing ads → creating the creative you make in Cuttable as ads, ad sets and campaigns in your own Meta ad account.

  • Reporting → reading performance data so you can see how your ads are doing in the Insights tab and decide what to make next.

  • Improving your ads → using performance signals from your ads to make Cuttable's AI better at generating creative that works for you. The more signal we have on what's performing, the stronger the ads we generate become.

Everything we ask for maps back to one of those three jobs. We never message your audience, post on your behalf without you publishing it, or read private inboxes.


How the connection works

Cuttable connects using Facebook Login for Business. This links Cuttable to the business assets you choose (your Business Manager, ad account, the Pages your ads run under, and any linked Instagram account), not to your personal Facebook profile. You choose which Business Manager and ad account to connect, and Meta shows you the exact permissions being requested before you approve them.


The permissions we request, and what each is for

Here is what Meta asks you to grant, why Cuttable needs it, and what it enables. The permission name Meta uses is shown in brackets.

Create and manage your ads (ads_management)

  • Why: This is the core of the integration. Cuttable creates and updates ads, ad sets and campaigns in the ad account you select, and reads their performance.

  • What it enables: Publishing the creative you build in Cuttable straight into Meta, and the Insights tab showing how your ads (including ads you didn't make in Cuttable) are performing.

See your business assets (business_management)

  • Why: So you can choose which Business Manager and ad account to connect, rather than us guessing.

  • What it enables: Selecting the right account at connect time, and keeping that connection working.

See the Pages you manage (pages_show_list)

  • Why: Every Meta ad runs "as" a Facebook Page. We read the list of Pages you manage so you can pick the right one.

  • What it enables: Choosing which Page your ad is published under.

Read your Page's details (pages_read_engagement)

  • Why: Meta grants this alongside the Page access above as a set. It covers your Page's own content and details, so your ads publish correctly under your Page.

  • What it enables: Publishing ads under your Page identity. It is read-only, and limited to your Page's own information. It does not include the content of comments or messages your audience sends (see below).

Identify your linked Instagram account (instagram_basic)

  • Why: Meta ads can run on both Facebook and Instagram. Where an Instagram account is linked to your Page, we read its basic profile (such as the handle) so your ads can be associated with the right account.

  • What it enables: Your ads running under your own Instagram identity when you choose Instagram placements. This is read-only access to the linked account's profile and posts. It is not message access.

Your basic profile (public_profile)

  • Why: This is the standard Facebook Login default.

  • What it enables: Your name and profile picture, so we know who connected the account. Nothing more.


What Cuttable does not access

This is the part security-conscious customers usually want to know. Cuttable does not read, and does not request the permissions needed to read:

  • Your Instagram or Facebook direct messages or inboxes. Reading messages requires separate messaging permissions that we don't request.

  • The content of comments your audience leaves on your posts or ads. That requires a separate permission we don't request.

  • Your personal Facebook profile beyond your name and picture, your friends list, or your personal timeline posts.

  • Anything outside the Business Manager and ad account you choose to connect.

⭐ Important: You stay in control. You choose which Business Manager and ad account to connect, and you can disconnect Cuttable at any time from Meta Business Settings → Business assets, or in Cuttable by selecting Disconnect on the Meta card, on the Connectors tab in Settings.


Why the permission list can look broad

An ads integration has to operate across a few areas of your Meta account: the ad account where ads are created, the Page your ads run under, and the Instagram account linked to that Page. Meta also groups related permissions together, so you may see a few extra items on the consent screen (such as product-catalog access) that come bundled with the permissions we need. We only ever use the access required to publish and report on your ads, and to improve the creative we generate.


Questions or concerns

If you'd like more detail on how your data is handled, or you're reviewing the integration from a security standpoint, reach out via chat and it comes straight to our team. We're happy to walk through it.

Did this answer your question?