Manage projects

Projects are used to control collaborator access to systems and backends that are allocated to a group. Collaborators can only access backends that are added to the projects that they belong to. For example, if you have one project that can access system reservations, only members of that project can access systems during reserved system time.

You can make changes to and view information about projects, including managing collaborators, managing backends, and accessing job results.

Create a project

You can create up to 100 projects per group. Because projects are members of groups, you create a project from within a group.


Do not include personal information in hub, group, or project details.

  1. From the Groups tab, select the group where you want to create a new project. Alternatively, you can create a new group first (see Groups).

  2. Click Add project +.

  3. Enter the project details, including the title and description. The name is used to connect to the hub in Qiskit. It is auto-genterated, but editable. Click Next.

  4. Select an available system or simulator and set the priority, maximum circuits, and maximum shots, then click Add +. See Define system share and What values should I set for Max circuits and Max shots? for help setting these values. Continue allocating systems and simulators as necessary, then click Next.

  5. Add Collaborators by entering their email addresses, then click Save and close the window.

The project details page features three tabs: Collaborators, Backends, and Results. For more information on Results, visit the Results page.


The Backends tab lists all available backends for your project.

Backend details

All backends that are allocated to the project are listed. Click any backend to see detailed information.

Define system share

Priority of jobs in the queue is determined globally and is based on the usage of all systems (not on individual backends). Hub and group administrators can adjust the job priority among groups and projects from the administrator dashboard. See Fair-share queuing and What is a system share (queue slot)? for more information.

What is a system share (queue slot)?

A hub’s entitlement determines its proportional share of a system, which is measured in portions of system shares. System shares implement a fair-share algorithm that helps to facilitate job prioritization. The algorithm balances the recent history of on-chip execution time with the order of job submissions, in order to determine which jobs run next, and where in the queue a submitted job will sit. Therefore, the length of a queue is not necessarily an indication of how long a job will take to run.

The queueing system first tries to satisfy the hub’s share. It then determines which group, and then which project, will go next. This hierarchical relationship means that while a system share may be available to a hub, the queueing behavior is based on the recent activity and usage of other providers (a hub/group/project combination) in the hub.


User A in one hub, who has not submitted a job for a long time, submits a job to a queue. User B, in a different hub, is constantly submitting jobs to the same queue. Even though User A’s job may have been submitted after User B’s jobs, User A’s job may be interleaved among User B’s jobs already in the queue, or User A’s job may be run before all of User B’s submitted jobs.