Frequently asked questions

TeamLinkUp is a shared team calendar web app. Create master calendars with color-coded sub-calendars, share secure permission links, invite team members, sync with Google/Apple via iCal, and manage bookings — with strong security defaults.

Yes. Create a free account to own calendars (up to 5 sub-calendars, 5 team seats, standard links, views, and built-in skins). Premium unlocks unlimited sub-calendars, the UI builder and Looks profiles, advanced links, password protection, custom logos, and more.

Viewers of a share link do not. To keep a calendar you create, sign up free — otherwise the homepage makes a 7-day demo that is deleted automatically. The demo includes skins and a try-out of the UI builder. Captcha and per-network limits stop spam.

Premium: a live editor for calendar chrome. Paint top bar, sidebar, canvas and other panes, rearrange layout, save named Looks, and apply them to calendars you manage. Free users keep stock skins and accents only. Saving a profile does not change calendars until you apply it.

Each link is a long random secret in the URL (/c/…). Permissions can be read-only, add-only, or admin. Only a hash of the token is stored in the database, so lost tokens cannot be reconstructed from the server.

Yes — safely. Create an iCal feed under Manage → Sync & backup and subscribe in Google (From URL) or Apple (New Calendar Subscription). That is a separate subscribed calendar in those apps. TeamLinkUp never writes into your existing Google or Apple calendar, so a bad sync cannot fill or wipe it. To copy events into TeamLinkUp, import a .ics file (preview first) or, on Premium, paste their secret iCal URL onto a dedicated Imported layer.

No. We only publish a read-only feed they pull, or we pull their public/secret URL into TeamLinkUp. We do not use Google/Apple write APIs. Imports merge; they never replace a whole calendar. A failed inbound pull leaves existing events in place.

From Manage → Teams & invites, enter their email and role. They receive a link to accept. They can sign up or log in with that email. You can also share a public link without requiring an account.

We use PDO prepared statements (SQL injection protection), CSRF tokens, rate limiting, optional Cloudflare Turnstile, password hashing, optional TOTP 2FA, and security audit logging. Public IDs use UUIDs/hashes rather than sequential integers.

When enabled on a calendar, visitors can open /book/{token} and request a time slot. TeamLinkUp checks for conflicts with existing events and notifies the calendar owner.

Use a read share token with the embed URL: /embed/{token}. Copy the iframe snippet from Manage → Booking & embed.

That usually means the share link is invalid, revoked, or your account does not have team permission. Open the calendar from Dashboard → Open (for calendars you own or were invited to), or create a new share link under Manage → Share links. This is an app permission check, not always a server file permission issue.

Use the Contact page for bug reports and questions. Messages are delivered to our support address with anti-bot protections (CSRF, captcha, honeypot, rate limits).