Create Accountor Login
Docs

Work Requests in Your Account

Part of the MountDev Ops Workspace documentation. Updated November 19, 2026

MountDev Ops Workspace documentation | Updated November 19, 2026

A work request is how you ask your provider for work from your own account: a new project, or a change to something they built. You pick what you need, fill in a short form, and see where your request stands.

Our Commitment

MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.

Every update passes all 8,865 automated checks before it ships, and every screen change is walked through before release.

Where It Is

Requests in the left column. When your provider has turned on at least one kind of work, New Work Request appears beside New Request. Nothing is added to the menu. With nothing turned on, Requests looks as it always did.

Work requests come from your provider's own pages, through the client feed (Client Feed). Until an owner or admin turns the feed on for your account, Requests says: "An owner or admin needs to turn on your provider's pages first." New Request keeps working.

Sending One

Choose New Work Request, pick what you would like to ask for (skipped when there is only one kind), fill in the fields, and choose Send Request. Before you send, the form says what your provider will receive: the answers below, your name, and your email. Nothing else of your account is sent. A double tap, or a retry, sends one request. Never put a password or a key in a request.

You may have a few open requests at once (5 at first, set by your provider). At the limit the form says: "You have 5 open requests. Please wait for an answer before sending another."

Who may send: people who hold Send a work request to your provider (action core.work_requests.client.send). Everyone who uses Requests holds it at first, and an owner can take it away through a role or permission group. Someone without it sees "New Work Request: Ask an owner to send this" as text. An AI agent, an API key, or an assistant never sends a work request for your account.

Where It Stands

One card for each request, newest first, with its status in words:

  • Received: your provider's account has it.
  • Preparing Your Proposal: your provider started a proposal from it.
  • Proposal Sent: the proposal is ready. The card shows Open Proposal, the same private link the proposal's email carries.
  • Accepted: you accepted that proposal.
  • Not Going Ahead: your provider declined it, with a sentence from them.
  • Withdrawn: you withdrew it.

You can Withdraw a request only while it is Received (action core.work_requests.client.withdraw). The person who sent a request gets one notice on their own bell when it becomes Proposal Sent and one when it becomes Not Going Ahead. No email is sent for a work request.

People who hold See the work requests your account sent (action core.work_requests.client.list, with core.work_requests.client.types for the kinds of work offered) see them. Everyone who uses Requests holds it at first. A closed account still sees its past requests and cannot send a new one (Closed Accounts).

What Your Provider Sees

Your provider sees the request you sent and nothing else of your account. It cannot read your records, settings, or people. What your account keeps of your provider's answers is part of Export Everything.

Actions

  • core.work_requests.client.types shows the kinds of work your provider lets you ask for. People only.
  • core.work_requests.client.list shows the work requests your account sent and where each stands. People only.
  • core.work_requests.client.send sends a work request. People only.
  • core.work_requests.client.withdraw withdraws a work request that has not been started on. People only.

Ask Us Anything

We’d love to hear from you!