Knowledge Base
Browse the concepts behind Truestamp. Follow the links between concepts, or search across everything.
Tagged: team
10
Glossary
Billing owner
The user who created a team, whose plan plus any administrator overrides sets the effective limits and entitlements for all work done in that team, whichever teammate does it - including the pooled monthly item allowance and member limits counted across every team that person created.
Item visibility
The per-item read scope - private (default; only the item's user-owner plus the owning team's admins and owners), team (any member of the owning team), or public (readable by anyone, including anonymous visitors); visibility controls who can read an item, ownership controls who can change it.
Ownership model
The per-team setting choosing who owns newly submitted items - creator retains (the default; the submitting user owns their items) or team retains (the team owns them; plan-gated, requires each invitee's acknowledgment of ownership terms, and blocks plan downgrades while in effect).
Plan
The account-level tier (Free, Starter, Pro, Enterprise) setting numeric limits (items per month, teams owned, members per team, metadata size, claims-only budget, webhooks, retention, daily chat messages and knowledge-base searches) and named entitlements; the billing owner's plan governs the team.
Team
The unit of tenancy in Truestamp - every item belongs to exactly one team, every signed-in request is evaluated against your identity plus one active team, and team membership is what grants any visibility into a team's items and members.
Team role
The single role each Truestamp team membership carries, in a strict privilege hierarchy - team owner (full control), team admin (team settings plus member and viewer memberships), team member (submits and works with items), team viewer (read-only); roles govern actions, plans govern features.
Teams
Plans, Limits, and Entitlements
The Truestamp plan tiers (free, starter, pro, enterprise), the per-account limits and feature entitlements each tier carries, how usage is counted and enforced, and how an administrator can augment a single account's effective limits and features.
Scope and Tenancy for Teams
How a signed-in user's work is scoped to a team, the team roles (owner, admin, member, viewer) and their rights, the auto-created personal team, active and default team resolution, and plan-based feature gating.