Applications

Identity and availability

Setting	What it does
Status	Active serves normally. Maintenance refuses with APP_PAUSED. Disabled refuses with APP_DISABLED.
Message shown to clients	Returned over the encrypted channel when paused or disabled, so your loader can display a reason.
Client version	The build string your loader reports.
Reject stale client versions	When on, a mismatch is refused with VERSION_MISMATCH.
Update URL and message	Sent alongside VERSION_MISMATCH so the loader can self update.

Sessions and rate limits

Setting	What it does
Concurrent sessions per key	The main anti sharing control. 1 means one machine at a time. 0 disables the check.
When the limit is reached	Either refuse the new session, or close the oldest one. Closing the oldest is friendlier for customers who crash a lot.
Session lifetime	Seconds, refreshed on every heartbeat. Shorter means a ban bites sooner.
Clock tolerance	How far a client clock may drift before CLOCK_SKEW. Do not widen this to paper over a broken clock.
Requests per minute per IP	Coarse abuse protection. Failed logins have their own stricter counter.
Accept client log messages	Lets clients write into your activity log.
Allow client initiated bans	Off by default, and it should stay off. A tampered client can ban its own key.

File delivery and transport

Setting	What it does
Chunk size	Bytes per encrypted chunk, applied to future uploads only.
Inline delivery limit	Files at or below this ride along with the login response. See releases.
Encrypt stored files	Leave on. Each chunk gets its own tag bound to its index.
Server public key pin	SHA-256 of the SubjectPublicKeyInfo, 64 hex characters. The SDK then refuses any other certificate. Requires HTTPS.

Application resellers

The owner assigns a reseller from the application's Resellers page by entering the email address of an existing active seller account. Email matching is case insensitive. The assignment does not create an account or send an invitation, and administrators, suspended accounts and the application owner cannot be assigned. Each assignment and every permission below applies to this application only.

Permission	Effect
Create keys	Issue single keys and batches only from the key types the owner selected and that are still on sale. Normal test-key and batch rules still apply.
Ban keys	Ban and restore keys inside the reseller's current key scope.
Delete keys	Remove access to keys inside the reseller's current scope. A reseller action revokes the key and preserves its history; only an owner or administrator hard deletes it.
Manage every key	Expands the reseller's scope from their own keys to keys created by the owner and every other reseller. It does not grant create, ban or delete by itself.

Without Manage every key, key pages, batches, reveals, exports and actions are scoped to created_by, so the reseller sees only keys they issued. Allowed key types limit creation; they do not widen visibility or action scope.

The owner retains the reseller dashboard: key totals, pending and activated counts, test keys, month/all-time revenue, write-offs, recent keys and application-scoped audit entries. Disabling access takes effect immediately while preserving keys, revenue and audit history. Resellers receive no access to application settings or secret, SDK downloads, releases, files, variables, blacklist, sessions or the owner's revenue and activity pages.

Danger zone

Rotate the application secret when a binary leaks. Every existing build stops authenticating immediately, so you must ship a rebuilt loader at the same time. Both this and deletion require typing the application name, because neither can be undone.

Deleting an application removes its keys, devices, sessions, releases, files, variables, blacklist and logs.