About event fields
On typical calendars, when you create an event you can also fill in fields like Who, Where, and Description.
With Teamup, you get so much more:
- More control and flexibility with configurable default event fields.
- Special-use event fields like signups and comments.
- Three event fields to upload images and files.
- The ability to create your own custom event fields.
Default event fields
These are the event fields that come built-in with Teamup:
- Title
- Calendar
- Who
- Where
- Description
- Signup
- Comments
- Attachments
The default event fields can be configured in various ways.
Configure event fields
Calendar administrators can configure the default event fields:
- Open Teamup in a browser.
- Go to Settings > Event Fields.
- This section lists the event fields. If you add custom fields to your calendar, they will also appear in this list.
- To configure an event field, click the pencil icon beside the field name.
- To rearrange event fields, use the arrows to move any field up or down in the order.
- To deactivate an event field, click the toggle next to the field name.
- Note that deactivated fields are hidden from the list by default. To view deactivated fields, check Show deactivated fields at the top of the list.
What you can do with the built-in event fields:
Rename the field
If this is left blank, the field will display its default name (e.g. Who).
Make a field required
If this option is chosen, an event cannot be created or edited without that field being completed
Deactivate the field
This will completely hide the field from all existing and future events. If you would like the field to still show up on old events where it was filled in, you can uncheck Hide from existing events. You can also deactivate the field from the field list.
Show in event titles
If enabled, the contents of the field will be shown in brackets next to the event title.
Defaults and limitations
Some fields have additional defaults to be configured, such as Signups and Comments. There are also limitations on configuration for a few fields.
→ See how to configure event fields for more details.
Custom event fields
Teamup supports three types of custom event fields: text fields, number fields, and choice fields. The number of custom fields you can create varies by pricing plan.
- Single-line text fields: Enter a single line of text. These look and feel much like the Who and Where fields.
- Choice fields: Select from a list of prefilled options. These look and feel similar to the Calendar field.
- Number fields: Enter numerical values and get the sum in the Table view.
Important: When you create a custom field, think carefully about which type is best. You cannot change a custom field type once the field has been created. If you made an error, you will need to delete it and start over again.
Single-line text fields
- To create a single-line text field, click the New Field button above the field list.
- Then, enter a name for your field and select Single-line text option under Type.
Choice fields
- To create a choice field with options, click the New Field button above the field list.
- Then, enter a name for your field, and choose the Choices option under Type.
- Next, you should decide whether you want to make a single-choice or a multiple-choice field.
- A single-choice field lets only one option be selected at a time. You can use this if it does not make sense for a user to be able to choose multiple options. For example, a Status field might be one of Planning, In progress or Completed, but it would not make sense for it to be both In progress and Completed at the same time.
- A multiple-choice field lets more than one option be selected. You can use this where more than one option might apply. For example, a meeting might be attended by multiple people at once, or a film might be multiple genres at once.
- Now you can add your options. You can optionally click the colored dot next to an option to change its color, and choose an emoji for the option which can be displayed in the event title:
Save, and refresh your calendar. Now anyone who can modify the calendar will be able to make the choice and viewers will be able to see the chosen option:
Choice field options
The number of options you can add to a custom field depends on your subscription level. See our pricing page for details.
- To the right of each option are arrows to rearrange options as needed.
- To the left of each option is a toggle that lets you deactivate it.
- If an option is deactivated, it is hidden and cannot be selected on new events. However, it will still appear on existing events where it was previously selected, unless you check the “Hide” box.
Number fields
On the Create Custom Field page, select Number then configure the basic settings:
Configure the prefix or postfix for the number, for example, $100 or 100 kg. The other settings are as explained
The value of a number field is displayed on all calendar views as a custom field similar to a custom text field or choice field. Noteworthy is in the Table view, where each field is displayed in its own column, and for the number field, the sum of the column is displayed in an extra row in the bottom.
Deactivate or delete a custom field
- To deactivate a custom field, go to Settings > Event Fields, find the custom field in the list, and switch the toggle button to red (off):Deactivated fields can be reactivated, and their data is not lost.
- To delete a custom field, go to Settings > Event Fields, find the custom field in the list, and click the Pencil icon to edit the field. Click the Delete button next to the Save and Cancel buttons.
This will permanently delete the field and any information it contains from all your calendar’s events.
Make a custom field required
- To make a custom field required, go to Settings > Event Fields, find the custom field in the list, and click the Pencil icon to edit the field. Scroll down to the Required section and check Yes.
- If a field is marked as required, then an event cannot be created or edited unless that field is completed. This is useful if there is important information that must be available on all events, but users may forget to fill in.
- Be aware that making a field required would require the field to be filled in when you modify an event that was created earlier.