User

Projects

Screen guide

Before you start

Use the account and workspace that own the relevant records. The feature also needs to be enabled for this installation and plan.

Open this feature

Choose a task

Open /portal/projects on your application domain, using the workspace account for this task.
Find the form containing Project name, Company name, Company. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
Select Create project. Check the current record, recipients, amount or destination before confirming when those values apply.
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.

Field	What to enter or choose
Project name	Required. Enter the project name for this task, using the help or example shown by the form. The form’s example is Website launch. Replace it with your own value. Maximum 255 characters.
Company name	Required. Enter the company name for this task, using the help or example shown by the form. The form’s example is Client company name. Replace it with your own value.
Company	Required. Enter the company for this task, using the help or example shown by the form.
Priority	Required. Choose Low, Normal, High, Urgent.
Due Date	Optional unless the current form requests it. Use the date/time picker. Check the date range and the timezone shown by your account or this screen.

Open /portal/projects and select the record you want to work with. Its detail/edit address follows /portal/projects/{project}. Use the application’s record link; do not type a placeholder such as {id}.
Find the form containing Name this work item, Add context, scope, or instructions. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
Select Create. Check the current record, recipients, amount or destination before confirming when those values apply.
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.

Field	What to enter or choose
Name this work item	Enter the name this work item for this task, using the help or example shown by the form. The form’s example is Name this work item. Replace it with your own value.
Add context, scope, or instructions	Enter the add context, scope, or instructions for this task, using the help or example shown by the form. The form’s example is Add context, scope, or instructions. Replace it with your own value.

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

Stay in the same account/workspace and reopen the intended record or result screen.
For saved settings, compare the displayed values with the choices you made. For filters and previews, check the current result scope.
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.

Problem	What to check
The screen or action is missing	Check the correct workspace account, role, enabled app and plan. A hidden action is not fixed by typing an internal endpoint.
A field is rejected	Read 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 empty	Check 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 pending	Check its status/history before repeating it. For messages, publishing, imports and payments, a submitted request can finish later or fail separately.

Role-scoped source references

Pinned commit: 40d27448e4517301d3d8f5a27ca0c7531c51f136

Source-only route information

Method	Source-default route
GET	/portal/projects
GET	/portal/projects/{project}

Unmapped fields — not user instructions

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

Source key	Handler
due_date	modules/AppProjects/Livewire/ProjectIndex.php
quickPriority	modules/AppProjects/Livewire/ProjectWorkspace.php
quickClientId	modules/AppProjects/Livewire/ProjectWorkspace.php
quickDeliverableId	modules/AppProjects/Livewire/ProjectWorkspace.php
quickClientId	modules/AppProjects/Livewire/ProjectWorkspace.php
quickDueDate	modules/AppProjects/Livewire/ProjectWorkspace.php
quickDescription	modules/AppProjects/Livewire/ProjectWorkspace.php
quickAssetId	modules/AppProjects/Livewire/ProjectWorkspace.php
quickTitle	modules/AppProjects/Livewire/ProjectWorkspace.php
quickDescription	modules/AppProjects/Livewire/ProjectWorkspace.php