All guides
Admin

Services

Screen guide

Before you start

Use an administrator account with permission to manage this feature. The feature also needs to be enabled for this installation and plan.

Open this feature
  1. Open /admin/services on your site.

Steps

Use Post reply

  1. Open /admin/services/orders on your application domain, using the administrator account for this task.
  2. Find the form containing Write an update, ask a question or confirm delivery details.... Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Post reply. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
Write an update, ask a question or confirm delivery details...Required. Enter the write an update, ask a question or confirm delivery details... for this task, using the help or example shown by the form. The form’s example is Write an update, ask a question or confirm delivery details.... Replace it with your own value.

Use Save progress

  1. Open /admin/services/orders on your application domain, using the administrator account for this task.
  2. Find the form containing Use this note for delivery scope, summary updates or the next action the client should take.. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Save progress. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
Use this note for delivery scope, summary updates or the next action the client should take.Enter the use this note for delivery scope, summary updates or the next action the client should take. for this task, using the help or example shown by the form. The form’s example is Use this note for delivery scope, summary updates or the next action the client should take.. Replace it with your own value.

Use Save changes

  1. Open /admin/services on your application domain, using the administrator account for this task.
  2. Find the form containing Title, Short description, Fixed price. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Save changes. Check the current record, recipients, amount or destination before confirming when those values apply.
  4. If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.
FieldWhat to enter or choose
TitleRequired. Enter the title for this task, using the help or example shown by the form. Maximum 255 characters.
Short descriptionOptional unless the current form requests it. Enter the short description for this task, using the help or example shown by the form. Maximum 255 characters.
Fixed priceRequired. Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 0. Maximum 9999999.
TurnaroundOptional unless the current form requests it. Enter the turnaround for this task, using the help or example shown by the form. The form’s example is Example: 24 hours. Replace it with your own value. Maximum 120 characters.
PositionOptional unless the current form requests it. Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 0. Maximum 9999.
Icon classOptional unless the current form requests it. Enter the icon class for this task, using the help or example shown by the form. The form’s example is fa-light fa-screwdriver-wrench. Replace it with your own value. Maximum 120 characters.
DescriptionOptional unless the current form requests it. Enter the description for this task, using the help or example shown by the form.
Requirement instructionsOptional unless the current form requests it. Enter the requirement instructions for this task, using the help or example shown by the form. The form’s example is Tell the client what they must provide after payment. Example: domain, hosting login, WordPress admin, color preferences, screenshots, or access notes.. Replace it with your own value. Maximum 10000 characters.
StatusRequired. Choose Enable, Disable.

Fields and choices

Field descriptions appear beside each task above so that separate forms are not mixed together.

Check the result

  1. Stay in the same account/workspace and reopen the intended record or result screen.
  2. For saved settings, compare the displayed values with the choices you made. For filters and previews, check the current result scope.
  3. For queued or external work, inspect its status/history and provider result where applicable. A successful save does not by itself prove message delivery, publication, payment completion or provider approval.

Common problems

ProblemWhat to check
The screen or action is missingCheck the correct administrator account, role, enabled app and plan. A hidden action is not fixed by typing an internal endpoint.
A field is rejectedRead its validation message, choose from the offered options and check the relevant format or limit. Do not substitute a database ID for a displayed choice.
A list is emptyCheck the selected workspace, search text, date range and status filters. Clear one filter at a time before concluding that records are missing.
A request is still pendingCheck its status/history before repeating it. For messages, publishing, imports and payments, a submitted request can finish later or fail separately.

Technical reference

Role-scoped source references

Pinned commit: 275481cdd3c8519a24c5ecf5cac3e11ceb1708d8

Source-only route information
MethodSource-default route
RESOURCE/admin/services
POST/admin/services/list
GET/admin/services/update
GET/admin/services/edit/{id}
POST/admin/services/save
POST/admin/services/status/{any}
POST/admin/services/destroy
GET/admin/services/orders
POST/admin/services/orders/list
POST/admin/services/orders/status/{stage}
POST/admin/services/orders/destroy
GET/admin/services/orders/view/{id}
GET/admin/services/orders/view/{id}/messages
POST/admin/services/orders/save/{id}
POST/admin/services/orders/message/{id}
POST/admin/services/orders/view/{id}/messages/{message}/update
POST/admin/services/orders/view/{id}/messages/{message}/delete
Unmapped fields — not user instructions

These fields belong to this role’s source handler, but their screen labels were not confirmed.

Source keyHandler
status_labelmodules/AdminServices/app/Http/Controllers/AdminServiceOrdersController.php
progress_percentmodules/AdminServices/app/Http/Controllers/AdminServiceOrdersController.php
notemodules/AdminServices/app/Http/Controllers/AdminServiceOrdersController.php
amountmodules/AdminServices/app/Http/Controllers/AdminServiceOrdersController.php
statusmodules/AdminServices/app/Http/Controllers/AdminServiceOrdersController.php
messagemodules/AdminServices/app/Http/Controllers/AdminServiceOrdersController.php
titlemodules/AdminServices/app/Http/Controllers/AdminServicesController.php
excerptmodules/AdminServices/app/Http/Controllers/AdminServicesController.php
descriptionmodules/AdminServices/app/Http/Controllers/AdminServicesController.php
requirement_promptmodules/AdminServices/app/Http/Controllers/AdminServicesController.php
iconmodules/AdminServices/app/Http/Controllers/AdminServicesController.php
pricemodules/AdminServices/app/Http/Controllers/AdminServicesController.php
turnaroundmodules/AdminServices/app/Http/Controllers/AdminServicesController.php
positionmodules/AdminServices/app/Http/Controllers/AdminServicesController.php
statusmodules/AdminServices/app/Http/Controllers/AdminServicesController.php
pricemodules/AdminServices/app/Http/Controllers/AdminServicesController.php