Create and delete a project
Enterprise Tier
A project is the isolation boundary for a team's models, keys, Model Context Protocol (MCP) servers, policy, and members. The Create Project wizard creates the project and can grant members, models, and MCP servers in the same pass; models must already be enabled in the organization catalog (Provision models and providers). On its own the project is configuration only, selecting a data plane so Agent Router provisions the gateway that makes it callable follows in the next guide. When a project is no longer needed, delete it from the project's page after clearing anything that blocks removal.
Every wizard step except Details is optional. A project can be created empty and given members, models, and MCP servers later from its own pages: members in Manage project Users and access, MCP in Grant MCP servers and profiles to a project, and the endpoint in Provision a gateway for a project.
Persona: Platform operator working in the Admin Console.
Estimated time: 5 to 10 minutes per project to create; a few minutes to delete once blockers are cleared.
Outcomes
By the end of this guide:
- A project exists as an isolated configuration and access boundary.
- The members who should work in the project are added, with the creator as admin.
- The models the project may call are granted, with their providers granted automatically.
- The MCP servers the project may use are granted.
- A project can be deleted when it is no longer needed, after clearing live keys, data planes, gateways, and project settings.
Prerequisites
- Access to the Admin Console with permission to create projects. The Create Project button is only visible with project write permission. Deleting a project requires permission to manage projects so the Delete project option appears.
- The models the project will use already enabled in the organization's catalog. Adding provider credentials and enabling models is covered in Provision models and providers.
Step 1: open the Create Project wizard
- In the Admin Console, open Projects and select Create Project.
The wizard walks through five steps: Details, Members, Models, MCP servers, and Review. Only Details is required; the catalog steps (Members, Models, MCP servers) may be skipped and granted later.
Some steps may not appear at all. The wizard shows a catalog step only if the account can browse that catalog (the user directory, the model catalog, or the MCP server catalog). The project can still be created without those steps; someone with the missing permissions adds the grants afterward.
Step 2: name the project (Details)
- Give the project a name that identifies the team, application, or environment it represents, for example
bedrock-team. - Review the generated Project ID. It is suggested from the name and can be edited, and must use only lowercase letters, digits, and hyphens. The ID becomes the project's path, shown under the field as
/projects/<id>. - Optionally add a description.
The name is an optional display name; the Project ID is the required, permanent identifier.
Step 3: add members (optional)
- Search for users by name or email, or browse by team, and select the people who should have access.
- Optionally select a whole team to add all of its members at once.
The creator becomes the project admin automatically; everyone selected joins as a member. Selecting a team adds its current members individually, users who join the team later are not added to the project. Roles are adjusted later in Manage project Users and access.
Agent Router creates a user's record the first time they sign in, so only people who have already signed in show up in this search. Someone who has been invited but has not signed in yet cannot be added here. See Onboard developers and issue keys.
Step 4: grant models (optional)
- Pick the models the project may call, grouped by provider. Select all models from a provider in one click, or search across all models.
Providers are granted automatically based on the models picked. There is no separate provider-grant step. Model access remains explicit: a model that is not granted cannot be reached through the project's gateway and is refused at request time. This explicit grant is the mechanism behind per-project model isolation. Only models already enabled in the organization catalog appear here.
Step 5: grant MCP servers (optional)
- Pick the MCP servers the project may use from the organization's catalog.
Granting servers here scopes them to the project; building a profile that exposes them to clients is covered in Grant MCP servers and profiles to a project.
Step 6: review and create
- Check the summary of members, models, and MCP servers. Expand a section to remove individual items before creating.
- Select Create project.
If any grant fails during creation (for example one provider errors) the project is still created, and a warning lists what did not apply. Re-apply the missing grants from the project's pages afterward.
Delete a project
To remove a project that is no longer needed, open the project's page, select the ⋯ menu in the header, then Delete project. Permission to manage projects is required for this option to appear. The default project created during onboarding cannot be deleted.
A confirmation dialog opens and shows what will happen before anything is removed.
When something is blocking the delete
If the project cannot be deleted yet, the dialog says so and lists exactly what to clear first:
- Live API keys: revoke or delete them from the project first. See Issue a project-scoped API key.
- Data planes: remove them from the project first.
- Gateways: delete the project's gateway first. See Manage multiple gateways on a data plane.
- Settings (rate limit or global fallback). These have no other screen, so the dialog provides a one-click Clear settings control.
Once everything listed is cleared, the delete control unlocks.
When nothing is blocking the delete
The dialog previews the impact (for example that deletion will remove members and model assignments) so what goes away with the project is clear. Tick the I understand checkbox, then select Delete.
What gets removed
The project and everything attached to it are removed in one step: members, model assignments, provider and MCP server grants, and gateway links. Removed members lose their project permissions, and the project's API keys disappear from the keys list.
Shared organization resources are not deleted. Models, providers, MCP servers, and users themselves remain; only the project's grants and memberships are removed. Deletion is permanent. There is no undo. The project's name becomes available again right away, so a new project can reuse it.
Where to go next
A project with granted models is still configuration with nowhere to send traffic. It becomes usable only once a data plane is selected on the project and the gateway is auto-provisioned. That gateway needs a hostname of its own, and hostnames are not shared between projects, so a data plane exposing a single hostname serves a single project until another hostname is added.