User

Groups

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/publishing/groups on your application domain, using the workspace account for this task.
Select the intended record or item first and review its displayed values. There is no separate input form described for this control.
Select New group. 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.

Open /portal/publishing/groups on your application domain, using the workspace account for this task.
Find the form containing Group name, Accounts, Group status. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
Use the button shown for the current state: Save changes, Create group. Creation and editing can show different labels; submit the form once.
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
Group name	Required. Enter the group name for this task, using the help or example shown by the form. The form’s example is Launch channels. Replace it with your own value. Maximum 120 characters.
Accounts	Optional unless the current form requests it. Enter the accounts for this task, using the help or example shown by the form.
Group status	Required. Choose Active, Inactive.
Group color	Required. Enter the group color for this task, using the help or example shown by the form. Maximum 24 characters.
Description (optional)	Optional unless the current form requests it. Enter the description (optional) for this task, using the help or example shown by the form. The form’s example is When should your team use this group?. Replace it with your own value. Maximum 1000 characters.

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
LIVEWIRE	/portal/publishing/groups

Unmapped fields — not user instructions

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

Source key	Handler
form.color	modules/Publishing/AppGroups/Livewire/GroupWorkspace.php
form.status	modules/Publishing/AppGroups/Livewire/GroupWorkspace.php
form.account_ids	modules/Publishing/AppGroups/Livewire/GroupWorkspace.php