Skip to content
TipPage Docs
Esc
navigateopen⌘Jpreview
On this page

Accounts, teams and platforms

How TipPage is put together - tenants, users and their sign-in accounts, connected channels - and what "both Twitch and Kick" means feature by feature and in the API.

TipPage works with Twitch and Kick, and one streamer can use both at once. To make sense of the settings - and of the ids you see in the API - it helps to know that there are three separate things, and none of them is “your Twitch account”:

  • Your TipPage - the thing you created at signup. It owns your tip page, overlays, queues, chat bot, settings, tip history and team. There is one per streamer.
  • People - everyone who can sign in to a TipPage: you, and any team members you add. Each person is one TipPage user with one or more sign-in accounts (a Twitch account, a Kick account, or both).
  • Channels - the platform channels your TipPage streams on. TipPage reads chat and events from a channel and posts there as the bot. A TipPage can have a Twitch channel, a Kick channel, or both.

Keeping these apart is what lets you sign up with Kick and add Twitch later, sign in with whichever account is handy, or run a two-platform stream from one dashboard.

Your TipPage

A TipPage has exactly one owner - the person who created it - and any number of team members. The owner is the only one who can manage members, payments and the platform connections. Everything else is granted per member with permissions.

The tip page, overlays and queues belong to the TipPage, not to a platform. A tip is a tip whether the viewer found you on Twitch or Kick; the same overlay plays alerts from both.

People and sign-in accounts

When you sign up or accept an invite, TipPage creates a user for you and links the account you used. That user is what a TipPage remembers: the owner, a team member’s permissions, who approved a refund, who created an API key - all of it points at the person, not at a Twitch id.

  • Link another account in Settings -> Platforms. With Twitch and Kick both linked you can sign in with either and land in the same place.
  • A platform account can be linked to one TipPage user. If the account is already someone else’s, the link is refused - accounts are never merged.
  • You can’t unlink your last account, because then you couldn’t sign in.
  • One person can be on more than one TipPage: owner of their own, team member on a friend’s. Switch between them from the account menu in the dashboard header.

Channels

Settings -> Platforms is where channels are connected. Each row is one platform: the channel this TipPage streams on there, and the account you sign in with there.

  • A channel belongs to one TipPage. If a channel is already connected somewhere else, connecting it is refused.
  • Connecting a channel means authorising TipPage with the account that owns it, so that account is also linked as a sign-in account for you.
  • Disconnecting a channel stops alerts, chat commands and the bot for that platform. Tips, history and settings are kept, and you can still sign in with the account. A TipPage needs at least one channel, so the last one can’t be disconnected.
  • “Needs reconnect” means the platform revoked or expired TipPage’s permissions - click through to authorise again and everything resumes.

The owner connects channels. Team members link their own sign-in accounts, but linking never connects a channel.

What “both platforms” means, feature by feature

Where a feature exists on both platforms it is one setting that applies to both. Where a feature only exists on one, TipPage says so rather than pretending.

Area Twitch Kick
Alerts Follows, subs, gift subs, resubs, cheers, raids, channel points Follows, subs, gift subs, renewals, Kicks
Alert box Same rows for both. Per box you can turn a platform off, and switch on a platform badge. Kick subs have no tiers.
Chat widget Twitch, Kick, or both in one box, from your linked channels. Each platform’s own badges and emotes; a platform mark per message when showing both.
Goal, viewer count, total-followers label Both (added together), Twitch, or Kick per widget. Kick publishes no sub count, so sub figures are Twitch’s.
Activity feed, celebration, emote rain, custom widgets Events from both platforms; custom-widget events carry platform.
Chat announcements Post in the chat the event came from, with the same template. Tips post in every connected chat.
Chat bot On/off per platform. Appears as TipPageBot, or your custom bot account (TipPage+) On/off per platform. Appears as TipPage - no custom bot accounts yet
Chat bot commands Work in both chats. Each command and timer has a platform switch (shown once both are connected).
Variables Everything Everything except {accountage}, {emote}, {emotes} and the {user.*} stats, which render empty on Kick for now. {followage} works best-effort. {uptime}, {title}, {game} and {viewers} read the channel the message came from, or any channel you name ({viewers:kick}, {game:twitch:somebody})
Chat moderation, !permit Yes Not yet
Timers’ live check Yes Yes
Timers’ chat-activity minimum Yes Counts Twitch chat only; not applied on a Kick-only TipPage
Stream info (title, category) Yes Not yet
Sub rewards (free message credits) Yes Not yet
Tip page viewer sign-in Twitch Not yet

In the API the same split shows as ids and fields: a TipPage is the t_... tenant id every key belongs to, a person is a u_... user id (the actor on events carries it, plus the platform account they acted through), and channels appear as platform on payloads - alerts are twitch.* and kick.* events, chat events carry platform, and POST /v1/chat/messages can be told which chat to speak in. See the webhooks catalog and realtime groups.

Teams in practice

  • The Members page is owner-only. Members join through a single-use invite link or the quick-add from your Twitch mods.
  • Invites are accepted with a Twitch account today. Once someone is in, they can link their Kick account under Settings -> Platforms and sign in with either from then on.
  • Super Admin members can do everything except the owner-only things above. See Permissions.

Was this page helpful?