All guides
User

Teams

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/teams/stream on your site.

Steps

Use Create invite

  1. Open /portal/teams on your application domain, using the workspace account for this task.
  2. Find the form containing Email address, Invite message, Permissions. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Create invite. 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
Email addressOptional unless the current form requests it. Enter the intended email address. Use an inbox you control when practicing. The form’s example is [email protected]. Replace it with your own value. Maximum 255 characters.
Invite messageOptional unless the current form requests it. Enter the invite message for this task, using the help or example shown by the form. Maximum 1000 characters.
PermissionsEnter the permissions for this task, using the help or example shown by the form.
Managed accountsChoose an available entry by its displayed name. The list depends on your account and the selected workspace; do not type an internal record ID.
Expires onOptional unless the current form requests it. Enter the expires on for this task, using the help or example shown by the form.

Use Join team

  1. Open /portal/teams on your application domain, using the workspace account for this task.
  2. Find the form containing Invite code. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Join team. 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
Invite codeRequired. Enter the invite code for this task, using the help or example shown by the form.

Use Save team

  1. Open /portal/teams 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 Save team. 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.

Use Open

  1. Open /portal/teams on your application domain, using the workspace account for this task.
  2. Find the form containing Workspace. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Open. 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
WorkspaceEnter the workspace for this task, using the help or example shown by the form.

Use Create room

  1. Open /portal/teams on your application domain, using the workspace account for this task.
  2. Find the form containing Room name, Topic, First message. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Create room. 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
Room nameRequired. Enter the room name for this task, using the help or example shown by the form. The form’s example is Content planning. Replace it with your own value. Maximum 255 characters.
TopicOptional unless the current form requests it. Enter the topic for this task, using the help or example shown by the form. Maximum 1000 characters.
First messageOptional unless the current form requests it. Enter the first message for this task, using the help or example shown by the form. Maximum 5000 characters.

Use Save changes

  1. Open /portal/teams on your application domain, using the workspace account for this task.
  2. Find the form containing Room name, Topic. 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
Room nameRequired. Enter the room name for this task, using the help or example shown by the form. Maximum 255 characters.
TopicOptional unless the current form requests it. Enter the topic for this task, using the help or example shown by the form. Maximum 1000 characters.

Use Approve

  1. Open /portal/teams on your application domain, using the workspace account for this task.
  2. Find the form containing Decision note. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Approve. 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
Decision noteComplete the visible field for the current selection; follow its validation message.

Use Reject

  1. Open /portal/teams on your application domain, using the workspace account for this task.
  2. Find the form containing Decision note. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
  3. Select Reject. 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
Decision noteComplete the visible field for the current selection; follow its validation message.

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: 5af0236c6d99c50079f5ab8b8fb035506634bd8d

Source-only route information
MethodSource-default route
GET/portal/teams/stream
GET/portal/teams/switch
LIVEWIRE/portal/teams
LIVEWIRE/portal/teams/join/{inviteCode}
Unmapped fields — not user instructions

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

Source keyHandler
invite_codemodules/AppTeams/Livewire/Workspace.php
team_namemodules/AppTeams/Livewire/Workspace.php
team_descriptionmodules/AppTeams/Livewire/Workspace.php
enabled_modulesmodules/AppTeams/Livewire/Workspace.php
emailmodules/AppTeams/Livewire/Workspace.php
messagemodules/AppTeams/Livewire/Workspace.php
expires_atmodules/AppTeams/Livewire/Workspace.php
rolemodules/AppTeams/Livewire/Workspace.php
conversation_titlemodules/AppTeams/Livewire/Workspace.php
conversation_descriptionmodules/AppTeams/Livewire/Workspace.php
initial_messagemodules/AppTeams/Livewire/Workspace.php
bodymodules/AppTeams/Livewire/Workspace.php
edit_conversation_titlemodules/AppTeams/Livewire/Workspace.php
edit_conversation_descriptionmodules/AppTeams/Livewire/Workspace.php