Plans and Share Allowance

Every plan caps how many shares you may create in a period. This page covers the numbers, the counting rules, and the options once the allowance is spent.

The allowance by plan

Annual plans carry the same figure as their monthly equivalent: Solo Yearly is 50 shares a month, not 600 a year.

The two windows

The two windows behave differently, and which one applies depends only on whether you are on the Free plan.

Free — a calendar day, in UTC. The count covers shares created between 00:00:00 and 23:59:59 UTC. It resets at UTC midnight, not at midnight in your own timezone, so if you are west of UTC your allowance refreshes during your working afternoon or evening.

Paid plans — a billing month, anchored to your renewal day. The window runs from your renewal day-of-month to the same day of the following month. If your subscription renews on the 17th, the allowance resets on the 17th. It is not the first of the month. This holds on annual plans too: the allowance still resets monthly, on the day-of-month your subscription renews.

What counts against it

The allowance counts shares created in the window, not shares that currently exist. That distinction is where most of the surprises live.

• Expired shares still count. A share that has reached its expiry, or burnt through its view limit, remains in the tally for the rest of the window.
• Ending a share early still counts. The delete action on an active share is labelled Expire & scrub: the encrypted contents are destroyed, but the record stays in your Expired list and it does not return to the allowance.
• Credentials submitted into a Secure Request count against the request owner, not the person submitting. If you send a request to ten suppliers and all ten reply, that is ten shares off your allowance.
• Team shares draw on the team owner's pool. When a share is attributed to a team, the allowance checked is the one belonging to the account that owns that team, and every member's shares come out of the same pool. A seat member's own personal shares are a separate matter: those are judged on the member's own account, which without a subscription of its own is the Free allowance.
• The API and the dashboard share one pool. There is no separate API quota — see Errors and rate limits.
• Shares created through the Slack app count against the account the Slack user is linked to.

What does not count

Anonymous pastes are exempt. A paste created on the public SecurePaste tool is not attributed to any account and does not touch anyone's allowance — not even if you are signed in to CredenShare in another tab, because that tool deliberately does not attach your session. A paste created from SecurePaste inside the app, where you are signed in, counts like any other share.

Seeing what is left

Two places in the app show where you stand:

• The Your Plan card on the dashboard shows Shares used as a count of shares created against your total, with a usage bar. Between one and three remaining it adds a line of the form Only 3 shares remaining; at zero it shows Share limit reached — upgrade your plan.
• Account → Subscription shows what is left, under Current Plan, as N shares remaining. On an unlimited plan it reads Unlimited shares instead.

Both numbers include any add-on shares you hold.

When the allowance runs out

Creating a share is refused. In the app you get a toast titled Share Limit Reached:

You have used all available shares. Purchase more to continue.

It carries a Buy More Shares button that takes you straight to the add-on packs.

Through the API the same refusal is an HTTP 403 carrying error code 61:

{
  "success": false,
  "message": "You have reached limit of your share creation.",
  "error_code": 61
}

Nothing already created is affected. Existing shares stay live and openable; only new creates are blocked.

You have three options: wait for the window to reset, buy an add-on pack, or upgrade.

Add-on share packs

Extra shares can be bought as a one-off pack, on any plan below Enterprise and Free included, without changing your subscription. Go to Account → Subscription, then the Buy More Shares tab beside Annual and Monthly.

Payment is by card. Packs are not offered on Enterprise, which has no share limit to raise.

How they behave:

• Pack shares are drawn only after your plan's own allowance is spent. They are held in reserve rather than merged into the monthly figure, so a pack bought early in the month sits untouched until the plan allowance reaches zero.
• A pack lasts one month from the moment you buy it, not to the end of your billing period. Unused shares in a pack lapse when it reaches that date.
• Packs stack. Buying two adds both to your reserve, and the balance shown in the app is the plan allowance plus everything unused across your packs.
• Buy on the account that owns the team. On a team, the allowance that gets checked is the owner's, so a pack bought by a seat member does not raise the team's ceiling.

Upgrading

Upgrading raises the ceiling for the current window as well as future ones. Choose a plan under Account → Subscription; the Annual and Monthly toggles show the same plans priced each way.

Two things worth knowing before you pick:

• Share allowance is not the only thing that scales. Access-log retention, seats, secure requests, field templates, API access and the Slack integration are all tied to the plan — see Plans and limits for the value of every entitlement on every tier.
• An upgrade lifts a refusal on your next attempt. The plan on file is cached for up to five minutes, but a cached answer saying the allowance is spent is never trusted — it is re-checked against billing before a create is refused. Whether the account has API access at all is cached separately, for up to 30 seconds; see Timing.

Enterprise is unlimited and is arranged directly rather than bought in the app.