# Manage restricted application and shop connections

Choose the correct credential type, save one-time secrets securely and inspect connection admission before use.

Source: https://help.smartfact.ai/manuals/configsheets/application-access

Review edition: 25 October 2026

Roles: owner

Connections have distinct purposes and authority. Application access offers temporary session-bound credentials where enabled; shop and source-observation connections use their own controlled setup. Choose the workflow that actually matches the supplying or receiving service.

## Create a restricted temporary key

Open Application access and read the site's availability notice. Choose one source, the required ability and expiry. Native tables permit reading; external sheets can also receive snapshots. Create the key only for the intended test connection.

Save this key now shows the secret once. Store it in the appropriate private settings and inspect Issued keys. These credentials depend on the issuing Owner's current Accounts session and authority. Signing out, loss of access or verification failure stops them. They are not production credentials for unattended integration.

If the response does not provide a usable secret, inspect and revoke any newly issued key before creating another. Revocation needs a confirmed outcome. Avoid copying keys into enquiry notes, screenshots or source-data tables.

## Check a shop before starting it

Where connected mode is available, use Connect a WooCommerce shop and its webhook setup. Keep endpoint and credential settings private. Run the supported checks, inspect their results and arrange an independently activated mapping before starting.

The Owner's Check and start this connection workflow records the intended admission and any unattended-work approval offered. Do not treat a saved connection or reachable endpoint as proof that current Accounts, shop, receiver and recovery checks all pass.

## Maintain the correct boundary

For qualified source observations, use the dedicated source-bound producer setup in Source observations. It has no ordinary reading, querying, rule or stock powers. Revoking a credential stops future submissions but does not automatically withdraw already accepted observations.

Inspect connection activity and current hold reasons when something stops. A stale grant or restored generation needs its own current review. Follow [Use source observations](/manuals/configsheets/source-observations) and [Review shop orders and delivery](/manuals/configsheets/shop-orders) rather than reissuing broader credentials to get around an unresolved refusal.