Teams
Sites belong to a team, not to a person. Invite whoever needs the numbers, on every plan, with no seat to pay for.
Every site in Peeko is owned by a team, and you are a member of it. That is true even when you are the only person in it: signing up creates your team and puts your sites there.
Team seats are unlimited on every plan, so inviting somebody costs nothing and there is no seat count to manage.
Two roles
| Role | Can |
|---|---|
| Owner | Everything a member can, plus billing, inviting and removing people, deleting a site and rotating a site key. |
| Member | See every site the team tracks, with the same dashboard, and create sites, edit their settings, export, and mint their own API keys. The one setting reserved for an owner is "Count my own visits". |
That is the whole model. There are no per site permissions and no read only seats: a member sees everything the team measures.
Inviting somebody
The Team card on your settings takes an email address and sends an invitation. They join as a member.
The invitation is valid for 48 hours and is a link in an email. Opening it lands on a page with a button, and the join happens when they press it, never when a mail scanner follows the link.
- They already have a Peeko account. Signing in and accepting adds the team to their account. If they are in more than one team, a switcher appears in the sidebar.
- They do not. The same page offers to email them a sign in link fixed to the invited address. Opening it creates the account and lands them back on the invitation. Somebody who joins this way gets no team of their own and no trial, because they already have a team: yours.
An invitation that could not be emailed is withdrawn on the spot, rather than left pending, so nothing is stuck in a state you cannot see. You can also withdraw one yourself, which stops the link working.
Leaving and removing
An owner can remove any member, and access ends immediately, including on a browser that was already signed in. Anybody can leave a team they are in, except the sole owner of it, who has nothing to leave to.
Removing somebody does not touch the data they saw. A team's sites, history, goals and share links belong to the team.
What is not built: there is no way to hand ownership to somebody else, and no way to rename a team from the product. Both are done by hand for now, so ask at the address on the privacy policy if you need one.
API keys and teams
An API key belongs to a person, not to a team. It reaches every site of every team that person belongs to while that team's plan is active, and both things are checked on every single call rather than baked into the key. So joining a second team widens a key by itself, removing somebody closes their key at the same moment it closes their dashboard, and a team whose subscription lapses drops out of every key that reached it until the plan is back.
Keys are made in the API keys card on the same settings page. See MCP for what they open.