Gradient Docs
Gradient HomeHelp DeskCommunitySign up free
Gradient Next
Gradient Next
  • About Gradient
  • Get Started
    • Quick Start
      • Install the Gradient CLI
    • Core Concepts
    • Organizing Projects
      • Secrets
      • Storing an API key as a Secret
    • Tutorials
      • Gradient Notebooks Tutorial
      • Gradient Workflows Tutorial
      • Gradient Deployments Tutorial
    • FAQ
    • Common Errors
  • Gradient Platform
    • Gradient Notebooks
      • Runtimes
      • Files and storage
      • Machines
      • Terminal
      • Shortcuts
      • Sharing
      • TensorBoard
      • Run on Gradient
    • Gradient Workflows
      • Basic operations
      • Understanding Inputs & Outputs
      • Workflow Spec
      • Gradient Actions
      • Environment Variables
      • Using YAML for Data Science
    • Gradient Deployments
      • Basic operations
      • Deployment Spec
  • Artifacts
    • Container Management
      • Custom Containers
    • Data
      • Versioned Data
        • Public Datasets Repository
        • Storage Providers
      • Persistent Storage
    • Models
      • Managing Models
        • Model Types & Metadata
        • Public Models
    • Code
    • Metrics
      • Push Metrics
      • View & Query Metrics
  • Gradient Cluster
    • Overview
      • Setup
        • Managed Private Clusters
        • Self-Hosted Clusters
          • Pre-installation steps
          • Gradient Installer CLI
          • Terraform
            • Pre-installation steps
            • Install on AWS
            • Install on bare metal / VMs
            • Install on NVIDIA DGX
          • Let's Encrypt DNS Providers
          • Updating your cluster
      • Usage
  • More
    • SDK
      • Projects Client
      • Models Client
      • Deployments Client
      • Workflows Client
      • SDK Examples
      • Full SDK Reference
    • Machine Types
      • Machine Tiers
      • Free Machines (Free Tier)
    • Your Account
      • Teams
        • Creating a Team
        • Upgrading to a Team Plan
      • Hotkeys
      • Billing & Subscriptions
        • Storage Billing
      • Public Profiles
    • Release notes
    • Roadmap
Powered by GitBook
On this page
  • Create a Project
  • Get Your Project's ID
  • Managing access to a Project
  • Linking a Project to a GitHub repository
  • Deleting a Project
  1. Get Started

Organizing Projects

PreviousCore ConceptsNextSecrets

Last updated 3 years ago

A Gradient Project is a workspace for you or your team to run Notebooks and Workflows, store Models, and manage Deployments. Projects create an additional isolation layer of organization and control (e.g., managing access) within your team. You can create a project in the web UI or the CLI.

Create a Project

On your , click Create Project.

Provide a name and then click Create.

The following command creates a Project called ExampleProject

gradient projects create --name ExampleProject

For a project name with spaces in it, enclose the name in quotes, as in --name "Example Project".

You will need to be logged into Gradient via having run gradient apiKey <your API key>, or pass the --apiKey argument, along with your key, to the command.

Get Your Project's ID

A Project's ID is a required parameter for several commands within Gradient.

To find the ID, click the ID on the left of any entry in the Projects list to copy it to your clipboard. The ID is 9 characters long and begins with p.

To get a Project ID, you can use the following command:

gradient projects list

The output table includes an ID column. The projects for your current team (API key) will be listed.

Managing access to a Project

To add other team members to a project, click any Project in the projects list to navigate to its Project details page and then click the Settings tab. On the resulting sidebar, click Collaborators.

You will then find a list of users who already have access to the Project. Add an Accessor by clicking the "Manage" button on the right side of the page. Assign other team members to the Project by selecting their name in the drop-down and clicking on "Assign User":

You can also remove members' access to a Project by clicking the "Remove Access" button next to the member's name.

Note: Only existing team members will be displayed in the drop-down list. Only Team admins can add additional team members to this list.

Additionally, project access can only be controlled through the web console – Accessors cannot be added or removed through the Gradient CLI.

Linking a Project to a GitHub repository

In future, other components of a Project, such as Notebooks and Deployments, may also become able to be linked to a repository.

Deleting a Project

You can delete a project by visiting the project's Settings page and hitting the Delete Project button.

Deleting a Project will delete its associated Notebooks, Workflows, Deployments, and Models.

To delete a Project, you can use the following command:

gradient projects delete --id <Project ID>

Deleting a Project will delete its associated Notebooks, Workflows, Deployments, and Models.

For other command line options, see the , or gradient projects create --help

Projects can be linked to a GitHub repository chosen by the user. This is done when the user , and in the Workflow creation steps the repository to which to link is chosen.

CLI command reference
creates a Workflow
main Gradient workspace page