Requests¶
The Requests feature lets you submit structured requests to platform administrators — for more GPU quota, new storage, image access, feature suggestions, or bug reports.
Access: All authenticated users.
Request Types¶
| Type | When to Use |
|---|---|
| Resource | Need more GPU/CPU quota, additional storage capacity, or new resource allocation |
| Access | Need to join a group, access a shared PVC, or get elevated permissions |
| Feature | Suggest a new platform feature |
| Bug | Report a platform issue |
| Question | Ask a general question to platform administrators |
| Other | Anything that doesn't fit the above categories |
Request Lifecycle¶
stateDiagram-v2
[*] --> Submitted : User submits form
Submitted --> UnderReview : Admin opens request
UnderReview --> Approved : Admin approves
UnderReview --> Rejected : Admin rejects
UnderReview --> Submitted : Admin requests more info
Approved --> [*]
Rejected --> [*]
My Requests Page¶
Figure 1: Requests list showing request cards with type tags, status badges, and creation dates.
The Requests page lists all requests you have submitted, with:
- Type tag — coloured label (Resource, Access, Feature, Bug, Question, Other)
- Status badge — Submitted, Under Review, Approved, Rejected
- Title — your request title
- Created — submission date
- Click any request to open the detail view with the message thread
Submit a New Request¶
- Click Requests in the left sidebar.
- Click + New Request (top-right).
Figure 2: New request creation form with type selector, title, and description fields.
- Fill in the form:
| Field | Description |
|---|---|
| Project | Optional — link the request to a project so admins see its current GPU quota. The selected project's GPU bar appears beside the picker. |
| Type | Select the request category from the tag grid (Resource, Access, Feature, Bug, Question, Other). |
| Title | Short, descriptive title (e.g., "Request 4 GPU units for project LLM-Training"). |
| Description | Rich-text editor — supports formatting, code blocks, and inline image uploads. Drag screenshots in to attach evidence. |
- Click Submit.
Be specific in your description
A clear description speeds up admin review. For resource requests, include: which project needs the quota, how many GPUs you need, for how long, and the research objective.
Image Requests¶
When you need a base image that is not in the platform's allowed list, use the Request Image form (linked from the project Images tab and the dashboard image catalog). It is a structured request type that an admin can act on without back-and-forth.
| Field | Description |
|---|---|
| Registry | Optional. Defaults to docker.io when blank. |
| Repository | Image path without tag, e.g. pytorch/pytorch or nvidia/* (use * for wildcard requests). |
| Tag | Optional. Defaults to latest, or * when the repository is a wildcard. |
A live preview shows the canonical image reference admins will review. Once approved, the image is added to the platform allowlist and becomes selectable from the workspace and deploy forms.
Track Your Request¶
- Open your request from the list.
- The detail page shows the full message thread.
- If an admin asks for more information, you'll see their message in the thread — reply using the text box at the bottom.
Figure 3: Request detail page showing status history and message thread between user and admin.
Common Questions¶
How long does it take for a request to be reviewed?
Review times vary. Resource requests typically take 1–2 business days. Bug reports are triaged as soon as possible.
My request was rejected. Can I resubmit?
Yes. Create a new request with updated details. Reference the previous request number in your description if helpful.
I don't see a notification when my request is approved.
Check your notification settings under Settings → Notifications. Make sure email notifications for request updates are enabled.