Feature Requests

Enable admin to manage all users, owner can manage permissions for each member

Implement file management system, allowing the user to attach files, and upload avatar to S3, Cloud Storage.

First of all, congratulations on your great Product! It would be ideal to restrict access to the organization when the Tier is set to Not Subscribed or Free. Many SaaS platforms require a paid subscription for access, meaning there’s no completely free version—only a paid option. Alternatively, you could define different access levels based on the subscription tier. For example, clearly specifying what features the Free Plan includes versus what is covered under the Pro Plan would help differentiate them.

As one of the future starterkits. Man, it's going to be a great developer experience for you, I promise)

Integrate PostHog for product analytics.

For a real application intended for production, it's essential to have unit tests and integration tests. Managing a system without these items is unfeasible and irresponsible, as they are crucial to verify what is working and what is not.

It will be nice to add the ability to chose if you want to activate email password login or Magic Link

Allow using Sendgrid SMTP by default. Sendgrid is a great alternative to Gmail and works seamlessly with nodemailer. It can be added by following these steps: Add to .env EMAIL_SENDGRID_HOST=smtp.sendgrid.net EMAIL_SENDGRID_PORT=587 EMAIL_SENDGRID_USERNAME=apikey EMAIL_SENDGRID_PASSWORD= Update detect-transport.ts Something like this.. Feel free to adjust the flow of logic, but checking it first in conf. makes good sense for me. // Check for SendGrid configuration first if ( env.EMAIL _SENDGRID_HOST && env.EMAIL _SENDGRID_PORT) { return { host: env.EMAIL _SENDGRID_HOST, port: parseInt( env.EMAIL _SENDGRID_PORT), auth: { user: env.EMAIL _SENDGRID_USERNAME || 'apikey', pass: env.EMAIL _SENDGRID_PASSWORD }, secure: false // SendGrid uses TLS }; } Update the keys.ts (createEnv) Added the " EMAIL_SENDGRID_" prefixed keys.. createEnv({ server: { EMAIL_FROM: z.string(), // emails can be in format "Acme < noreply@mailer.example.com >" EMAIL_FEEDBACK_INBOX: z.string().email().optional(), EMAIL_MAILER: z.enum(['NodeMailer', 'Resend']), // credentials (you just need one) EMAIL_NODEMAILER_URL: z.string().optional(), EMAIL_RESEND_API_KEY: z.string().optional(), EMAIL_SENDGRID_HOST: z.string().optional(), EMAIL_SENDGRID_PORT: z.string().optional(), EMAIL_SENDGRID_USERNAME: z.string().optional(), EMAIL_SENDGRID_PASSWORD: z.string().optional() }, runtimeEnv: { EMAIL_FROM: process.env.EMAIL _FROM, EMAIL_FEEDBACK_INBOX: process.env.EMAIL _FEEDBACK_INBOX, EMAIL_MAILER: process.env.EMAIL _MAILER, EMAIL_NODEMAILER_URL: process.env.EMAIL _NODEMAILER_URL, EMAIL_RESEND_API_KEY: process.env.EMAIL _RESEND_API_KEY, EMAIL_SENDGRID_HOST: process.env.EMAIL _SENDGRID_HOST, EMAIL_SENDGRID_PORT: process.env.EMAIL _SENDGRID_PORT, EMAIL_SENDGRID_USERNAME: process.env.EMAIL _SENDGRID_USERNAME, EMAIL_SENDGRID_PASSWORD: process.env.EMAIL _SENDGRID_PASSWORD } And that's it, Sendgrid works.

Similar to a multi select, this is specialized to pick "people". This is an "advanced" component, means that you usually don't need it in the beginning, but later when your application grows.

Add Sentry for application logging and performance monitoring