AutoNoah
Request a demo

Permissions asked of each service

What AutoNoah asks each service for when a company connects it. The same is shown on each connection in the console.

Where the service divides read and write, only read permissions are asked for until writing is allowed. Where it cannot, agents may still use only the operations you allow.

A2A agentThe service cannot divide them, so AutoNoah keeps agents within the scope.

The remote agent's provider decides its permissions.

How they are given
The API key's permissions
Permission names shown by the service
None

If you set a scope for the connection, that scope is asked for.

Official pagesA2A specification

AgentforceThe service cannot divide them, so AutoNoah keeps agents within the scope.

The permissions are set on your company's own app, and no operation only reads.

How they are given
Permissions set when the app is registered
Permission names shown by the service
  • api
  • chatbot_api
  • sfap_api
With writing allowed
Allowing writing does not change what the service is asked for.

Official pagesAgent API: Get started

AirtableRead and write permissions are asked for separately.

The service divides read and write permissions, so only read permissions are asked for until writing is allowed.

How they are given
Consent at sign-in
Permission names shown by the service (read only)
  • data.records:read
  • data.recordComments:read
  • schema.bases:read
Added when writing is allowed
  • data.records:write
  • data.recordComments:write

Official pagesAirtable: ScopesAirtable: OAuth reference

Amazon BedrockThe service cannot divide them, so AutoNoah keeps agents within the scope.

It only calls models, and what it may call is decided by AWS IAM.

How they are given
Service account
Permission names shown by the service
None

Official pagesAmazon Bedrock: API keys

AsanaRead and write permissions are asked for separately.

The service divides read and write permissions, so only read permissions are asked for until writing is allowed.

How they are given
Consent at sign-in
Permission names shown by the service (read only)
  • workspaces:read
  • projects:read
  • tasks:read
  • stories:read
Added when writing is allowed
  • tasks:write
  • stories:write

Official pagesAsana: OAuth scopesAsana: OAuth

BacklogThe service cannot divide them, so AutoNoah keeps agents within the scope.

An API key carries the rights of the user who issued it.

How they are given
The API key's permissions
Permission names shown by the service
None

Official pagesBacklog: Authentication

BoxRead and write permissions are asked for separately.

The service divides read and write permissions, so only read permissions are asked for until writing is allowed.

How they are given
Consent at sign-in
Permission names shown by the service (read only)
  • root_readonly
Added when writing is allowed
  • root_readwrite

Official pagesBox: ScopesBox: Authorize

ChatworkRead and write permissions are asked for separately.

The service divides read and write permissions, so only read permissions are asked for until writing is allowed.

How they are given
Consent at sign-in
Permission names shown by the service (read only)
  • users.profile.me:read
  • rooms.info:read
  • rooms.messages:read
  • rooms.tasks:read
  • offline_access
Added when writing is allowed
  • rooms.messages:write
  • rooms.tasks:write

Official pagesChatwork: OAuth

ClickUpThe service cannot divide them, so AutoNoah keeps agents within the scope.

ClickUp's sign-in has no kinds of permission: it carries the rights of the person who signs in.

How they are given
Consent at sign-in
Permission names shown by the service
None

Official pagesClickUp: Authentication

ConfluenceRead and write permissions are asked for separately.

The service divides read and write permissions, so only read permissions are asked for until writing is allowed.

How they are given
Consent at sign-in
Permission names shown by the service (read only)
  • search:confluence
  • read:space:confluence
  • read:page:confluence
  • read:comment:confluence
  • offline_access
Added when writing is allowed
  • write:page:confluence
  • write:comment:confluence

Official pagesConfluence: ScopesConfluence: Search (v1)

Copilot StudioThe service cannot divide them, so AutoNoah keeps agents within the scope.

It only converses with one agent, so there is no read or write to divide.

How they are given
The API key's permissions
Permission names shown by the service
None

Official pagesDirect Line authentication

DocuSignThe service cannot divide them, so AutoNoah keeps agents within the scope.

DocuSign has no read-only permission for eSignature.

