Understanding projects

A Pinecone project belongs to an organization and contains a number of indexes and users. Only a user who belongs to the project can access the indexes in that project. Each project also has at least one project owner.

Project environments

On the new Pinecone API, you no longer choose a single cloud environment for a project. Instead, you choose a cloud environment for each index in a project. This makes it easy to manage related resources across environments and use the same API key to access them.

Project roles

There are two project roles: Owner and User. Table 1 below summarizes the permissions for each role.

Table 1: Project roles and permissions

Project role	Permissions in organization
Owner	Manage project members
Manage project API keys
Manage pod limits
User	Access API keys
Create indexes in project
Use indexes in project

API keys

Each Pinecone project has one or more API keys. In order to make calls to the Pinecone API, a user must provide a valid API key for the relevant Pinecone project.

To view the API keys for your project, open the Pinecone console, select the project, and click API Keys.

Project pod limit

To control costs, project owners can set the maximum total number of pods allowed across all pod-based indexes in a project.

Pod limits do not apply to serverless indexes. Serverless indexes auto-scale based on usage.