Asset requests
The asset request system replaces ad-hoc emails and Slack messages. Client users submit hardware requests through their portal; MSP staff manage them from a central view across all clients.
How requests work
- A client user submits a request with a title, description, and priority
- The request appears in the MSP's request list (visible across all clients)
- MSP staff update the status and add response notes
- The client user sees the status update in their portal
Submitting a request (client side)
- Log into the client portal
- Go to Requests in the sidebar
- Click New Request
- Fill in:
- Title — a short summary, e.g. "Need 2 monitors for new marketing hires"
- Description — full details: specs needed, timeline, business reason
- Priority — Low, Normal, High, or Urgent
- Click Submit Request
The request is immediately visible to MSP staff. No email is sent — everything stays in Tether.
Managing requests (MSP side)
MSP staff see requests from all clients in a single list under Requests in the MSP sidebar. Requests are sorted by priority then creation date by default.
Click any request to open the detail view. From there:
- Read the full description and any previous notes
- Change the status (see below)
- Add a response note visible to the client
- Save changes
Status flow
| Status | Set by | Meaning |
|---|---|---|
open | System (on submission) | Submitted, not yet reviewed by MSP |
in_progress | MSP staff | Being worked on — hardware sourced, quote in progress, etc. |
fulfilled | MSP staff | Hardware has been provided or the request is complete |
declined | MSP staff | Request rejected — add a note explaining why |
When you update a request's status, the client sees the new status and your response note the next time they refresh the Requests page. There is no email notification — both parties check the portal.
Priority levels
| Priority | Display | Meaning |
|---|---|---|
| Low | Grey dot | No urgency — batch with other requests |
| Normal | Blue dot | Standard timeline |
| High | Amber dot | Needed within the week |
| Urgent | Red dot | Business-blocking — act immediately |
Priority is informational only — it affects sort order in the MSP list but does not trigger any automated actions.
Permissions required
| Action | Permission |
|---|---|
| Submit a request | Any authenticated client user (no specific permission required) |
| View requests in client portal | Any authenticated client user |
| Update request status and add notes (MSP side) | msp.dashboard (MSP staff only) |
Requests via the API
http# Create a request POST /api/requests Authorization: Bearer {client-token} Content-Type: application/json {{ "title": "Need 2 monitors for new hires", "description": "Joining 1 July. Dell UltraSharp 27 preferred.", "priority": "high" }} # List requests (MSP: all clients; client: own only) GET /api/requests Authorization: Bearer {token} # Update status (MSP only) PUT /api/requests/{id} Authorization: Bearer {msp-token} {{ "status": "in_progress", "response_note": "Ordered — arriving by 28 June." }}