Add project-based team member controls within ChatGPT Teams
Summary
Allow workspace owners or admins to assign specific team members to individual projects, so that not all members have access to every shared project within the workspace.
Problem
Currently, when using ChatGPT Teams, anyone in the workspace can access all shared conversations across all projects. This model works for small, highly collaborative teams — but becomes problematic when managing multiple distinct projects within the same workspace.
There’s no way to limit visibility or contribution on a per-project basis, making it difficult to collaborate securely or privately on separate initiatives (e.g., books, reports, campaigns, or client work) without creating entirely separate workspaces.
Use Case / Context
I’m using ChatGPT Teams to manage the drafting of a longform nonfiction book and other projects which are unrelated. I want to share the book project with one editor from my team, without exposing that same content to the rest of the workspace members, who are working on unrelated tasks.
In future projects, I may work with different collaborators per project — and need the ability to isolate content, memory, and assistant context accordingly.
This is also relevant for agencies, publishers, or cross-functional teams who collaborate across multiple domains (legal, editorial, marketing, research) but want to avoid cross-exposure.
Requested Behavior
- Add the concept of Project Settings within a ChatGPT Teams workspace.
- Allow workspace admins or project creators to:
- Create a new Project (e.g., “Book Project”)
- Assign specific workspace members to that project only
- Only assigned members (and the assistant) can:
- View or join conversations in that project
- Access related files or memory (if enabled)
- Collaborate within the assistant context of that project
Optional bonus features:
- Allow project-level permissions: read-only, comment, edit
Implementation Notes (Optional)
This feature parallels functionality in tools like:
- Notion (teamspaces, shared workspaces)
- Figma (team projects)
- Google Drive (folder-level access controls)
- Slack (channels visible only to members)
Adding this would align ChatGPT Teams with modern collaboration tools and allow it to scale to larger or more complex organizations.
Impact / Priority
High.
This feature is foundational for:
- Maintaining data security and relevance in multi-person teams
- Supporting solo users who manage multiple projects with different collaborators
- Avoiding workspace sprawl (i.e., having to create a separate workspace per project just to control access)
Without this, ChatGPT Teams lacks the control needed for many professional use cases and may force users to abandon Teams for smaller scale Plus accounts.