All guides
User

Client Portals

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
  1. Open /portal/client-portals on your site.

Steps

Use Enter client portal

  1. Open /client/login on your application domain, using the workspace account for this task.
  2. Find the form containing Password, Confirm password. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Enter client portal. 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
PasswordRequired. Enter the value privately from your account or the service configuration. Do not use sample credentials from a guide.
Confirm passwordRequired. Enter the value privately from your account or the service configuration. Do not use sample credentials from a guide.

Use Update password

  1. Open /client/projects on your application domain, using the workspace account for this task.
  2. Find the form containing Required to change password / Not required for first setup. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Update password. 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
Required to change password / Not required for first setupEnter the value privately from your account or the service configuration. Do not use sample credentials from a guide. The form’s example is Required to change password / Not required for first setup. Replace it with your own value.

Use Submit request

  1. Open /client/projects on your application domain, using the workspace account for this task.
  2. Find the form containing Project, Request type, Title. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Submit request. 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
ProjectChoose No specific project.
Request typeRequired. Choose General request, Revision request, Campaign request, Asset request.
TitleRequired. Enter the title for this task, using the help or example shown by the form. The form’s example is Example: Update homepage CTA before launch. Replace it with your own value. Maximum 160 characters.
Request briefRequired. Enter the request brief for this task, using the help or example shown by the form. The form’s example is Describe the change, goal, deadline, links, screenshots, Loom URL, or context your agency should know.. Replace it with your own value.
PriorityRequired. Choose Normal, High, Urgent.
Needed byEnter the needed by for this task, using the help or example shown by the form.

Use Share Access

  1. Open /portal/client-portals on your application domain, using the workspace account for this task.
  2. Select the intended record or item first and review its displayed values. There is no separate input form described for this control.
  3. Select Share Access. 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.

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 workspace 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: 40d27448e4517301d3d8f5a27ca0c7531c51f136

Source-only route information
MethodSource-default route
GET/portal/client-portals
GET/client/login
POST/client/login
POST/client/logout
GET/client/forgot-password
POST/client/forgot-password
GET/client/reset-password/{token}
POST/client/reset-password
GET/client/access/{token}
GET/client/invites/{token}
POST/client/invites/{token}
GET/client/projects
GET/client/profile
POST/client/profile/password
GET/client/search
GET/client/projects/{project}
GET/client/timeline
GET/client/deliverables
GET/client/requests
POST/client/requests
GET/client/reviews
GET/client/approvals
POST/client/reviews/{review}/comments
POST/client/approvals/{approval}/decision
GET/client/files
GET/client/files/{file}/download
GET/client/reports
GET/client/exports
GET/client/exports/{export}/download
GET/client/{portalSlug}
GET/portal/client/login
POST/portal/client/login
Unmapped fields — not user instructions

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

Source keyHandler
emailmodules/AppClientPortals/Http/Controllers/ClientPortalAuthController.php
due_datemodules/AppClientPortals/Http/Controllers/ClientPortalController.php
bodymodules/AppClientPortals/Http/Controllers/ClientPortalController.php
annotation_typemodules/AppClientPortals/Http/Controllers/ClientPortalController.php
marker_xmodules/AppClientPortals/Http/Controllers/ClientPortalController.php
marker_ymodules/AppClientPortals/Http/Controllers/ClientPortalController.php
video_timestampmodules/AppClientPortals/Http/Controllers/ClientPortalController.php
pdf_pagemodules/AppClientPortals/Http/Controllers/ClientPortalController.php
thread_keymodules/AppClientPortals/Http/Controllers/ClientPortalController.php
parent_idmodules/AppClientPortals/Http/Controllers/ClientPortalController.php
decisionmodules/AppClientPortals/Http/Controllers/ClientPortalController.php
notesmodules/AppClientPortals/Http/Controllers/ClientPortalController.php