---
title: How to manage integrations, your workspace name and the audit log
url: https://tideswell.xyz/docs/workspace-admin/integrations
description: Connect Shopify and Klaviyo, fix a Reconnect warning, rename the workspace, and read who changed what.
---

> Documentation index: fetch https://tideswell.xyz/llms.txt to discover every page before exploring further.

# How to manage integrations, your workspace name and the audit log



Three settings screens that do not fit anywhere else: **Integrations**, **Org**, and the **Audit
log**. All three are admin-only.

## What is on the Integrations screen? [#what-is-on-the-integrations-screen]

Every connector as a row with its logo, a one-line description and a status chip: **Connected**,
**Reconnect**, **Error**, **Not connected** or **Set up needed**.

Click a row to expand it and reveal its connect and disconnect controls.

## How do you connect Shopify? [#how-do-you-connect-shopify]

Type your shop domain and approve on Shopify's own screen. There is nothing to copy or paste.

**One Shopify store per workspace**, which the screen states plainly: a second store needs a
second workspace. That single-store rule is what makes every money figure in Tideswell
unambiguous, because there is only one currency it could be in.

## What does a Reconnect warning mean? [#what-does-a-reconnect-warning-mean]

That the connection still works for reading, but is missing a permission Tideswell now needs, so
some things quietly fail.

The commonest case names itself: a store connected before stock-writing permission was required
shows that receiving is failing. Until it is re-authorized, receiving deliveries and stock
corrections fail against it, per <Ref to="purchasing/receive-a-delivery" />.

Fix it by **re-authorizing the existing store** rather than disconnecting it. That picks up the
newly required permissions without losing anything.

The banner also names the homepage banner scheduler when theme permissions are what is missing,
per <Ref to="store/homepage-banner" />.

Take Reconnect seriously. It is the one status that looks like it is working and is not.

## How do you connect Klaviyo? [#how-do-you-connect-klaviyo]

Through Klaviyo's approval screen, or by pasting a private API key instead. Both are offered:
the key route is an alternative rather than a fallback.

Klaviyo is what the customer directory is built from, so nothing appears there until this is
connected. See <Ref to="customers" />.

## What does "Set up needed" mean? [#what-does-set-up-needed-mean]

That the connector is built, but this installation's own credentials for it have not been added
yet. Google Drive, Google Calendar and HubSpot show this until they are.

It is not something you can resolve from the screen, and the row says so in plain words.

## How do you rename the workspace? [#how-do-you-rename-the-workspace]

On the **Org** screen, which holds the workspace name and its general settings.

The name is what appears at the top of everybody's sidebar, so it is worth being the company
name rather than an abbreviation only some people recognise.

## What is in the audit log? [#what-is-in-the-audit-log]

Every recorded action in the workspace, newest first: when it happened, what it was, who did it
and what kind of thing it touched.

It is **read-only**, and the page says so: entries are never edited or removed.

Filter to a single kind of action from the dropdown, which is built from the actions that have
actually occurred in your workspace. Expand a row, where one was recorded, to see a before and
after of what changed.

Page backwards with **Load older**, fifty at a time, and **Back to newest** returns you.

## How do you use it? [#how-do-you-use-it]

For the two questions nobody can otherwise answer: **who changed this setting**, and **what
happened to this record**.

Two things to expect while reading. A row without a recorded before-and-after has no expander,
deliberately, because an expander showing nothing twice is worse than none.

And actions with no person behind them, such as a scheduled run or an automation, show as
**System** rather than being attributed to somebody. A person who has since left the workspace
also shows as System rather than as somebody else, which is the honest outcome.