Using the portal

The console at https://shovelbase.com is your organization's admin UI. The dashboard lists the organization's projects and sources and provisions new ones. Organization settings — like its name — are editable by admins from the dashboard. Inside a project, the left rail (below) groups everything the same way these docs do:

Project Overview

The landing page for a project: service health for PostgREST, GoTrue, storage-api, and edge-runtime, a restart button for each, and the connection info you'd need to point a client at it. This is the first place to look if something's not responding.

Data: Table Editor, SQL Editor, Database

Three views onto the same Postgres database, from lightest to heaviest touch: Table Editor browses rows and definitions and moves data in and out as CSV; SQL Editor runs anything; and Database is a read-only catalog of what exists — tables, functions, triggers, indexes, enums, extensions, policies, roles. Project Settings → Database (below) also lives in this same Postgres instance: the direct connection string and nightly backups.

Platform: Authentication, Storage, Functions, Queues, Feature Flags

Authentication covers users and invites, sign-in providers (email/password plus optional Google OAuth), URL configuration, and the confirmation and password-reset emails and hosted pages — all editable per project. Storage manages buckets and their objects: upload, download, generate a signed URL, toggle public/private. Functions lists deployed edge functions and shows each one's code read-only — deploys come from the CLI — with a verify_jwt toggle, plus its own sub-pages for cron Schedules, MCP endpoints, and Secrets shared by every function. Queues creates and inspects SQS queues (message counts: visible, in flight, delayed), links them to functions on its Triggers tab, and, on its Webhooks tab, gives a queue a public inbound URL that writes straight onto it. Feature Flags is a flat list of named booleans you toggle live. See Authentication, Storage, Functions, Queues, and Feature Flags for the full detail on each.

Web: Websites, Domains

Websites lists published static sites — file counts, size, last publish, public URL, delete — and has a Public APIs sub-tab for attaching a custom domain to the project API itself. Domains is where a domain you own actually gets connected: the Route53 hosted zone, a free ACM certificate, and DNS records, which Websites and Public APIs then attach to. See Websites and Domains.

Monitor: Observability, Signals, Logs

Observability is metrics, not events: a resources overview plus per-product detail pages (database, auth, storage, functions, queues, websites) — request rates, error rates, throughput. Signals is product analytics your own apps send: an events-over-time overview, a live event stream, per-user activity, and a custom-chart builder. Logs is raw request/console output: one unified timeline plus a tab per service. Rule of thumb — Observability for “is it healthy,” Signals for “what are users doing,” Logs for “what exactly happened at 2:14pm.” See Signals and Logs.

Project Settings

API shows SHOVELBASE_URL, the anon key (safe for browsers — RLS applies), and the service_role key (trusted servers only — bypasses RLS). It is also where you mint MCP access tokens — the credential an AI client uses to manage the project — and see when each was last used, rotate it, or revoke it. Database shows the direct Postgres connection string and manages nightly backups (see Database). The danger zone here is also where a project is deleted, permanently, along with everything in it.

The dashboard: Sources

One level up from any single project, the dashboard also lists the organization's sources — shared, slimmed-down projects every project in the org can read from. A source gets the same portal shell, but a shorter rail: Table Editor/SQL Editor/Database, Functions, Logs, and Settings only, since a source has no Auth, Storage, Websites, or Domains of its own. See Organizations, projects & sources.