How to use ImpRYnt

Sign up with your email, or accept a teammate's invite link if someone already set up your organization. The first person to sign up for an organization becomes its Owner.

Every project, ticket, and teammate lives inside an organization — think of it as your company's workspace. You can belong to more than one (e.g. an agency working across clients), and switch between them from the Dashboard.

From the Dashboard, click New project. First, tell ImpRYnt what kind of project this is:

• •From scratch — a brand-new product with nothing built yet.
• •Upgrade — an existing product that's getting new features.
• •Fix — something already live that's broken or behaving wrong (a link to it helps).

That choice shapes the questions the AI asks next. Describe what you're building in a sentence or two, and keep chatting — the AI (Claude, ChatGPT, or Gemini, whichever your organization has configured) will ask follow-ups until it has enough to draft a full plan. Review the proposed Domains and Modules, then click Create this project.

No AI provider configured yet? A plain form is offered instead, creating a single starter node you can build out by hand — see Settings below to add a key.

Every project is a hierarchy, drawn as a map instead of a flat list:

• •Domain — a major area of the product (e.g. Payments, Authentication).
• •Module — a subsystem within a Domain (e.g. Refunds).
• •Feature — a shippable piece of a Module.
• •User Story — a specific user-facing behavior within a Feature.
• •Task — concrete engineering work under a User Story.
• •Subtask — the smallest unit of work under a Task.

Tasks and Subtasks are the tickets your team actually works — everything above them is structure that gives those tickets context. Each node is color-coded by status: locked, not started, in progress, blocked, or completed, so you can see progress at a glance without opening anything.

World View shows the entire map at once. Focus Mode narrows the map down to just the ancestry chain of wherever you currently are — useful when a project has grown large and you want to work without the rest of the map competing for attention.

The You Are Here panel always shows your current position, the trail of what you've already visited, and lets you ask the AI Navigator about your current ticket without leaving the map.

On mobile, the map becomes an indented, tappable tree list instead — the same hierarchy, built for a smaller screen.

Open any Task or Subtask to see its full detail: description, status, technical layer, and assignee. Only the assignee, or an organization Admin/Owner, can change a ticket's status or reassign it — everyone in the organization can view it.

• •Chatter — a comment thread on the ticket for async discussion.
• •Test cases — track pass/fail coverage for Task and Subtask tickets.
• •AI implementation prompt — generates a ready-to-paste prompt for your coding assistant of choice, scoped to that specific ticket.

The Tickets and Test Cases pages (top nav) list everything across every project you have access to, with search and filters — useful when you want a flat view instead of navigating the map.

From You Are Here, ask the Navigator to explain your current position, suggest what to do next, or summarize progress so far — answered in the context of exactly where you're standing in the map.

By default your organization uses ImpRYnt's shared AI keys. To use your own Anthropic, OpenAI, or Google AI key instead (recommended once you're past trying it out), add it under Settings → AI Navigator keys. Keys are scoped per organization, never shared across tenants.

From Settings, invite teammates by email — they'll get an email with a link to join. You can also copy the invite link directly if it's easier to share some other way.

• •Owner — full control, including billing and removing anyone.
• •Admin — can manage tickets, projects, and invite/manage members, but not remove the Owner.
• •Member — can view everything and work tickets assigned to them.

Projects change. Regenerate plan (from the project header) replaces the entire node tree with a fresh AI-drafted one — everything you've completed or edited is replaced, so use it deliberately. Every regeneration is saved as a version, and Version history lets you inspect or restore any previous one.

The bell icon opens your Notification Centre — updates on tickets assigned to you, like new comments or status changes. On the Dashboard, the Welcome back widget lists everything currently open in your name so you always know where to pick up.

The Milestone Map (top nav on any project) reorganizes your Task and Subtask tickets into a linear roadmap — Step 1 through the Final Step — instead of the full Domain-to-Subtask tree. Generate it with AI from your existing tickets, or build it by hand.

• •Connect a GitHub repo (Owner/Admin only, from the map itself) and Start implementation dispatches queued tickets to a coding agent one at a time — it opens a branch, writes the change, opens a PR, and auto-merges once its own tests pass.
• •Pause for approval between tickets (on by default) stops after each merge instead of auto-continuing, so credit spend never runs ahead unnoticed. Click Dispatch next ticket when you're ready to continue.
• •Every ticket's agent run shows its cost and token usage; all-time spend for the whole project is on the Dashboard.

No repo connected, or a ticket you'd rather do yourself? Set its status and assignee directly on the Milestone Map — no AI or GitHub required, and it's always free.

Shipped something you're proud of? Flip Showcase (in the project toolbar, Owner/Admin only) to list it on ImpRYnt's public homepage, linking straight to wherever you've deployed the real app.

Two building blocks, both under Settings → Connectors (organization Owner/Admin only), let ImpRYnt talk to anything else you use — directly, or via Zapier, Make, n8n, a CI pipeline, or your own script.

• •API tokens — a bearer credential for the REST API: list and update tickets, list projects.
• •Webhooks — ImpRYnt POSTs a signed JSON payload to a URL you choose whenever a subscribed event happens (ticket created, status changed, assigned, blocked, or completed).

Create a token, then call the API with it as a Bearer token:

curl https://imprynt.space/api/v1/tickets?status=BLOCKED \
  -H "Authorization: Bearer imp_xxxxxxxxxxxxxxxxxxxxxxxx"

curl -X PATCH https://imprynt.space/api/v1/tickets/<ticketId> \
  -H "Authorization: Bearer imp_xxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"status": "COMPLETED"}'

Every delivery includes an X-Imprynt-Signature header — an HMAC-SHA256 hex digest of the raw request body, signed with the secret shown when you created the webhook. Recompute it on your end and compare before trusting the payload:

const crypto = require("node:crypto");

const expected = "sha256=" + crypto
  .createHmac("sha256", webhookSecret)
  .update(rawRequestBody) // the exact bytes received, before JSON.parse
  .digest("hex");

if (expected !== req.headers["x-imprynt-signature"]) {
  throw new Error("Invalid webhook signature");
}

Stuck, or found something broken? Message us on WhatsApp for the fastest reply, or use the chat bubble in the bottom corner of any page or the contact form on the homepage — all three reach the team directly.