Projects group research runs. Teams provide organizational access and compute management. Share links provide access to particular job results. These mechanisms serve different purposes.
Organize jobs into projects
In Workspace, select New Project, supply a name and description, and choose the available visibility setting. Team visibility is available when your account belongs to a team.
To organize existing jobs, select their rows and choose Move to Project. The control stays disabled until jobs are selected. The destination must be compatible with the selected jobs’ personal or team ownership. Mixed selections may have fewer compatible destinations.
Use the Projects view to browse grouped runs. Editing a project changes its organizational metadata; it does not rerun calculations or change their scientific outputs. Deleting a project leaves its jobs intact and unassigned rather than deleting their files.
Understand team access
The workspace exposes My Jobs, Team Jobs when available, and project views. Personal balances and team balances are separate. Review the relevant account context before launching large campaigns.
Team membership can grant access to jobs associated with that team. Moving a run into a project is not a way to bypass job-level access rules. Changes to team membership may affect which historical team jobs you can access.
Share a particular result
Job result pages expose sharing controls for eligible owners. A share link includes an access token for the job; treat the complete URL as sensitive. Anyone receiving a valid link may be able to inspect the associated result and files.
Removing a share link revokes that link’s future access. It cannot retract files already downloaded by a recipient. Generating a new link replaces the job’s previous share token.
Use personal ownership, team access, and explicit links according to the collaboration you need. Do not assume that a project name, job ID alone, or access to a pipeline template grants access to private molecular inputs.
Keep an audit-ready research record
Record project purpose, candidate identifiers, job IDs, and selection decisions. Keep credentials separate from scientific manifests. When contacting support, include job or project identifiers rather than granting unnecessary access to unrelated work.