With Teamup calendar, administrators can create and maintain sub-calendars and manage calendar access through shareable links or account-based access. This article discusses how administrators can create sub-calendars and calendar links in bulk by importing CSV files.
The Settings in a Teamup calendar allow calendar administrators to create and maintain sub-calendars and manage calendar access through calendar links or through account-based users and groups.
In some exceptional use cases, you may need to create a very large number of sub-calendars or calendar links. You can import sub-calendars and access links from CSV files to make the process more efficient. You will need some familiarity working with the CSV file format.
How to import a CSV file
The bulk import of sub-calendars and calendar access links is available from the Import Events page of the calendar settings. Look for the links to the bulk import in the introductory text at the top of that page.
Follow the steps below to proceed:
- Open the calendar in a web browser with your administrator link
- Go to Settings > Import Events
- Select either bulk import of sub-calendars or bulk import of calendar link from the intro text. See screenshot below.
- Select File to import (more details on required file formats below).
- Click Save to start the import process.
Bulk import of sub-calendars
This section explains the format required to import sub-calendars from a CSV file.
Example: CSV file to import sub-calendars
Calendar Name, Color Id, Allow Overlap, Feed URL, Refresh Interval
Conf. Room Newton, 25, true
Conf. Room Thales, 17, true
AUS Holidays, 23, true, https://calendar.google.com/calendar/ical/en.australian%23holiday%40group.v.calendar.google.com/public/basic.ics, 7dLine 1 is a header line and defines all the columns of this file: Calendar Name, Color Id, Allow Overlap, Feed URL and Refresh Interval. The header line must be present in the file exactly as shown in the above example. Each additional line below the header line defines a sub-calendar.
If the name of an imported sub-calendar matches the name of an existing sub-calendar, the existing sub-calendar is updated rather than a new sub-calendar being created.
Supported fields
The following table defines the supported field names and the format of the field values.
| Field Name | Required? | Description |
| Calendar Name | Yes | Name of the sub-calendar. Up to 100 characters. |
| Color Id | Yes | ID of color assigned to sub-calendar. All supported colors are defined in the API documentation. |
| Allow Overlap | No | Supported values are true or false. This defines if the sub-calendar allows overlapping events or not. |
| Feed URL | No | If a URL is provided, a read-only sub-calendar is created that is periodically updated from the specified feed URL. |
| Refresh Interval | No | This parameter applies only if a feed URL has been provided. It defines the refresh interval. Supported values are 30d, 7d, 12h, 4h, 1h and 15m. Please note that the supported refresh intervals depend on the subscribed plan. |
Bulk import of calendar links
This section explains the format required to import calendar access links from a CSV file.
Example: CSV file to import calendar links
Link Name, Password, Calendars Shared, Permissions
Admin, SecretAdminPassword, all, 0
Reception, , all, 1
Sarah, , selected, "Conf. Room Newton=1, Conf. Room Thales=2"
Frank, , selected, Auditorium=1;Line 1 is a header line and defines all the columns of this file. This line must be present in the file exactly as shown in the example above. Each additional line below the header line defines a calendar link.
If the name of an imported link matches the name of an existing link, the existing link is updated rather than a new link being created.
Supported fields
The following table defines the supported field names and the format of the field values.
| Field Name | Required? | Description |
| Link Name | Yes | Name of link. Up to 100 characters. |
| Password | No | A password is optional. If a value is provided for this field, a password check is activated for this link. |
| Calendards Shared | Yes | This field defines if all or only selected sub-calendars are accessible through this link. Supported values are all and selected. |
| Permissions | Yes | The value of the permission field depends on how field Calendars Shared is configured. If field Calendars Shared is set to all, then this column takes an integer that defines the permission that is granted to all sub-calendars. The following permission values are supported: 0 : Administrator 1 : Modify 2 : Read-only 3 : Read-only, no details 4 : Add-only 5 : Add-only, no details 6 : Modify from same link 7 : Modify from same link, no details If field Calendars Shared is set to selected, then this column takes a list of name=value pairs separated by commas. The name is equal to the name of an existing sub-calendar. The value is a permission value as defined below: 1 : Modify 2 : Read-only 3 : Read-only, no details 4 : Add-only 5 : Add-only, no details 6 : Modify from same link 7 : Modify from same link, no details |
Examples
Let’s have a closer look at the example file given above.
Link Name, Password, Calendars Shared, Permissions
Admin, SecretAdminPassword, all, 0
Reception, , all, 1
Sarah, , selected, "Conf. Room Newton=1, Conf. Room Thales=2"
Frank, , selected, Auditorium=1;- Line 1 is a header line and must be copied as shown above.
- On line 2, a link named “Admin” is assigned administration permission to the calendar. A password is enabled and set to the value “SecretAdminPassword.”
- On line 3, a link named “Reception” is assigned modify permission to all sub-calendars.
- On line 4, a link named “Sarah” is assigned modify permission to sub-calendar “Conf. Room Newton” and read-only permission to sub-calendar “Conf. Room Thales.”
- On line 5, a link named “Frank” is assigned modify permission to sub-calendar “Auditorium.”