Feature overview
Custom Forms let template owners collect any combination of Text, Choice or Number inputs before the team is created. Answers can be reused in naming conventions, group email aliases, descriptions, and welcome messages, ensuring every new workspace starts with the right context. On the Deal Room template shown on page 2 you can see three sample fields: Opportunity Name, Opportunity Type and Customer Name. Custom form and metadata
Typical use‑case
Scenario:
Project Teams want to capture Project data such Project type, Location, Name, reference number, etc. Or in a Sales scenario, Sales Ops wants every new Deal Room to capture Deal Size (Number), Opportunity Stage (Choice) and Primary Competitor (Text).
Outcome:
The fields populate the metadata and include this in the team name, description or welcome messagee for example
PRJ‑ [Project Type] - [Customer Name]Deal‑ [Opportunity Type] - [Opportunity Name].
Step‑by‑step
Open the template → Form tab → toggle Enable custom form (see page 1). Custom form and metadata
Add or import fields
Drag T, #, or Choice blocks.
Import pulls an identical definition (label, help text, validation) from any existing template to stay consistent.
Re‑order by dragging the six‑dot handle – end‑users will see the same order in the request form.
(Optional) Add default values or tooltips to cut down on user mistakes.
Update naming – insert any field into:
Team name / M365 group email
Description / Welcome message (page 3). Custom form and metadata
Save the template and test it with Preview as requester.
How Custom Forms and Metadata work together
Behind the scenes, every field you add to the Custom Form is automatically registered as a metadata type for your organization.
When the requester fills in the form:
A value is written to the team as metadata (e.g., Opportunity Stage = Qualification).
The same value appears as a coloured pill on the team card, is searchable and filterable in My Teams, and can be bulk‑edited later from the Bulk module.
If you connect the template to nFlow, the metadata key created by the form is reused—nFlow simply updates the value from external systems such as Salesforce rather than creating a duplicate field.
Example: The Project Type (Choice) you capture at creation is stored as metadata; Manager can later pick the project type they want to display the corresponding teams.