Organization Team
Team members
Manage who can access your BuildWithHQ organization and what each person can do.
| Member | Role | Status | MFA | Last login | Effective permissions | |
|---|---|---|---|---|---|---|
GI George W. Scott III Owner[email protected] | Owner | Active | On | 2 min ago | Full access | |
MR Maya Ruiz[email protected] | Administrator | Active | On | 1 hr ago | Manage teamDeploy+4 | |
DK Dan Kowalski[email protected] | Developer | Active | On | Yesterday | DeployTemplates+2 | |
PT Priya Tanaka[email protected] | Billing manager | Active | Off | 3 days ago | BillingInvoices | |
LO Leon Osei[email protected] | Support | Active | On | 5 days ago | Read tenantsSupport inbox | |
RB Riley Bhatt[email protected] | Analyst | Disabled | Off | Mar 4 | No active access |
Showing 6 of 6 members
About this page
Everyone in your organization, with their role and status. Roles decide what each person can do — and the server re-checks permissions on every single action, so what you see here is a directory, not the enforcement itself.
Behind this page/team · CanManageUsers
Retrieve
sp_Builder_ListUsers (server-injected identity) → FOR JSON PATH roster via vw_BuilderUserPermissions; read with ExecProcJson, no secrets in payload.Save
None on this list. Role →sp_Builder_UpdateUserRole; status → sp_Builder_SetUserStatus; invite → sp_Builder_CreateInvitation; transfer → sp_Builder_TransferOwnership.Success
- Roster scoped to the account.
- Seat count reconciles to plan limit.
- 403 renders permission-denied, not an error.
CLI handoff
Implement this scaffold from the structured contract, then remove hard-coded preview rows. The source of truth is CLI Handoff and admin-cli-manifest.json.
Page IDteam-members
Route/team
AccessCanManageUsers
Statusschema-backed-scaffold
Server-inject identity and scope values; never trust browser-supplied account, app, tenant, user, entitlement, price, or permission identifiers. Preserve the loading, empty, forbidden, failed, retrying, and completed states shown by the preview.