Managing the project

Each project is one app, one project key, one gallery, and one set of people. Everything that governs it sits on the project's own page.

The project page, top to bottom

  1. A ← Dashboard link back to your list of projects.
  2. A warning, when there is one. Owners see the expiry notice here when captures are close to being deleted. Warnings sit above everything else, including the project's name, so they are never behind a menu.
  3. The title row. The project's name on the left; on the right, Manage people, the Hot Takes Project Key button, and, for owners, a menu.
  4. Project details, the facts about the project.
  5. Recent activity, the last 10 captures.
  6. The captures module, which holds the filter row and the gallery.

The gear menu

The ⚙ appears for the project owner only, because everything inside it is owner-only. A gear that opened an empty menu would be worse than no gear. It holds:

  • Rename project
  • Export project data
  • Auto-tag app version, a switch rather than a command, set apart from the items above and below it
  • Delete project, set apart again and shown in red

The menu stays open when you pick something, because the dialog it opens appears over it. Close it with Escape, by clicking outside it, or by clicking the gear again.

Rename project

Opens a small dialog. The name changes everywhere it appears, including on your dashboard. Nothing else is affected: the project key, the captures, and the people all stay as they are.

Export project data

Downloads a ZIP straight away: every capture's media, plus a metadata.json describing them. It is built at the moment you ask for it, so it always reflects the project as it stands.

The export includes captures that have already aged out of the gallery but are still inside their 30-day grace window. Once that window closes they are gone for good, so an export is the way to keep them.

Auto-tag app version

With the switch on, each new capture is automatically tagged with the version of the app the reviewer was running, for example 2.3.4 (16). It is an ordinary tag once applied: it shows in the Tag filter, and anyone on the project can remove it from a capture.

Turn it on before a round of testing and “everything from build 16” becomes one filter click. Turn it off and past tags stay where they are.

Delete project

Permanently removes the project and every capture in it. You type the project's name to confirm, and it cannot be undone. This is the only place it lives: your dashboard's project cards carry no controls, only a link into the project.

The project key

The Hot Takes Project Key button in the title row is visible to everyone on the project. It opens the integration panel: the snippet to drop into your app, with a Copy button, a note about the microphone permission your app needs to declare, and, for owners, a Regenerate key control.

The key looks like ht_pk_…. It is publishable, which is why it ships inside your app: it identifies the project and lets reviewers enroll against it. It is not a secret that unlocks your data.

Each project has its own key. The full integration walkthrough is in the setup guide.

Regenerating the key

Regenerate if a key ends up somewhere it should not be, for example in a public repository.

Regenerating affects new enrollments only. Reviewers who have already enrolled keep working, and every capture already in the gallery is untouched. Builds carrying the old key can no longer enroll anyone new, so ship a build with the new key before you regenerate if enrollment matters to you that week.

Regenerating is owner-only.

Project details

A row of facts, not controls:

  • Captures, how many the project holds
  • Created, the date the project was made
  • Next expiration, when the next capture ages out, or “Never” on a plan with no retention limit, or “No captures yet”
  • Teammates and Reviewers, the current counts, shown to owners and managers

Dates render in the timezone saved on your account. Set it on the account page. Every control that used to sit on this card now lives in the title row or the gear menu, so the card itself is only ever something to read.

Creating a project

From your dashboard, click New Project. You give it a name and choose how the capture control appears in your build: a floating button reviewers tap, or a shake of the device.

That choice is a label for your own reference. It is not delivered to your app, so you still set the matching option in code when you call the SDK. It appears on the project's dashboard card so you can tell your projects apart at a glance.

New projects are limited by plan: 1 on Free, 10 on Starter, and 20 on Pro. See Plans and billing for the rest.

Your dashboard

Every project you own or belong to appears as a card: name, trigger style, capture and reviewer counts, and when something last happened in it. Sort the cards by recent activity or by date created.

The whole card is a link into the project and carries nothing else. Inviting a teammate, renaming, exporting and deleting all live on the project's own page, so there is one place to look for each of them rather than two.

Need a hand?

Use the support form.