Projects

A project groups related work inside one ProteinIQ workspace. Use projects for a target, screening campaign, paper, client engagement, or any other body of work you want to revisit as a unit.

Project assignment is optional. Every resource belongs to a workspace, but a job, file, workflow, run, Studio session, or AI Assistant conversation can remain in No project.

Projects and workspaces

A workspace is the collaboration, access, billing, credit, and storage boundary. A project belongs to exactly one workspace and inherits that workspace's member access.

• Switching workspaces changes which projects are available.
• A resource and its project must belong to the same workspace.
• Moving a resource between projects does not move it to another workspace.
• Workspace roles continue to determine which resources a member may view or change.

Projects do not have separate members or permissions. Project-specific access may be added in the future.

What a project can contain

Projects can organize:

• Tool jobs and their results
• Saved and uploaded files
• Workflow definitions and workflow runs
• Batch runs
• Studio sessions
• AI Assistant conversations

Each supported resource can belong to one project at a time. Moving it to another project replaces its previous project assignment. Choose No project to remove the assignment without deleting the resource.

Creating work in a project

Submission, upload, and creation flows include an optional project selector. When you start an action from a project page, that project is selected by default. You can change it or choose No project before creating the resource.

Related resources inherit project context when they are created:

• A workflow run defaults to its workflow's project.
• Jobs created by workflow and batch runs inherit the run's project.
• Jobs started from Studio inherit the Studio session's project.
• Files saved from a job default to the job's project.

Changing a parent resource's project later does not silently rewrite historical children. For example, moving a workflow changes the default for future runs, while completed runs keep their existing project.

Moving jobs and files

Use Move to project from an individual or bulk resource action.

When you move a job, ProteinIQ shows how many saved files are linked to it. Move linked saved files is selected by default, and you can clear it when the files should stay in their current project.

Moving a file does not move the job that created it. This makes it possible to curate saved assets independently from job history.

Projects and collections

Projects and collections serve different purposes:

• A project exclusively groups several kinds of work. A resource can belong to only one project at a time.
• A collection is a reusable set of saved files. One file can belong to several collections.

Collections remain workspace-wide and do not belong to projects. A collection can contain files from different projects without duplicating them.

Deleting a project

When deleting a project, choose what happens to its assigned resources:

1. Move everything to another project.
2. Keep everything in the workspace as No project.
3. Delete the project and its contents.

ProteinIQ shows the affected resource counts before deletion. Active jobs, workflow runs, and batch runs must finish or be cancelled first.

Deleting project contents is permanent. You must type the project name to confirm that option. Deleting files also removes their collection memberships, but it does not delete the collections themselves.