DocsProject settings
AdministrationProjectsProject settings
This is part of our commercial offering.

Project settings

Open Settings in a project to manage its details, defaults, features, members, and resource access. The tabs include General, Defaults, Features, Members, Teams, Projects, Agents, Queues, Namespaces, Presets, and Connections.

Settings tabs for the acme/demo project

Use General to edit the project's description, tags, visibility, and user attribution. Further down the page, Project restrictions policy lets you apply an organization policy.

General settings and user attribution for acme/demo

Users can also use the CLI to perform admin operations:

Updates

polyaxon project update -c ...

Deletion

polyaxon project delete -c ...

Default queue and presets

A project inherits the organization default queue and presets unless project defaults are set. Open Defaults to choose a queue and move presets from Available Presets to Selected Presets. Selected presets apply in the listed order.

This tab also contains Archives deletion interval, which overrides the organization retention interval.

Project defaults with archive retention, queue, and ordered presets

Access settings

By default, organization members access a project according to their organization roles. Use the settings tabs to restrict the teams that can access the project and the agents, queues, namespaces, presets, and connections it can use. If a Project restrictions policy is applied, its restrictions are synchronized and cannot be manually overridden.

Use Teams to select which teams can access the project, then click Save:

Team access controls for acme/demo before selecting restrictions

Use Agents to restrict which compute clusters the project can use:

Agent access controls for acme/demo

Use Queues to restrict which queues the project can use:

Queue access controls for acme/demo