Projects

Tenant admin

A project is a shared token budget with a membership. Jobs charged to it draw on its balance rather than the submitter’s.

Use them when you want to know what a piece of work cost rather than what a person cost.

Creating one

Create project takes a name and an initial token allocation from the tenant balance.

Membership

Members can be added individually or by user group. Adding a group means new members of that group join the project automatically, which is usually what you want for a standing team.

Storage

A project can be granted storage buckets in its own right, read-write or read-only, independently of what its members’ groups grant them. This is a neat way to give a team a shared dataset without editing every group.

The same two-sided rule applies: the queue still has to be linked to that storage.

Job visibility

A project can hide its jobs from its own members. With it on, members charge work to the project without seeing each other’s jobs - appropriate where the project spans people who should not see one another’s experiments.

Tokens

A project’s balance is adjusted from here or from Tenant tokens. When a user selects the project on a job, the submission summary shows the project’s balance instead of their own.

Requiring a project

Set require project on a user group and its members get no “no project” option - every job they submit must name one. That is how cost attribution becomes mandatory rather than a convention.

Deleting

A project can be deleted. Its jobs’ history remains; the budget does not.