Team | Waziper Official documentation

Before you start

Use the account and workspace that own the records. This page does not include administrator configuration forms.

Open this feature

Open /portal/teams on your application domain, or use the matching item in the application menu.

Steps

Save changes / Create team

Open /portal/teams/create on your own application domain.
Complete these fields in that form: Team name, Description. Their choices and limits are listed below.
Select Save changes / Create team. The exact label can change between creating and editing a record.
If validation fails, correct the named field and submit again. After success, reopen the same record and compare the saved values.

Field shown in the form	What to enter	Example / note
Team name	Required. Use a stable name because it appears in the workspace switcher and shell header. No more than 255 characters.	Test record (use a unique value where required).
Description	Optional, unless this form asks for it. Optional context for the client, brand, or workflow this workspace contains. No more than 5000 characters.	A short description of this test record.

Fields shown in the interface

Only fields traced to this role’s handler and its own view are listed. The application can show separate create/edit forms; do not fill every row on one screen.

Form 1 — fields shown in the interface

Field	What to enter or choose
Team name	Required. Use a stable name because it appears in the workspace switcher and shell header. No more than 255 characters.
Description	Optional, unless this form asks for it. Optional context for the client, brand, or workflow this workspace contains. No more than 5000 characters.

Form 2 — fields shown in the interface

Field	What to enter or choose
Email or phone number	Required. At least 5 characters. No more than 190 characters.
Role	Required. Choose Admin, Editor, Member.

Check the result

After a source-checked procedure, verify the same record in the same workspace. Check saved values, visible state and access with the intended test account. An external payment/message/provider action needs its own result check.

Problems and validation

Problem	Next step
A field rejects the value	Check its named error, the form’s visible choices and the relevant limit. Do not substitute internal numeric codes for the displayed options.
The control is missing	Check role, plan, enabled app and current record state. Do not grant administrator access merely to complete a User task.
The saved result is unexpected	Reopen the same record and verify its owner/workspace before repeating the action.

Messages defined for this screen

Message	What to review
Too many searches. Please try again in a few minutes.	Check the related field or action in this role’s form.
Enter a registered email address or phone number.	Check the related field or action in this role’s form.
This account is unavailable or is already a workspace member.	Check the related field or action in this role’s form.
Review the member and permissions before confirming.	Check the related field or action in this role’s form.
This user is already in the workspace.	Check the related field or action in this role’s form.

Technical reference

Role-scoped source references

Pinned commit: 37d44a1727216f5c492205024b323aa522730ebc

Source-only route information

Method	Source-default route
GET	/portal/teams
GET	/portal/teams/create
GET	/portal/teams/switch/{team}
GET	/portal/teams/{team}/edit
GET	/portal/teams/{team}/members
GET	/portal/teams/apps/manage

Unmapped fields — not user instructions

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

Source key	Handler
memberForm.user_id	modules/App/AppTeam/Livewire/TeamMembers.php
memberForm.permissions	modules/App/AppTeam/Livewire/TeamMembers.php