---
url: https://void.cloud/guide/platform/administration/projects.md
description: >-
  Find users, inspect their projects and usage, and change the plan assigned to
  an account.
---

# Users and Projects

## Managing Users and Projects

Start by finding the user you want to inspect:

```sh
void platform user list --search teammate
void platform user show <user-id>
```

Use the ID from the list in the second command. The detail view shows the user's projects and usage. You can change their plan or list just their projects:

```sh
void platform user plan <user-id> pro
void platform project list --user <user-id>
void platform project show <project-id>
```

Project details include resources, domains, and recent builds and deployments. The [command reference](../../../reference/cli/platform.md#operator-commands) also covers suspending and restoring users, deleting projects, and removing accounts.

### Project Teams

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. To remove the owner, transfer ownership first.

Pending invitations remain visible until accepted or revoked. If an invitation cannot be sent by email, share its ID so the user can accept it with `void project team accept <invitation-id>`.

Removing a collaborator or admin, changing one to reader, or suspending or deleting their account [replaces the project's platform credentials](../../project-collaboration.md#change-or-remove-access), the same as the CLI.

### AI Logging

Keep prompt and response bodies out of a project's AI Gateway logs while retaining request metadata:

```sh
void platform project ai-logging <project-id> metadata
```

Only platform administrators can change this setting. It covers the project's AI requests through the platform, including calls with the app's own provider key and calls from `void dev`.

Use `off` to store no log entry or `full` to include prompts and responses. Use `inherit` to follow the owner's [plan default](./plans.md#ai-gateway-logging), then the gateway's own setting. A project setting overrides its plan default.

The command reports when new requests are expected to follow the change, normally within 2 minutes after publishing. Check progress on the project's dashboard page or with `void platform project show <project-id>`. See the [command reference](../../../reference/cli/platform-users.md#ai-gateway-logging) for logging scope, status messages, and recovery steps.

### Transferring Project Ownership

Only an installation administrator can change a project's owner. The new owner must already have an account on this platform. In the dashboard, search for the new owner on the project page and preview the transfer before applying it. The CLI accepts a user ID:

```sh
void platform project owner <project-id> <new-owner-user-id> --plan
void platform project owner <project-id> <new-owner-user-id> --yes
```

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. Its AI logging default normally applies within 2 minutes, unless the project has its own setting.

Earlier usage stays with the former owner; later usage counts toward the new owner's limits. If the command reports an incomplete transfer, inspect the project and operator event log before retrying it.

## Account Limits and Administrator Access

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](/guide/platform/administration/plans) 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, Void 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.
