klixly
Back to help

Teams: working on pages and posts together

With a team you work together on bio pages and the Content Planner. Teams are part of the Business plan. Only the team owner needs the plan, members sign in with a free klixly account.

Setting up and joining a team

With the Business plan you'll find your team under “Team” in the sidebar. That's where you invite members by email. An invitation is valid for 7 days and can only be accepted with the account it was sent to. Everyone can be in one team only: anyone who is already a member of another team, or owns a team with members or team pages, can't join.

How many members

On the Business plan you can invite up to 10 members in addition to yourself, and open invitations count towards that. The owner and admins manage members and roles. Invited members don't need a plan of their own; inside the team the owner's features apply.

Roles and custom roles

Every member gets a role. The permissions apply to all of the team's pages and to the Content Planner:

  • Owner: everything, including billing, deleting team pages and payment or calendar connections.
  • Admin: edit and manage pages (custom domain, team sharing), the full planner, members, legal templates and the activity log.
  • Editor: edit pages, write posts, view statistics.
  • Viewer: view statistics only.

If the fixed roles aren't enough, create up to 5 roles with hand-picked permissions under “Custom roles”, optionally starting from a fixed role as a template. Viewing is always included, while deleting pages and payment or calendar connections stay reserved for the owner. You can't assign a role with permissions you don't have yourself.

Approvals in the Content Planner

Under “Settings” in the team you can require that posts by editors are approved before they're published. Anyone with approval rights approves the post or sends it back with a note. Per brand you can also switch on that the client then confirms every post via a link, without a klixly account of their own.

Team pages and shared pages

A page gets into the team in one of two ways:

  • Team page: you create it for the team directly via “Create new page”. It belongs to the team, stays when someone leaves and counts towards the team page limit (25 on the Business plan).
  • Shared page: someone shares one of their own pages with the team under “Team” in its settings. It stays their page and counts towards their own page limit. The team can edit it, but can't delete it or touch payment or calendar connections. Sharing can be ended at any time.

Under “Pages” you see every page you have access to, with tags and warnings, for example about a missing legal notice or a domain that isn't active yet.

Legal templates for legal notice and privacy policy

Under “Legal templates” you maintain your legal notice and privacy policy as templates, up to 20 per team. Each page fills placeholders in double curly braces from its own legal notice fields. These placeholders are available:

  • {{name}} and {{anschrift}} (street, postcode, city and country combined)
  • {{strasse}}, {{plz}}, {{ort}} and {{land}} individually
  • {{email}}, {{telefon}} and {{ust_id}}
  • {{vertreten}}, {{register}} and {{zusatz}}

If a page is missing a value, that spot stays empty, and lines containing only an empty placeholder are dropped. Which template a page uses is chosen in its settings under “Legal template”. The text becomes visible once the legal notice or privacy policy is switched on there. Changes to a template apply immediately to every page using it. klixly doesn't write or review legal texts; you bring your own.

Integrations: Stripe and calendars

Under “Integrations” the team owner connects Stripe accounts and calendars (Calendly and meetergo) for the team, for example one per client, and sets a default. Team pages use the default unless you assign them a different connection.

Shared pages use their owner's accounts. A team connection only applies there once both sides have agreed: if the team proposes it, the page owner confirms. If the page owner requests it, the team owner agrees. Until then it shows as pending in the overview.

Activity log

The activity log records who invited members, changed roles, created, shared or transferred pages, approved posts and changed connections. Only metadata is stored, never the content of posts or legal texts. You can filter by area, page, person and period. Anyone with the “View activity log” permission can see it. How long entries are kept is shown in the log itself.

Two-factor sign-in for everyone

Under “Settings” in the team, the owner can require all members to protect their sign-in with two factors, via an authenticator app or a passkey. The owner needs to have set this up first. Members without 2FA lose access to the team's pages and planner until they've set up one of the two. Invitations can then only be accepted with 2FA.

Leaving the team or removing members

Members can leave the team at any time, and the owner and admins can remove members. Whoever leaves loses access to the team's pages and planner, while their own pages stay. If they had shared pages of their own with the team, those are detached: the team loses access, the team's legal templates and connections no longer apply to them, and they use their own text and accounts again. The owner can't leave their own team.

Transferring ownership

Under “Ownership” you hand the team over to an active member whose plan includes teams, meaning the Business plan. You confirm with your password; if your account doesn't have one, set one under “Account” first. Afterwards the new owner's limits apply: pages and members above the limit go offline or lose access, nothing is deleted. You stay in the team as an admin. The team's Stripe account and calendars are disconnected, and the new owner connects their own.

Handing over individual pages

When the collaboration with a creator ends, you transfer their page to their own account. How that works and what moves along is explained in the “Transferring a page” guide.