Teams
Who owns what, the two roles, and how invitations work.
Every account is a team, including a team of one. The team owns the projects, the monitors and their history — not the person who created them. That is what lets a colleague pick up a monitor when the person who set it up is asleep, and why alerts go to everyone rather than to an owner.
Roles
| Role | Shown as | Can |
|---|---|---|
admin | Admin | Everything, including team settings, billing, and inviting or removing members. |
member | User | Work with projects and monitors. |
The role lives on the membership rather than on the person, so it describes a relationship to this team.
The team's owner is always an admin, and cannot be demoted or removed. Billing belongs to them.
Inviting people
Invite by email address from the team settings. The invitation is a link; accepting it joins that team.
One account belongs to one team. An email address that already has a Rippler account cannot be invited into another team — the invitation is refused, and says so, rather than appearing to work and silently doing nothing. Someone who needs to move teams needs a different address, or their existing account removed first.
Alert emails are personal
Whether a person receives alert emails is a setting on their own profile, not something an admin sets for them. Switching it off stops their delivery and changes nothing else about what the team alerts on.
The members list shows who has alerts off, so it stays visible when a team has quietly stopped receiving anything.
API tokens
Tokens are personal, and created under Account → API. A token resolves to the team the person belongs to, which is why no API path carries a team id. Anything a member can do in the app, their token can do through the HTTP API.
Revoking a person's access removes their token's reach with it.
Plans and allowances
| Plan | Monitors | Price |
|---|---|---|
| Indie | 10 | Free |
| Business | 100 | $25 a month |
The allowance is a limit on creating monitors, and only that. A team that downgrades or lapses while holding a hundred monitors keeps watching all hundred — it simply cannot add another until it is back under the allowance. Quietly stopping the monitoring somebody depends on, to make a billing point, is the one failure this product should not have.