A Team field assigns a record to a team instead of a person. Think of a ticket routed to a department's queue.

Here is the test: does a group own this record, and should every member of the group be able to work on it? If yes, you want a Team field. For a named person, use an Assigned To field. Pair the two when one person inside the team takes the work on.

Example: a Controls table with a field called Owning Team. Each control belongs to the team that operates it, such as IT Operations or Finance. Every member of that team can update the control, and a My Team view shows each person their team's controls.

The Owning Team field in a control record, showing the IT Operations team as an avatar and name chip.

The field settings panel opens. It has two tabs: Settings and Help Text. The rest of this article takes them in that order. Save at any point with Add Field (or Update Field on a field that already exists) and come back to the other tab later.

The field settings panel, Settings tab, with Display Format, Number of Entries Allowed and the two Options switches.

The Settings tab holds how the team is shown, how many a record can hold and two rules. Top to bottom: Display Format, Number of Entries Allowed and Options.

How the assigned team looks in a record and in views.

Use Avatar Only in a crowded grid where the team avatars are known; use Avatar and Name everywhere else.

Owning Team is Single. One team operates a control, so the audit trail names one team. Use Multiple where ownership is shared, such as a SOX control owned by both Finance and IT.

Two switches, both off to start. Each one is a rule for the people who fill in records.

Require an entry in this field. On, a record cannot be saved until at least one team is set. Turn it on when every control must have an owning team from the day it is created.

Disable assignment notifications. On, setting or changing the team sends no notification from this field. Leave it off for routed work, where the notice is the point. With notifications on, every member of the team gets an in-app notification. The email goes to the team's Team Email if a Workspace Administrator has set one, otherwise to every member. Bulk updates send no per-record notifications.

A note for the person filling in the record, up to 800 characters. Help Text Appearance shows it As A Tooltip (the default, behind an info icon next to the field name) or Below The Field Name (always visible).

Write it for someone who has never seen the field. For Owning Team: "The team that operates this control. Pick the team, not the person; the Control Owner field names the person."

Three things apply to this field.

Field Permissions. Every field can carry its own permissions, which control who can see the field and who can edit it. Open the column menu and select Edit Field Permissions. Let the compliance lead set Owning Team while everyone else reads it. A member who cannot see the field still gets the access their team grants (below); only the value stays hidden. See Field Permissions.

Team-mediated access. Setting a team on a record gives that team's members access to the record, by the team's permission on the table. A team with Contributor permission can edit the records assigned to it. A team with Assignee permission can view and edit them. Assignee+ does not work with a Team field; it works with an Assigned To field only. When a member reaches a record through more than one path, such as two teams, or a team and an Assigned To field, the highest permission wins. A member of a Viewer team and an Editor team works as an Editor. See Table Permissions.

Dynamic Record Permissions. A Team field can drive record-level rules: who can see or edit a record based on the team it holds. A rule such as "records whose Owning Team is my team are editable by me" uses the field as the condition. Every field type except Button can drive a rule. See Dynamic Record Permissions.

Once teams are set, the field answers "whose queue is this?" across the table.

In a record or a grid cell, open the picker and pick a team. The picker offers only teams that have access to the table, never the Everyone team, and a search box appears when more than five teams are available. Only Workspace Administrators create teams, so a team missing from the list needs table access first. A deleted or inactive team stays on the records that held it but cannot be picked again.

An Assigned To field in the same table can use Owning Team as its Parent Team Field. Its picker then offers only members of the team set on the record. With no team set, it offers everyone with table access. Changing the team updates the picker at once but does not change a person already set. See Assigned To Field.

The team picker open on a control record, listing the teams with access to the Controls table.

The operators are has any of, has all of, is exactly, has none of, is empty, is not empty, contains and does not contain. The value list offers the teams with access to the table and the teams already set in the table. It also offers My Team, which stands for the current member's teams when the view opens. "Owning Team is exactly My Team" is one view that works for every member. With Multiple on, "has any of My Team" matches a record that holds any of the member's teams. "Has all of My Team" matches only when the record holds all of them.

Group a view by the field and each team becomes a group with its controls under it. In Kanban View each team becomes a column. See Kanban View.

Sort A → Z or Z → A from the column menu, so controls order by their team's name.

The field works in Lookup fields and in their filters, and in Auto-Generated Titles. Document Designer can place the team in a generated document.

A formula reads a Single field as the team's name and a Multiple field as a list of names. This one marks the controls in SOX scope:

Automations treat the field like Assigned To. An action can set the team from any text source: a team name, a lookup, a formula or a fixed value. A team without access to the table is skipped, and the skip is recorded in the run history. An action can also fill an Assigned To field from the team: every member for a Multiple field, the first member for a Single one. Send Email goes to the Team Email when set, otherwise to each member. Send Notification reaches every member. A loop over the field runs an action per member. A comment cannot be assigned to a team; use Assigned To for that. See Automation Actions explained.

Bulk Update, import and copy-paste set the field the same way, by team name, and skip teams without table access. The field is in the public API with the same structure as Assigned To.

A Team field can be placed on a form where the feature is enabled for the workspace; the form builder lists the field only then. See Form View.

Change the team on one record. Open the picker in the record and pick another team. The new team is notified unless notifications are off.

Allow more than one team. Open Modify Field Settings, set Number of Entries Allowed to Multiple, then Update Field. Existing single teams stay.

Stop the notifications. Turn on Disable assignment notifications and select Update Field. It applies to this field only.

Change the field type. The type cannot be changed after the field is created. To hold the same information another way, add a new field.

Need more help? Ask the SmartSuite Community, where builders, administrators and the SmartSuite team answer questions about building on SmartSuite. For your account, billing or data, select the chat button in the lower-right corner of SmartSuite to reach support.

Last verified 1 Nov 2026.