Skip to content
Learn › Get data in › Connections: open the docs menu

Edit, repair or delete a saved connection

Project Admins · Updated 8 Nov 2026

Project Admins change saved connections on the Connections page: go to Data, click the Connections tab and click a connection to open its details. From there you can edit its sign-in, repair it, delete it, or copy a managed database's credentials. For the list itself, see Manage saved connections.

Actions on a connection

ButtonWhat it does
Edit connectionOpens the connection form to change its details, such as a new password, key or sign-in. Built-in connectors only. When you save, Mammoth shows, for example, "Connection Sales Postgres updated".
Delete (bin icon)Deletes the connection. See Delete a connection.
Show credentialsMammoth-managed PostgreSQL and Google BigQuery only. See Get a Mammoth-managed database's credentials.

Fix a connection that needs attention

The Connectors launcher lists failing connections under Needs attention, with a reason: key expired or unreachable. Click one: the Connections page opens with that connection selected, and:

ConnectionWhat opens
A built-in connectorThe Edit connection form, to enter a new key or sign in again
A connection the agent built (a REST API)A new draft, whose chat asks for the key again
A Mammoth-managed connection"Mammoth manages this connection's credentials, so there is nothing to repair here."
Any, if you are not a Project Admin"Only a project admin can repair this connection."

Delete a connection

  1. Open the connection and click the delete (bin) icon.
  2. Read the dialog, titled with the connection's name, such as Delete connection “Sales Postgres”?. It lists what stops working.
  3. Click Delete connection.
Listed itemWhat happens
ImportsEach dataset "Stops refreshing. Rows already imported are kept."
ExportsEach task "Stops delivering. Rows already delivered stay in the destination."
Stored credentials"You’d re-enter these to reconnect"

Deleting a connection never deletes data, datasets or pipelines. Its credentials are removed, and everything that used it becomes unconfigured until you point it at another connection. Mammoth confirms, for example, "Connection Sales Postgres deleted. 3 usages are now unconfigured." If nothing uses it, the dialog says "Nothing is using this connection."

A deleted connection does not go to Trash, so you can't restore it: create it again instead. Mammoth-managed connections have no delete button; Mammoth removes one by itself when the last published View that uses it is deleted.

Get a Mammoth-managed database's credentials

Mammoth creates a managed connection when you export a View to a Mammoth-managed PostgreSQL or Google BigQuery database. To connect an outside tool (for example, a BI tool) to that database:

  1. Open the managed connection and click Show credentials (Project Admins only).
  2. The Database credentials dialog lists the values. For PostgreSQL: the host, port, username, password and database. For Google BigQuery: the dataset, the service account's email and a link to the service account key.
  3. Click Copy all to copy them.

Troubleshooting connections

SymptomCauseFix
Buttons are disabled, with a permission bannerYou are not a Project AdminAsk a Project Admin to add or change the connection, or to give you Admin access
"This workspace is in view-only mode, so connections can't be created or changed. Choose a plan to continue working."The workspace has no active planChoose a plan (see Billing and plans)
Health shows ErrorThe key expired, the source refused it, or Mammoth couldn't reach itClick Edit connection and enter a new key, or check your firewall (see Allow Mammoth through your firewall)
Datasets stopped refreshing after a deleteDeleting a connection leaves its datasets unconfiguredPoint them at another connection
A link dataset shows Last fetch failed"The link answered 404" or "The link could not be reached"Check the URL still returns the file (see Import from a URL)

For more connection problems, see Troubleshooting.

Was this page helpful?

Something wrong? support@mammoth.io