Anvil organisations can now have more than one member. If your work on drivers is a team effort, you can invite the rest of your team into the same organisation and have everyone working against the same projects, API keys, and telemetry — rather than sharing a single login or duplicating projects across personal accounts. Invitations are how new members join. Enter a teammate's email, pick a role, and they get an email to accept. If they already have a Driverforge account they land on a "You've been invited" page and accept in one click; if they don't, the same email doubles as a signup invitation — they create their account and are joined to your organisation automatically. Invitations expire after 7 days if they aren't accepted, and can be cancelled, resent, or have their role changed while they're still pending. Access is governed by three organisation-level roles: Owner, Admin, and Member. A Member can view and contribute to every project in the org. An Admin can do everything a Member can, plus invite and remove members, change roles, and edit org and project settings. An Owner can do everything an Admin can, plus delete the org, manage billing, and transfer ownership. Roles cascade across every project — there's no per-project membership management for now, which keeps the model simple until organisations get large enough to need more. What we're thinking: Invite teammates by email with one of three roles: Owner, Admin, or Member Role applies across every project in the organisation (no per-project member lists yet) Existing Driverforge accounts accept in one click; new users get a signup-and-join flow in the same email Pending invitations can be resent, cancelled, or have their role changed; they expire in 7 days Members can leave organisations they no longer need access to Last-Owner protections: the final Owner can't be demoted, removed, or leave Audit log of membership events: invitations, role changes, removals Help us shape this: Roughly how many people work on driver development in your organisation today? Does Owner/Admin/Member cover your needs, or is there a distinction you'd want to draw that isn't there (e.g., billing-only, read-only)? Will you need per-project access control (some projects visible to some members, not others), or is org-wide access fine for now?