How they are given
Consent at sign-in
Permission names shown by the service
  • signature
  • extended
With writing allowed
Allowing writing does not change what the service is asked for.

Official pagesDocuSign: Scopes

DropboxRead and write permissions are asked for separately.

The service divides read and write permissions, so only read permissions are asked for until writing is allowed.

How they are given
Consent at sign-in
Permission names shown by the service (read only)
  • account_info.read
  • files.metadata.read
Added when writing is allowed
  • files.content.write

Official pagesDropbox: OAuth guideDropbox API spec

Dynamics 365The service cannot divide them, so AutoNoah keeps agents within the scope.

What it may do is the signed-in person's security roles in Dynamics 365.

How they are given
Consent at sign-in
Permission names shown by the service
  • Dynamics CRM user_impersonation
  • offline_access
With writing allowed
Allowing writing does not change what the service is asked for.

Official pagesDataverse: OAuthSecurity roles and privileges

freeeThe service cannot divide them, so AutoNoah keeps agents within the scope.

The permissions are set on the app, and cannot be divided at sign-in.

How they are given
Permissions set when the app is registered
Permission names shown by the service
  • 取引
  • 振替伝票
  • 取引先
  • 勘定科目
  • 口座
  • ファイルボックス
  • freee請求書
With writing allowed
Allowing writing does not change what the service is asked for.

What the connection may do is also limited by the signed-in person's role in the company.

Official pagesfreee: アクセストークンの取得freee: アクセストークンの権限

freee人事労務The service cannot divide them, so AutoNoah keeps agents within the scope.

The permissions are set on the app, and cannot be divided at sign-in.

How they are given
Permissions set when the app is registered
Permission names shown by the service
  • 従業員
  • 勤怠
  • 申請
  • 部門（参照のみ）
With writing allowed
Allowing writing does not change what the service is asked for.

Official pagesfreee: アクセストークンの権限

FreshdeskThe service cannot divide them, so AutoNoah keeps agents within the scope.

An API key carries the agent's role.

How they are given
The API key's permissions
Permission names shown by the service
None

Official pagesFreshdesk: Authentication

GitHubThe service cannot divide them, so AutoNoah keeps agents within the scope.

The permissions are the GitHub App's, registered once for the organization.

How they are given
Permissions set when the app is registered
Permission names shown by the service
  • administration: write
  • contents: write
  • members: read
  • metadata: read
  • organization_personal_access_tokens: read
  • pull_requests: write
  • repository_hooks: write
With writing allowed
Allowing writing does not change what the service is asked for.

Official pagesPermissions required for GitHub AppsInstallation access tokens

Google Vertex AIThe service cannot divide them, so AutoNoah keeps agents within the scope.

Vertex AI takes one permission, used only to call models.

How they are given
Consent at sign-in
Permission names shown by the service
  • https://www.googleapis.com/auth/cloud-platform
With writing allowed
Allowing writing does not change what the service is asked for.

What it may call is the signed-in person's roles in the project.

Official pagesVertex AI: REST reference

Google WorkspaceRead and write permissions are asked for separately.

The service divides read and write permissions, so only read permissions are asked for until writing is allowed.

How they are given
Consent at sign-in
Permission names shown by the service (read only)
  • https://www.googleapis.com/auth/gmail.readonly
  • https://www.googleapis.com/auth/drive.readonly
  • https://www.googleapis.com/auth/documents.readonly
  • https://www.googleapis.com/auth/spreadsheets.readonly
  • https://www.googleapis.com/auth/calendar.events.readonly
Added when writing is allowed
  • https://www.googleapis.com/auth/gmail.send
  • https://www.googleapis.com/auth/gmail.compose
  • https://www.googleapis.com/auth/drive
  • https://www.googleapis.com/auth/documents
  • https://www.googleapis.com/auth/spreadsheets
  • https://www.googleapis.com/auth/calendar.events
Only some of it
Calendar, Docs, Drive, Gmail, Sheets

Official pagesGmail API scopesDrive API scopes

