Knowledge Base
Browse the concepts behind Truestamp. Follow the links between concepts, or search across everything.
Tagged: plan
9
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.
Claims-only submission
Submitting an item without an external hash so the claims themselves are the timestamped content of record; requires a description of at least 32 characters or non-empty metadata, and the JCS-encoded claims must fit the team billing owner's per-plan byte budget (256 B Free up to 16 KB Enterprise).
Entitlement
A named Truestamp plan capability that cannot be reduced to a numeric limit, such as team-retained item ownership or the support level (community, email, priority); administrators can grant extra entitlements and limit overrides per account, and every check uses the effective values.
Item retention
The per-plan window a Truestamp item is kept - 90 days on the Free tier (expired items enter the deleted_expired state with an email warning and a 7-day cancellable grace period), unlimited on paid tiers; team-owned items follow the team billing owner's plan.
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.
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.