Projects aim to provide customers the ability to organize their work. Organizations can manage access and limits, provision service accounts (through the UI), and track usage against a constrained scope within a project (e.g. models, capabilities, threads, assistants, fine tuning, storage, etc.). Usage activity can be broken down by project, and users can view billing and set cost restrictions per project.

Organization owners can view all of their Active and Archived projects in the Projects page. Learn more about user roles and permissions in the API Platform.

Only the Owner of an organization can create a project. Please refer to our roles and permissions for more information.

To switch between organizations, hover over your organization’s name on the top-left of the page and select the organization from the list:

For those organizations that are on a consolidated billing plan, sub-orgs are identified separately. Projects cannot be created within sub-orgs.

Every organization will come with a ‘Default project’. The ‘Default project’ cannot be configured for limits or renamed, members and service accounts cannot be added to it as well it inherits the full configuration of the organization. If you create new users and service accounts at the organization level, they will automatically be provisioned for the ‘Default project’. All of your existing and new work will be allocated against the default project until you have created other projects to accumulate against.

To create a new project:

1. Hover on the project name on the left-corner of the page and select Create project.

2. Provide a name, description, and business website for your project and select ‘Create’ to create your project.

You can invite new members to your organization from the Team page. Organization members can be readers or owners. Readers can make API requests and view basic organization information, while owners can manage projects, modify billing information, and manage members within an organization. Organization owners can also see all projects, members, and API keys that have been created at the project level.

To assign a user to a project, go to your organization settings, select the project, and click on Members. On the top-right of the page, select Add member to add a user to the project.

When you add a team member, you assign them an owner or member role. Project members can make API requests that read or modify data, whereas project owners can also modify project settings and manage project members. Please refer to our roles and permissions for more information.

Organization owners are automatically added as owners to new projects created within an organization. Organization owners can remove members from their organization via the organization settings ‘members’ page.

Whereas Organizations have ‘owner’ and ‘reader’ roles, projects have ‘owner’ and ‘member’ roles. Project members are analogous to organization readers. Please refer to the table below for a more detailed description of what permissions accompany each user role.

Users that are not Owners in the organization can only see projects that they are members of. Only the organization owner can see all projects, members, and API keys at the project level, and have access to the Projects page.

Only the Owner of a project can update a user’s project role or remove a user from a project. Please refer to our roles and permissions for more information.

To update a user in a project, go to your organization settings, select the project, and click on Members. You have the option to set each member’s role as a Member or Owner. You can also select Remove to remove the user from the project.

A service account acts as a pseudo-user designed for system access, distinct from individual user accounts. Only organization and project owners can create service accounts.

Go to your organization settings -> Organization -> Members -> click on "+ Service account":

First make sure you are on the project you want to add to by checking the drop-down in the top navigation bar:

Then, go to your organization settings -> Project -> Members -> click on "+ Service account":

If you do not click on "+ Service account" but instead click on the green "+ Add member" button you will only see a list of the human users in your organizations who are also specifically the role of 'reader':

So be sure you click "+ Service account" if your intention is to create a unique service account for the project you're in.

Regardless of whether you create the service account at the organization level or create one unique to a project, when you create a service account you create a unique service account ID consisting of letters, numbers, and hyphens to easily identify the service account.

After selecting the Create button, an API key is immediately created for the service account and the secret key will be provided. Please save this secret key somewhere safe and accessible. For security reasons, you won't be able to view it again through your OpenAI account. If you lose this secret key, you'll need to generate a new one.

The service account API key permissions are defaulted to read and write all of the project’s API resources. These permissions can be updated in your project’s API Keys settings.

Service accounts are listed alongside project members in your project’s member settings page. Please refer here to learn more about updating or removing a service account’s access in your project’s member settings page.

Service accounts are managed like regular accounts - in https://platform.openai.com/settings/organization/team, you can Remove a service account or update its permission like they're a user:

All project-level API keys are tied to individual user accounts. If the user leaves the project of organization, the API key becomes disabled. To maintain continuity with production/system access, we recommend using Service account API keys. Service account API keys can be managed by organization and project owners.

You can create and manage API keys for each project on that project’s settings page. In your organization settings, select the project, and click on API Keys.

To create a new secret key, select Create new secret key. You can also select the Edit key button next to a secret key to edit its permissions.

You can set permissions for each of your API keys when you create a new secret key or by editing an existing key.

Three levels of permissions are available: All, Restricted, and Read Only.

Users can be members of as many projects as are needed. Within a project, users can generate a personal API key that is scoped and limited to accessing that project and its resources.

Limits can be set across all projects and will be individually enforced. However, if the organization limit is reached before the project limit, the projects will also be rate limited.

Example:

Project A: $100 limit // Project B: $100 limit // Project C: $100 limit

Only the Owner of an organization can set and manage billing restrictions. Please refer to our roles and permissions for more information.

In your organization settings, click on the project you want to update and select Limits. You can update your Model Usage on this page.

Model usage allows you to configure which models can be used by the project, and rate limits can be set for each model as needed.

Only the Owner of an organization can set and manage billing restrictions. Please refer to our roles and permissions for more information. Any limits you set at a per project level will always be less than or equal to the limits set at the organization level. To change the limits at the organization level, in your organization settings, click on Limits, and scroll down to Usage limits.

To set your project limits, in your organization settings, click on the project you want to update and select Limits. You can update your Monthly budget, Notification threshold, and Model Usage.

The Monthly budget allows you to set a hard limit for the project’s budget. If the project's usage exceeds this amount in a given calendar month (UTC), all subsequent API requests are blocked.

To receive billing alerts for a project’s usage, you can set a budget limit under Notification threshold. If the project's usage exceeds this amount, all project and organization owners will be sent an email.

Please note that the organization owner(s) and project owner(s) will always receive these messages and this cannot be customized. In all cases, project-level limits must be lower than your organization’s limits.

Projects can be archived through either the new project listing page or on the settings of an individual project. Once a project is archived it cannot be restored. When proceeding with an archive, you will be prompted to enter the project’s name to proceed forward.

You can view a list of all archived projects through the “Archived” tab on the same project listing page.

Deleting projects is not possible, we maintain a history of all projects to ensure continuity with usage and billing tracking.

Organizations can create up to 1000 projects.

No, the migration or movement of resources (e.g. Storage, Threads, etc.) between projects is currently not supported.

OpenAI currently support a file storage quota of 100 GB of files per project.
​
If this quota is breached, you will see the following error:

We recommend you delete unused files stored on your account. For reference, you can view and list files with the API.