HubSpotRead and write permissions are asked for separately.

The service divides read and write permissions, so only read permissions are asked for until writing is allowed.

How they are given
Consent at sign-in
Permission names shown by the service (read only)
  • crm.objects.contacts.read
  • crm.objects.companies.read
  • crm.objects.deals.read
  • crm.objects.tickets.read
Added when writing is allowed
  • crm.objects.contacts.write
  • crm.objects.companies.write
  • crm.objects.deals.write
  • crm.objects.tickets.write
Only some of it
Companies, Contacts, Deals, Tickets

Official pagesHubSpot: Scopes

IntercomThe service cannot divide them, so AutoNoah keeps agents within the scope.

The permissions are ticked on the app, and a sign-in cannot narrow them.

How they are given
Permissions set when the app is registered
Permission names shown by the service
  • Read and write users and companies
  • Read and write conversations
  • Read admins
With writing allowed
Allowing writing does not change what the service is asked for.

Official pagesIntercom: OAuth scopes

JiraRead and write permissions are asked for separately.

The service divides read and write permissions, so only read permissions are asked for until writing is allowed.

How they are given
Consent at sign-in
Permission names shown by the service (read only)
  • read:jira-work
  • read:jira-user
  • offline_access
Added when writing is allowed
  • write:jira-work

Official pagesJira: Scopes

KING OF TIMEThe service cannot divide them, so AutoNoah keeps agents within the scope.

The rights are chosen when the access token is issued.

How they are given
The API key's permissions
Permission names shown by the service
None

Issue it with read rights only: every operation AutoNoah offers here only reads.

Official pagesKING OF TIME: Developer site

kintoneThe service cannot divide them, so AutoNoah keeps agents within the scope.

The rights are chosen when the app's API token is issued.

How they are given
The API key's permissions
Permission names shown by the service
None

To only read, issue the API token with record viewing alone.

Official pageskintone: APIトークン

LINE WORKSRead and write permissions are asked for separately.

The service divides read and write permissions, so only read permissions are asked for until writing is allowed.

How they are given
Consent at sign-in
Permission names shown by the service (read only)
  • bot.read
  • user.read
Added when writing is allowed
  • bot.message

Official pagesLINE WORKS: Scopes

LinearRead and write permissions are asked for separately.

The service divides read and write permissions, so only read permissions are asked for until writing is allowed.

How they are given
Consent at sign-in
Permission names shown by the service (read only)
  • read
Added when writing is allowed
  • write

Official pagesLinear: OAuth 2.0

MailchimpThe service cannot divide them, so AutoNoah keeps agents within the scope.

Mailchimp's sign-in has no kinds of permission: it carries the signed-in person's role.

How they are given
Consent at sign-in
Permission names shown by the service
None

Official pagesMailchimp: OAuth 2Mailchimp: Authentication

Microsoft 365The service cannot divide them, so AutoNoah keeps agents within the scope.

The permissions are set in the app registration, and cannot be divided per connection.

How they are given
Permissions set when the app is registered
Permission names shown by the service
  • Mail.Send
  • Mail.ReadWrite
  • Files.ReadWrite.All
  • Calendars.ReadWrite
  • openid
With writing allowed
Allowing writing does not change what the service is asked for.
Only some of it
OneDrive, Outlook

These permissions reach every mailbox in the organization unless your Exchange administrator limits the app.

Official pagesMicrosoft Graph: Client credentialsMicrosoft Graph: PermissionsExchange: RBAC for Applications

Microsoft 365 (Excel, Teams)Read and write permissions are asked for separately.

The service divides read and write permissions, so only read permissions are asked for until writing is allowed.

How they are given
Consent at sign-in
Permission names shown by the service (read only)
  • offline_access
  • https://graph.microsoft.com/Files.ReadWrite
Added when writing is allowed
  • https://graph.microsoft.com/ChannelMessage.Send
Only some of it
Excel, Teams

Microsoft asks for file read and write even to read a workbook. AutoNoah stops the writes.

