Skip to main content

Teams

A Team is a cross-functional group with a lead and members. Team members are managed on the team record; there is no standalone Team Member page.

Path: Sidebar ← Organization ← Team
Pages: /Entities/ORG/Team · /Entities/ORG/Team/new · /Entities/ORG/Team/{id}

What a Team does for your business​

  • Groups people for delivery, support, or operations work
  • Names a team lead (ownerUsrId)
  • Maintains member membership on the TeamMembers tab
  • Exposes Insights, Activities, Attachments, and Logs on the record page

Views​

ViewDefault?Purpose
CardsYesCard overview of teams
ListNoTable with filters
Record (Id)—Details and members

List columns​

ColumnMeaning
NameTeam name
ActionsRow actions

List filters​

FilterUse
SearchName search
EntityTypeIdFilter by type
EntityStatusIdFilter by status

Create and edit fields​

FieldRequiredUse
Name (name)Yes (SaveDetails / Id)Display name
Arabic name (nameAr)Yes (SaveDetails / Id)Arabic display name
EntityTypeIdYesEntity type
EntityStatusIdYesEntity status
ownerUsrIdNoTeam lead
DescriptionsNoOptional text
isActiveHeaderActive flag on the record
DataConfidentialityIdHeaderConfidentiality level

Drawer Save schemas require type and status; names are enforced on SaveDetails / Id.

Record tabs​

TabPurpose
DetailsTeam identity, lead, descriptions
TeamMembersMembers list and membership actions

Side panels: Activities, Attachments, Logs, Insights.

Team members (embedded)​

Team members are edited only from the team record. There is no /Entities/ORG/TeamMember docs page or list route.

Member list columns​

ColumnMeaning
memberUsrNameMember display name
ActionsEdit / remove

Member filters​

FilterUse
Search (MemberUsrName)Find a member
EntityType / EntityStatusType and status filters
TeamIdHidden; locked from the parent team

Member fields and rules​

FieldRequiredUse
members[]Yes on add (≥1)Multi-select users to add
memberUsrIdYes on editSingle member user
TeamLockedTaken from the parent team page
Already on the team

Users who are already members are blocked from being added again.

Member actions​

ActionMeaning
AddOpens multi-select for one or more users
EditChanges memberUsrId for a row
DeleteRemoves the membership

Team actions​

ActionMeaning
CreateOpens /Entities/ORG/Team/new
EditDrawer or record edit
DeleteRemoves the team
Open IdOpens /Entities/ORG/Team/{id}

Usage​

  1. Open Teams from Organization
  2. Create a team (navigates to /new) or open an existing {id}
  3. Fill name, nameAr, EntityTypeId, and EntityStatusId
  4. Optionally set the lead (ownerUsrId), descriptions, Active, and DataConfidentialityId
  5. Save, then open the TeamMembers tab
  6. Add members with multi-select; edit or remove as needed
  7. Review Insights / Activities / Attachments / Logs from the record chrome

Best Practices​

Set type and status before inviting members

Required type and status keep the team usable in filters and related modules.

Members stay on the team page

Do not look for a separate Team Member menu item. Membership is always under the team record.

Lead is optional but useful

ownerUsrId is optional in the schema, but assigning a lead clarifies accountability.