Connecting and disconnecting

Who can manage integrations, what happens when you disconnect, and why an app can stop showing data without anything looking broken.

Who can

Owners and Admins. Everyone else can open an integration's page but sees You can't manage integrations in place of the connection controls.

That is the point of a workspace-level connection: one person authorizes it, and nobody else needs the credentials.

Connecting

Go to Settings > Integrations, where integrations are grouped by what they are for, and open the one you want. Each has its own page saying what it is for.

Most are a single Connect button that redirects you to the provider, asks you to authorize Screenly, and returns you to that integration's page in the same workspace, with a confirmation message.

Three are not:

Grafana wants a service account token you generate yourself, because Grafana has no OAuth flow for this. See Grafana.

Shopify asks for your store domain first, since the authorization address is built from it.

Tailscale wants an OAuth client ID, secret, and tag you create in Tailscale. You connect it here and turn it on for screens under Settings > Security. See Reaching your private network.

Salesforce additionally needs our managed package installed in your Salesforce org before the connection is useful. If it is already installed, skip that step.

Per workspace, not per person

A connection belongs to the workspace. Everyone in it can build apps on top of it without ever seeing the credential.

Slack and PagerDuty used to be per person. Since July 2026 they are workspace-level, and a workspace where several people had connected their own kept exactly one.

Disconnecting

From the same page, after a confirmation. It revokes Screenly's access at the provider.

Anything relying on it stops working, so check what is using it first. An app configured against a Salesforce dashboard does not fall back to anything; it simply shows nothing.

When something stops working

The usual cause of an app that installs fine and shows nothing is the connection rather than the app.

Access can end without anyone disconnecting it here: revoked from the provider's side, a rotated credential, an expired grant, or a service account deleted in Grafana. Screenly finds out the next time it tries to refresh, so the dashboard can still show the integration as connected for a while.