Official pagesMicrosoft Graph: Get rangeMicrosoft Graph: Send chatMessage

monday.comRead and write permissions are asked for separately.

The service divides read and write permissions, so only read permissions are asked for until writing is allowed.

How they are given
Consent at sign-in
Permission names shown by the service (read only)
  • me:read
  • boards:read
  • updates:read
Added when writing is allowed
  • boards:write
  • updates:write

Official pagesmonday.com: OAuth

NotionThe service cannot divide them, so AutoNoah keeps agents within the scope.

Notion has no kinds of permission at sign-in: they are the integration's capabilities.

How they are given
Permissions set when the app is registered
Permission names shown by the service
  • Read content
  • Update content
  • Insert content
  • Read comments
  • Insert comments
With writing allowed
Allowing writing does not change what the service is asked for.

It reaches only the pages chosen on Notion's sign-in page.

Official pagesNotion: AuthorizationNotion: Capabilities

PipedriveThe service cannot divide them, so AutoNoah keeps agents within the scope.

The permissions are set on the app, and a sign-in accepts or refuses them all.

How they are given
Permissions set when the app is registered
Permission names shown by the service
  • deals:full
  • contacts:full
  • activities:full
  • search:read
With writing allowed
Allowing writing does not change what the service is asked for.

Official pagesPipedrive: Scopes

QuickBooks OnlineThe service cannot divide them, so AutoNoah keeps agents within the scope.

QuickBooks has one accounting permission, for reading and writing alike.

How they are given
Consent at sign-in
Permission names shown by the service
  • com.intuit.quickbooks.accounting
With writing allowed
Allowing writing does not change what the service is asked for.

Official pagesQuickBooks: Scopes

SalesforceThe service cannot divide them, so AutoNoah keeps agents within the scope.

Salesforce's API permission reaches everything the signed-in person may do.

How they are given
Consent at sign-in
Permission names shown by the service
  • api
  • refresh_token
With writing allowed
Allowing writing does not change what the service is asked for.
Only some of it
Accounts, Cases, Contacts, Leads, Opportunities, Tasks, Users

To make the connection itself read-only, give the integration user a permission set that only reads.

Official pagesSalesforce: OAuth tokens and scopes

SansanThe service cannot divide them, so AutoNoah keeps agents within the scope.

An API key carries the rights of the user it is issued for.

How they are given
The API key's permissions
Permission names shown by the service
None

Every operation AutoNoah offers here only reads.

Official pagesSansan Open API

SAP S/4HANA CloudThe service cannot divide them, so AutoNoah keeps agents within the scope.

What it may do is set by the communication user's arrangements.

How they are given
The API key's permissions
Permission names shown by the service
None

Every operation AutoNoah offers here only reads.

Official pagesSAP Business Accelerator Hub

ServiceNowThe service cannot divide them, so AutoNoah keeps agents within the scope.

What it may do is the application user's roles and your instance's access rules.

How they are given
Service account
Permission names shown by the service
None

Official pagesServiceNow documentation

ShopifyRead and write permissions are asked for separately.

The service divides read and write permissions, so only read permissions are asked for until writing is allowed.

How they are given
Consent at sign-in
Permission names shown by the service (read only)
  • read_products
  • read_orders
  • read_customers
  • read_inventory
  • read_locations
Added when writing is allowed
  • write_customers
  • write_orders
  • write_draft_orders

Orders older than 60 days are not reached.

Official pagesShopify: Access scopesShopify: Authorization code grant

SlackRead and write permissions are asked for separately.

The service divides read and write permissions, so only read permissions are asked for until writing is allowed.

How they are given
Consent at sign-in
Permission names shown by the service (read only)
  • channels:history
  • groups:history
  • channels:read
  • groups:read
  • users:read
  • users:read.email
Added when writing is allowed
  • chat:write

The bot posts only where it has been invited.

Official pagesSlack: Methods

SmartHRThe service cannot divide them, so AutoNoah keeps agents within the scope.

An access token carries the rights of the user who issued it.

How they are given
The API key's permissions
Permission names shown by the service
None

