Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.pinecone.io/llms.txt

Use this file to discover all available pages before exploring further.

A Pinecone project belongs to an organization and contains a number of assistants 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 roles

If you are an organization owner or project owner, you can manage members in your project. You assign project members a specific role that determines the member’s permissions within the Pinecone console. When you invite a member at the project-level, you assign one of the following roles:
  • Project owner: Project owners have global permissions across projects they own.
  • Project user: Project users have restricted permissions for the specific projects they are invited to.
The following table summarizes the permissions for each project role:
PermissionOwnerUser
Update project names✓
Delete projects✓
View project members✓✓
Update project member roles✓
Delete project members✓
View API keys✓✓
Create API keys✓
Delete API keys✓
View indexes✓✓
Create indexes✓✓
Delete indexes✓✓
Upsert vectors✓✓
Query vectors✓✓
Fetch vectors✓✓
Update a vector✓✓
Delete a vector✓✓
List vector IDs✓✓
Get index stats✓✓
Specific to pod-based indexes:
Customers who sign up for a Standard or Enterprise plan on or after August 18, 2025 cannot create pod-based indexes. Instead, create serverless indexes, and consider using dedicated read nodes for large workloads (millions of records or more, and moderate or high query rates).
PermissionOwnerUser
Update project pod limits✓
View project pod limits✓✓
Update index size✓✓

​
API keys

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

​
Service accounts

This feature is in public preview and available only on Enterprise plans.
Service accounts enable programmatic access to Pinecone’s Admin API, which can be used to create and manage projects and API keys. Use service accounts to automate infrastructure management and integrate Pinecone into your deployment workflows, rather than through manual actions in the Pinecone console. Service accounts use the organization roles and project role for permissioning, and provide a secure and auditable way to handle programmatic access. To use service accounts, add the account to your organization before connecting it to a project.

​
Project IDs

Each Pinecone project has a unique product ID. To find the ID of a project, go to the project list in the Pinecone console.

​
See also