---
title: "Connection permissions"
description: "Control which accounts and data Nuxie can use."
search:
  tags: ["Features"]
  keywords: ["reconnect", "expired credentials", "provider permissions"]
---

Choose which accounts Nuxie can use by connecting them under **Connectors**. The account's permissions determine what Nuxie can read or change in that service. For example, a read-only analytics account can provide data for an investigation without allowing changes to the source.

<span id="review-account-access" />

## Account permissions

Connect an account that can access the app and data you want Nuxie to use. The setup form shows the credentials and other details required by the service; the provider's roles and scopes determine what those credentials allow.

To use an operation that needs more access, update the account's permissions at the provider and renew the connection's authorization if needed.

### Store app mappings

App Store Connect and Google Play accounts can contain more than one app. Configure the app mapping to choose which store app Nuxie uses for catalog and purchase synchronization. The mapping selects an app within the account's existing access.

Follow [App Store Connect](/docs/integrations/app-store-connect) or [Google Play](/docs/integrations/google-play) for the required credentials and mapping fields.

<span id="separate-access-from-approval" />

## Action approval

A connection makes the connector's tools available to Nuxie. It can use them to investigate a request, such as looking up a Product in your billing account. Work that needs approval is presented as a Proposal before it proceeds.

Approval applies to the change described in that Proposal. It doesn't grant additional provider permissions: the connected account must already have access to carry out the approved change.

See [Reviewing and approving work](/docs/guides/tasks-and-approvals) to approve, deny, or ask for a revised Proposal.

<span id="maintain-the-connection" />

## Reauthorize a connection

Expired credentials, revoked authorization, or changed account roles can interrupt access. Use **Reconnect** under **Connectors → Connected** to complete setup with the current account details. See [Connecting accounts](/docs/guides/connectors#permissions-and-connection-status) for the connection controls.

> **Note**
>
> Saved secrets aren't redisplayed in the form, so enter them again when requested. Enter credentials in that form rather than in Task messages.

## Disconnect and dependent Automations

[Disconnecting an account](/docs/guides/connectors#disconnect-a-service) removes its connection access, disables its event triggers, and pauses active Automations that use those triggers.

Reconnect the service, then review the account and trigger settings before resuming those Automations. Scheduled work that uses the service also needs a working connection, even when it runs on a timer rather than a provider event.
