Skip to main content

​
Teams, usage, and retention

Every signup receives an isolated personal workspace. Owners can create team workspaces and add existing Screenshotly users as admins or members. API keys belong to a workspace, while the plaintext key is shown only at creation. The workspace owner’s active billing entitlement controls features and monthly quota. Creating additional keys does not multiply throughput or quota. Account Controls lets an owner choose:
  • a warning threshold between 50% and 100%;
  • an optional hard stop below the plan limit;
  • retained-result lifetime between 1 and 30 days; and
  • an optional HTTPS usage webhook.
Warnings are deduplicated per billing month. Notification webhooks use the same durable retry queue as capture-completion webhooks. Deleting application data removes keys, jobs, request history, billing references, and stored capture objects before deleting the local account record; the Clerk identity remains separate and is identified as such in the confirmation flow.