Users and projects
Find users and projects on your platform, inspect them, and change ownership, plan or status.
On this pageLook up a user or project · Change ownership or plan · Suspend or restore a project
Managing users and projects
Requires: login or token
These commands need a signed-in administrator session.
This step finds a user and shows their details.
void platform user list --search teammate
void platform user show <user-id>Example output: Matching users, then one user's details.
Use the ID from the list in the second command. The detail view shows the user's projects and usage. This step changes their plan, lists their projects, or shows one project. Use the user ID from the previous step.
void platform user plan <user-id> pro
void platform project list --user <user-id>Example output: The user's plan changed, then their projects.
void platform project show <project-id>Example output: The project's details.
Project details include resources, domains, and recent builds and deployments. The command reference also covers suspending and restoring users, deleting projects, and removing accounts.
In the admin dashboard, open a project to view its team. Search for a platform user and choose a role to add them immediately; an email address is not required. You can also change or remove existing members. Pending invitations created through other project workflows remain visible until accepted or revoked. If email is unavailable for a pending invitation, share its ID so the user can accept it with void project team accept <invitation-id>. The owner cannot be removed from the team; transfer ownership first. Removing a collaborator or admin, changing one to reader, or suspending or deleting their account replaces the project's platform credentials, the same as the CLI.
Transferring project ownership
Only an installation administrator can change a project's owner. The new owner needs an account on this platform. In the dashboard, search for them on the project page and preview the transfer. This step previews and applies the transfer by user ID.
void platform project owner <project-id> <new-owner-user-id> --plan
void platform project owner <project-id> <new-owner-user-id> --yesExample output: A preview, then ownership transferred.
The preview shows both owners, their plans and suspension state, blockers, and the changes to routing and usage counters. Wait for active rollbacks and builds to finish. For an ordinary active deployment, wait or use void platform deployment cancel <id>; rollback deployments cannot be canceled. A managed Sandbox controller also blocks transfer until its cleanup completes, even if no Sandbox container is running; the preview identifies the deployment that owns it.
After the transfer, the former owner becomes a project administrator. Existing project-scoped CI deploy credentials are revoked; create replacements as the new owner. The new owner's plan and limits apply immediately. Usage before the transfer remains charged to the former owner; later usage is charged to the new owner. If an apply reports partial convergence, inspect the project and operator event log before repeating it.
By default, new users on a self-hosted installation start with the custom profile, which does not cap application requests, AI usage, deployment frequency, or retained Worker deployments. Named profiles such as pro apply the platform's quota and retention policies; they do not purchase Cloudflare services or bill your users. Storage figures are not a hard storage-quota boundary. Set an operating budget and retention policy before opening signup beyond your invited team.
Use Plans and Limits to define your own plans, change limits, or choose a different default for new accounts.
The last active administrator cannot be deleted or suspended, including through the browser admin UI. Another administrator must still have access. Automatic usage limits do not remove administrator access and do not count as a manual suspension.
When removing another administrator, the platform revokes their administrator access before changing application traffic or deleting resources. If cleanup fails, access stays revoked and the error describes the partial result. A remaining administrator can inspect it and retry cleanup.
