Audit the current auth and workspace model

Make the AI inspect the existing app structure before changing anything so the invite system fits the current data model and authorization rules.

If your app uses organizations, teams, accounts, or tenants instead of workspaces, tell the builder to map the feature to that exact model.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule

Analyze this SaaS app and map the current auth and team structure. Identify the user table or model, workspace or organization table, membership table, role system, and any existing settings or members page. Based on the current architecture, propose the minimal set of additions needed for a working invite system: database changes, API endpoints, server actions, auth checks, pages, and components. Do not implement yet; first give me a concrete plan aligned to the existing codebase.

Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

A code-aware implementation plan showing the existing user/workspace/membership setup and the exact files or areas to update.

Should NOT happen

An existing feature broke
A button only logs to console
Data disappears after refresh
Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Your notes for this step

Track what changed, failed, or needs follow-up. Notes export with the flow.

Pass the Verify Gate to complete this step

Verify before continuing

Do not move on until every check is true. The complete button stays locked until then.

The builder identifies the existing user modelThe builder identifies the workspace or organization modelThe builder identifies how roles and permissions are enforced todayThe plan names the pages or screens where invite UI belongsThe plan includes both backend and frontend changes

Do not continue if…

! Building only a modal or form without any backend invite persistence
! Creating invite links that are not validated server-side
! Marking invites as accepted in the UI without creating membership records
! Letting any logged-in user send invites regardless of role

If the AI messes this up

Use this when:

- it only made visual forms or placeholder UI
- buttons do nothing or only log to console
- data is not persisted - state disappears on refresh
- something that worked before is now broken

Use this when the AI fakes progress or breaks the feature. It forces a real fix.

You gave a generic plan. Re-scan the actual codebase and map the existing auth, workspace, and membership structure from real files. Show the exact models, routes, and pages that already exist, then revise the invite implementation plan to fit them.