Feeds, and the sub-calendar question

Teamup exposes iCalendar feeds, and the useful detail is that you can have one for the whole calendar or one per sub-calendar. That choice decides how your website is organised, so make it deliberately.

If your sub-calendars are meaningful categories — Studio A, Studio B, Private hire — then separate feeds map cleanly onto separate categories on your site, and you can list one studio's schedule on its own page. If they are just colours for the staff's benefit, one combined feed is simpler.

Where Teamup differs from Google or Outlook is that the sub-calendar structure is the point of the product, and a website that flattens it away usually loses something the venue cares about.

Why the embed is the wrong default

Teamup's embed is genuinely good — interactive, filterable, and it looks like Teamup. That is the problem on a public page: it looks like Teamup rather than like your venue, the events are invisible to search engines, and a visitor on a phone gets a scrolling frame inside a scrolling page.

Feeds give you the same events as pages on your own site, in your own design, indexable, and available to the rest of WordPress. The embed remains the right answer for an internal staff page where none of that matters.

Access links and what they let through

Teamup's access is built on links with different permission levels, and the calendar feed inherits from the link you generate it against. Generate the feed from a read-only link, and generate it from one restricted to the sub-calendars you actually want public. A feed made from an administrator link is a much larger secret than it needs to be.

If a link is later revoked, the feed stops working. That is correct behaviour, but it means your website's sync can be broken by someone tidying up access in Teamup without realising the site depended on it. Worth a note wherever your team documents things.

What comes across

Titles, times, recurrence, and location and description as text. What does not come across is anything Teamup-specific — custom fields, signup counts, attachments, and the sub-calendar colour. If your listings need those, the feed is the wrong mechanism and you should be looking at Teamup's API.

For most venues the feed carries everything the public page shows, which is why it is worth trying first.