To only read, issue it from a user whose role only views.

Official pagesSmartHR: Developers

StripeThe service cannot divide them, so AutoNoah keeps agents within the scope.

The permissions are the Stripe App's, the same for every account that installs it.

How they are given
Permissions set when the app is registered
Permission names shown by the service
  • customer_read
  • customer_write
  • invoice_read
  • invoice_write
  • charge_read
  • payment_intent_read
  • product_read
  • plan_read
  • subscription_read
With writing allowed
Allowing writing does not change what the service is asked for.

Connecting with a restricted key instead, you can make the key read-only.

Official pagesStripe Apps: PermissionsStripe: Restricted keys

TrelloRead and write permissions are asked for separately.

The service divides read and write permissions, so only read permissions are asked for until writing is allowed.

How they are given
Consent at sign-in
Permission names shown by the service (read only)
  • read:board:trello
  • read:member:trello
  • offline_access
Added when writing is allowed
  • write:board:trello

Official pagesTrello: Scopes

XeroRead and write permissions are asked for separately.

The service divides read and write permissions, so only read permissions are asked for until writing is allowed.

How they are given
Consent at sign-in
Permission names shown by the service (read only)
  • offline_access
  • accounting.contacts.read
  • accounting.invoices.read
  • accounting.settings.read
Added when writing is allowed
  • accounting.contacts
  • accounting.invoices

Official pagesXero: Scopes

ZendeskRead and write permissions are asked for separately.

The service divides read and write permissions, so only read permissions are asked for until writing is allowed.

How they are given
Consent at sign-in
Permission names shown by the service (read only)
  • read
Added when writing is allowed
  • tickets:write

Search needs it, so Zendesk-wide read access is asked for. Agents may use only the operations you allow.

Official pagesZendesk: OAuth tokensZendesk: Granular OAuth scopes

ZoomThe service cannot divide them, so AutoNoah keeps agents within the scope.

The permissions are the Zoom app's, and are not asked for at sign-in.

How they are given
Permissions set when the app is registered
Permission names shown by the service
  • meeting:read:list_meetings
  • meeting:read:meeting
  • meeting:write:meeting
  • meeting:update:meeting
  • meeting:read:list_past_participants
  • meeting:read:summary
  • user:read:user
With writing allowed
Allowing writing does not change what the service is asked for.

Official pagesZoom: Granular scopes

クラウドサインThe service cannot divide them, so AutoNoah keeps agents within the scope.

The client ID carries the rights of the user who issued it.

How they are given
The API key's permissions
Permission names shown by the service
None

Official pagesクラウドサイン: クライアントID

ジョブカン経費精算・ワークフローThe service cannot divide them, so AutoNoah keeps agents within the scope.

Jobcan documents no way to divide an API token's rights.

How they are given
The API key's permissions
Permission names shown by the service
None

Every operation AutoNoah offers here only reads.

Official pagesジョブカン: API

マネーフォワード クラウド請求書Read and write permissions are asked for separately.

The service divides read and write permissions, so only read permissions are asked for until writing is allowed.

How they are given
Consent at sign-in
Permission names shown by the service (read only)
  • mfc/invoice/data.read
Added when writing is allowed
  • mfc/invoice/data.write

Official pagesマネーフォワード クラウド請求書: API

The services' own connections

AirtableThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
  • data.records:read
  • data.records:write
  • schema.bases:read
  • schema.bases:write
  • data.recordComments:read
  • data.recordComments:write
  • workspacesAndBases:read
With writing allowed
Allowing writing does not change what the service is asked for.
CanvaThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
None
ClickUpThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
  • read
  • write
With writing allowed
Allowing writing does not change what the service is asked for.
CloudflareThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
None
DropboxThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
  • account_info.read
  • files.metadata.read
  • files.metadata.write
  • files.content.read
  • files.content.write
  • sharing.read
  • sharing.write
  • file_requests.read
  • file_requests.write
With writing allowed
Allowing writing does not change what the service is asked for.
FigmaThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
  • mcp:connect
