User manual

Connect sources and destinations

Integrations shows which services are connected to the brand and what they can read or change. Creating or changing a connection requires owner permissions and access to the external service.

Section 1

Find a service by category or summary

The four categories are Writing modes, Google and Bing, CMS, and Catalogue, social, location and tickets. The summary keeps services and available messages visible when you change category.

Unsaved choices stay in their panel when changing category for the same brand. Switching category neither saves a choice nor starts a provider operation.

  1. Choose a category or a service in the summary: its link takes you to the relevant panel.
  2. Read the status; a prompt to consult the service means it still needs checking, not that it is connected.
  3. Use the service control to request its current status. Errors remain in the summary when you switch category.
Integration status summary: for each Google, Bing and publishing service, what is connected and what is missing (fictional brand, demo data)
Demo data · Ilmarde Audio

Section 2

Check the service before consenting

Each service panel shows the connection’s status, brand and scope. A name in the list does not prove it is active for the workspace: reading it before consenting avoids needless authorisations.

Search Console, Analytics, Ads and Merchant Center do not write through their respective connections. Provider consent does not make unsupported markets or features available.

  1. Open Integrations and the panel for the service you need.
  2. Read the connection’s status, brand and scope, including any unavailability message.
  3. For a read-only service, check which data it supplies before starting the connection.
Your Google listing panel: how the brand’s listing is found, proposed only when it matches your data exactly and saved once you confirm (fictional brand, demo data)
Demo data · Ilmarde Audio

Section 3

Complete property selection too

For Google services, account consent and resource selection are separate steps. The connection is complete when the summary shows the brand’s property, so the data you read truly belongs to it.

A pending consent or missing property means the connection is incomplete. Do not select an unrelated property just to continue; refresh after a conflict before trying again.

  1. Use the connect command and complete consent with the correct account.
  2. On returning, check the status and request the property list when that command is available.
  3. Select and save the brand’s property, then check the resource shown in the summary.
Google Search Console connection: authorisation with Google, the brand’s selected property and the commands to change it or remove the connection (fictional brand, demo data)
Demo data · Ilmarde Audio

Section 4

Connect publishing from approved work

CMS and ticket destinations connect from Actions; Shopify connects from the Shopping AI catalogue. Each connector has a declared writing scope: you connect only what the approved work needs.

WordPress changes approved passages, Contentful changes approved fields and other connectors follow their declared scope. These connections do not provide general access to themes, users or the whole website. Enterprise connections remain subject to the plan.

  1. Open the approved action or relevant catalogue using the screen’s signpost.
  2. Read what the connector can change, what it cannot do and which permission it requires.
  3. Complete only the connection needed for the approved work, then check its status.
Sending to an external destination: WordPress connected to the brand’s site, the approved page address and the preview before you confirm (fictional brand, demo data)
Demo data · Ilmarde Audio

Section 5

Choose a mode for each connection

Writing mode shows, for each connection, whether work is manual, requires approval or is automatic. Automatic writing belongs to the Enterprise plan and stays limited to the intervention types the connector permits.

The default mode requires approval. Automation does not authorise every intervention or bypass connector limits. Check the save result: a local selection does not prove that the server applied it.

  1. Open Writing mode and identify the relevant connection.
  2. Read its current mode and select an option that is actually available.
  3. Automation belongs to the Enterprise plan: if both plan and connector allow it, select the permitted intervention types before applying your choice.
The writing modes table: for each connection its status, the chosen mode and the action types allowed automatically, with Ticket set to automatic before the choice is applied (fictional brand, demo data)
Demo data · Ilmarde Audio

Section 6

Check the effect and revoke unused access

Here you see whether a connection is still active and disconnect it when it is no longer needed. Connection status is separate from a collection or publication outcome, which you read in the action.

Do not replace missing data with an invented number. Never send passwords or tokens to support: report the service, status and visible message without credentials.

  1. Reopen the panel and check the service, resource and status returned by the server.
  2. For applied work, read the action’s read-back and outcome rather than stopping at provider consent.
  3. To stop access, use the available disconnect command and check the updated status.
Search Console connection status: the chosen property, the command to authorise again and the one to revoke the connection from TrustInsider (fictional brand, demo data)
Demo data · Ilmarde Audio

Related paths

Definitions, FAQs, guides and methodology: from here you reach the material you need to read the results and explain them to your team in the same words.

From question to action

Learn how to use TrustInsider: choose the brand and the questions, read the collected answers, update your content and compare the results.

Read

Find the right answer

Help with access, credits, collections, integrations and data: guides, FAQs, the site assistant and support requests from your workspace.

Read