Connections

The Connections tab of an org's page holds the org's connections to services outside GreenMind: a Linear workspace to track work in, a Google Drive to mirror documents to, the org's own OpenAI or ElevenLabs key. Any of the org's projects can then use them; Game Designer works from these. Only the org's admins see the tab.

A brand's accounts and channels in Marketing are not here: they are connected on the brand's own settings in Marketing, and serve that brand.

Making a connection

Each service the org can connect is listed with a button for each way it offers:

• Connect: sign in to the service through GreenMind's own app there.
• Use your own app: connect through an OAuth app the org makes at the service. The dialog gives the redirect URL and the scopes to paste into it.
• Add a key: an API key or token made at the service, checked with the service before it is saved.

Credentials are sealed when they are saved and never shown again. Each service's How to set this up opens its guide, with the steps to take in that service's own console.

Looking after a connection

Each connection shows whether it is working, who it is at the service, and how many projects use it.

• Test asks the service now whether the connection still works.
• Every night each connection is checked and its token refreshed. One that the service stops taking is marked as needing to be reconnected.
• Reconnect goes the way the connection was made, and also grants more where a feature needs it.
• Disconnect asks first, then revokes the access at the service where it can and erases it here. Everything using it stops.

How connecting works in every app, the three ways in detail, webhooks, and putting a connection to use in a project, are in the console's Connections.