With writing allowed
Allowing writing does not change what the service is asked for.
freeeThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
  • mcp:read
  • mcp:write
With writing allowed
Allowing writing does not change what the service is asked for.
IntercomThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
None
Jira・ConfluenceThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
None
LinearThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
  • read
  • write
With writing allowed
Allowing writing does not change what the service is asked for.
MiroThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
  • boards:read
  • boards:write
  • openid
  • email
With writing allowed
Allowing writing does not change what the service is asked for.
MisocaThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
  • mcp:read
  • mcp:write
  • offline_access
With writing allowed
Allowing writing does not change what the service is asked for.
monday.comThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
None
NotionThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
None
Oracle NetSuiteThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
  • mcp
With writing allowed
Allowing writing does not change what the service is asked for.
PayPalThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
None
PipedriveThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
  • base
  • activities:full
  • contacts:full
  • contact-fields:full
  • deals:full
  • deal-fields:full
  • leads:full
  • mail:full
  • products:full
  • product-fields:full
  • search:read
  • users:read
With writing allowed
Allowing writing does not change what the service is asked for.
SalesforceThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
  • api
  • sfap_api
  • refresh_token
  • einstein_gpt_api
With writing allowed
Allowing writing does not change what the service is asked for.
SentryThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
  • org:read
  • project:write
  • team:write
  • event:write
  • alerts:write
With writing allowed
Allowing writing does not change what the service is asked for.
ShopifyThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
  • read_all_orders
  • read_analytics
  • read_apps
  • read_companies
  • read_legal_policies
  • read_reports
  • write_checkout_branding_settings
  • write_checkouts
  • write_collective.access
  • write_content
  • write_customers
  • write_digital_products_product
  • write_discounts
  • write_draft_orders
  • write_files
  • write_fulfillments
  • write_inventory
  • write_locales
  • write_locations
  • write_marketing_events
  • write_markets
  • write_merchant_managed_fulfillment_orders
  • write_metaobject_definitions
  • write_metaobjects
  • write_online_store_navigation
  • write_order_edits
  • write_orders
  • write_price_rules
  • write_products
  • write_publications
  • write_returns
  • write_shipping
  • write_themes
  • write_translations
  • write_validations
With writing allowed
Allowing writing does not change what the service is asked for.
SquareThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
None
StripeThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
  • mcp
With writing allowed
Allowing writing does not change what the service is asked for.
SupabaseThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
  • organizations:read
  • projects:read
  • projects:write
  • database:write
  • database:read
  • analytics:read
  • edge_functions:read
  • edge_functions:write
  • environment:read
  • environment:write
  • storage:read
  • storage:write
With writing allowed
Allowing writing does not change what the service is asked for.
VercelThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
  • openid
With writing allowed
Allowing writing does not change what the service is asked for.
WebflowThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
None
WixThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
  • offline_access
With writing allowed
Allowing writing does not change what the service is asked for.
ZapierThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
  • openid
  • profile
  • email
With writing allowed
Allowing writing does not change what the service is asked for.
ZendeskThe service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
  • read
  • write
With writing allowed
Allowing writing does not change what the service is asked for.
マネーフォワード クラウド会計The service cannot divide them, so AutoNoah keeps agents within the scope.

This is the service's own connection, and it grants its permissions as one set.

How they are given
Consent at sign-in
Permission names shown by the service
  • mfc/accounting/offices.read
  • mfc/accounting/accounts.read
  • mfc/accounting/departments.read
  • mfc/accounting/journal.read
  • mfc/accounting/journal.write
  • mfc/accounting/report.read
  • mfc/accounting/taxes.read
  • mfc/accounting/trade_partners.read
  • mfc/accounting/trade_partners.write
  • mfc/accounting/connected_account.read
  • mfc/accounting/transaction.read
  • mfc/accounting/transaction.write
With writing allowed
Allowing writing does not change what the service is asked for.
接続先で求める権限 | AutoNoah