Console Guides

Project Details

The per-project settings home: logo, live usage against plan limits, name/slug/description and end-user account settings, the Emails section, sharing and duplication, export/import, and the danger zone.

Find it

There is no sidebar entry for Project Details — click a project from the Projects page (or the project switcher in the topbar) to land here.

Logo, usage, limits

Project Details top section with back link, project name and slug, logo upload, usage stat cards, and the plan limits grid marked
Production API — no logo set yet, zero usage, and this project's resolved plan limits
  1. Returns to the Projects list without saving any unsaved edits below.
  2. The project's display name and its URL-safe slug, shown together as this page's header.
  3. Upload a PNG, JPEG, GIF, or WebP up to 2MB. It replaces the folder placeholder icon shown here and appears anywhere the project is listed (project switcher, Projects page, community listing if shared).
  4. Lifetime counters for this project — a brand-new project like this one starts at zero on all three.
  5. Every metered and per-project limit this project resolves to under its org's current plan — projects, storage, API calls, buckets, collections, realtime connections, monitored wallets, functions, webhooks, messaging, chat, backups, roles, and more. This is read-only here; change plan tier on Plan and Subscription to raise it.

Details

Details card showing name, slug, project ID, organization ID, description, and end-user account settings, with an Edit button
Name, IDs, description, and default end-user account settings
  1. Name, slug, copyable Project ID and Organization ID (for API calls and SDK config), an optional description, and three end-user account defaults: whether new sign-ups require email verification, whether they require phone verification, and the default account status (active or pending) assigned on registration.
  2. Switches the card into an editable form for name, description, and the three account-verification settings. Name and description are required to save.

Emails

Top of the Emails section on Project Details, showing send stat pills and the Templates / SMTP settings tabs
A full email configuration panel lives directly on this page — covered in depth on its own guide
  1. Sent, delivered, failed, bounced, complaint, and suppressed counts for every email this project has sent through either the built-in service or a custom SMTP provider.
  2. Templates lists every transactional email (welcome, verification, password reset, and more) with a click-to-edit HTML editor; SMTP settings lets you switch off the rate-limited built-in mailer for your own provider. Full walkthrough on the dedicated Emails guide.

Sharing, duplication, export, import, danger zone

Bottom of Project Details with Sharing, Duplicate this project, Export project, Import data, and Danger zone cards marked
Everything below Emails — sharing, cloning, moving data in and out, and destructive actions
  1. Make the project public so anyone can find and fork it from Community, or share it privately with specific people by email. Private is the default.
  2. Copies this project's schema — and, optionally, its data and storage files — into any organization you belong to, including this one.
  3. Downloads a portable archive of the schema, every collection's data, storage files, and users. API keys and secrets are deliberately excluded.
  4. Moves collections, documents, storage files, and auth users in from Supabase, Appwrite, Clerk, MongoDB, PostgreSQL, or MySQL automatically — see the Migrate guide for the full field-mapping flow.
  5. Transfer ownership moves the project to another organization entirely — you lose access once it's accepted. Delete project permanently removes the project and everything in it. Both require typed confirmation before they run.
Note
The Limits grid renders every key present on the project's resolved limits object verbatim (humanizing the key name) — on this shared test project it also surfaces a stray Bug Analysis entry left over from unrelated internal testing, not a real Mudbase feature. A production project's limits list will only show actual plan entitlements.