User

Popup Settings

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/popup/settings on your application domain, using the workspace account for this task.
Find the form containing Accent color, Font family, Displays per visitor. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
Select Save changes. 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
Accent color	Required. Enter the accent color for this task, using the help or example shown by the form.
Font family	Required. Choose System default, Inter, Arial, Georgia.
Displays per visitor	Required. Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 1. Maximum 100.
Hours	Required. Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 0. Maximum 8760.
Apply these values now	Enter the apply these values now for this task, using the help or example shown by the form.
Days	Required. Enter a number in the unit shown by this setting. Check any currency, duration or count label before saving. Minimum 7. Maximum 730.
Protection mode	Required. Choose Manual, Safe — recommended, Strict.

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: 68a5655db1bbe17c74fb211f0fe0ee4e63c8be88

Source-only route information

Method	Source-default route