Docs → Advanced Features → CP run administration
⚔️ CP run administration
Run the admin side of CP: create and open a run, set who pays what, approve CP submissions, close the books, and manage defenders and balances.
A CP run has a tank, a defender, a list of participants and, at the end, money moving between all of them. CP RUNs → CP RUNs administration — the page opens headed CP Runs — is where you set that up and, once the run has happened, where you close the books on it.
Which page does what
All five sit in the CP RUNs section of the menu. Three of them open under a heading that is worded differently from the menu entry, which is the usual reason people think they have landed on the wrong page — so the table gives both.
| Menu entry, under CP RUNs | Heading on the page | What you do there |
|---|---|---|
| CP RUNs administration | CP Runs | Create runs, add and charge participants, approve CP submissions, close runs. |
| Defender Management | Defender Management | Active defenders, incoming applications, revoking and restoring, and adding a defender who has no portal account. |
| Clan CP accounts | CP Accounts | Every balance, transaction histories, recording payments, reviewing players' change requests, and your currency types. |
| CP Settings | CP Clan Settings | The defaults every new run starts from, the balance rules, and your defender invite code. |
| Clan Statistics | CP Run Statistics | Read-only overview of participation, CP earned and charges across every closed run. Members can see it too. |
The life of a run
| State | What it means | What you can do |
|---|---|---|
| Draft | Created, but invisible to members. | Edit anything, add participants yourself, Open for Signup, or Delete Run. |
| Open | Members who meet the requirements can sign themselves up, until the deadline. | Edit, add or remove participants, approve submissions. Not deletable. |
| Pending close | An open run whose scheduled time has passed. It is not a separate state in its own right — it is the portal telling you this one is waiting for you. | Everything an open run allows, plus Close Run. |
| Closed | Charges and payouts are booked and the run is locked. | Look at it. Nothing more. |
The four counts at the top of the page are the same four states. Pending Close is the one to keep at zero.
Creating a run
Every field arrives pre-filled from CP Settings, so normally you only touch the title, the tank, the defender and the times.
The tank must be a member of your clan. The defender must be an active defender — defenders are, by definition, never members of your clan. Anyone missing from the list is either not approved yet or revoked; both are handled on Defender Management.
Scheduled at (UTC) and Sign-up deadline (UTC). The deadline cannot be after the run starts. If the scheduled time falls inside a Ruthless Slaughter window, the form says so — troops can be revived with silver during RS, so tanks normally take a lower payout on those runs.
A run is always created as a draft. Opening it is a separate action — from that moment members can sign up, and the run can no longer be deleted.
What you are setting
| Field | What it controls |
|---|---|
| Price per Trillion CP (Silver) | What participants are charged. The form shows the equivalent per billion as you type. |
| Min G / Max G / Min S / Max S | Who may sign up. Values run from 1 to 9, and a minimum cannot be above its maximum. |
| Stats max age (days) | How recently a player's stats must have been synced for them to sign up. Starts at 5. |
| Max participants | Leave empty for no limit. Adding someone past the limit is refused. |
| CP City | The clan member whose city gets reinforced. They must be a member of your clan. |
| Equipment allowed · Artifacts allowed | Whether players may use those bonuses during the run. |
| Instructions | Shown to players at the moment they sign up. The single most effective place to prevent a support question. |
Paying the tank and the defender
Each side is independently either Variable % — a share of what the run collects — or Fixed amount, a flat sum whatever the run earns.
- Both on a percentage: the two cuts must add up to exactly 100%. The run pays out precisely what it collects and nothing is left over.
- Either side on a fixed amount: the payouts no longer match what the run collects. Whatever is left over goes into the clan vault, and any shortfall is taken out of it. A fixed amount must be greater than zero.
The close confirmation shows the numbers before you commit: total CP, total charged, what the tank receives, what the defender receives, and how much silver moves into or out of the vault.
Participants and their CP
Members sign themselves up once the run is open. You can also use + Add Participant — only clan members who are not already signed up are offered — and choose how they pay:
- Pay — billed after the run.
- Free — no charge at all.
- Clan vault — the clan vault pays for them.
Free and Clan vault are only offered if your CP Settings allow them. Each row then carries a Showed up tick, the CP earned (M) figure, the payment method and the resulting Charge.
Submissions
Players can submit their own CP with screenshots. Those appear under CP Submissions on the run, showing CP per attack and number of attacks, and you can correct the figures before deciding.
- ✓ Approve writes the totals as they stand to that player's CP for the run and recalculates their charge. They are notified.
- ✕ Reject tells the player, optionally with a reason you type, and lets them submit again.
Closing the run
Two things stop a close, both on purpose: the run must be open, and its scheduled time must have passed. The portal refuses to charge people for a run that has not happened.
Defenders
Defender Management holds all of it. Players from other clans apply using the defender invite code from your CP Settings; applications land here for ✓ Approve or ✕ Reject, with an optional reason the applicant sees.
- Revoke Defender stops them being assigned to new runs. Balance and history are kept, and Restore Defender brings them back unchanged.
- + Add Defender creates a defender who has no portal account at all. They get a balance and appear in run history like anyone else, but cannot sign in to see it. The name must match their in-game name so payments can be reconciled.
- Regenerating the invite code invalidates the old one immediately; anybody still holding it can no longer apply.
Accounts, payments and change requests
CP RUNs → Clan CP accounts is the money side. Accounts are created automatically the first time a player is charged or paid.
- + Record Payment always has two sides — this account pays, the account you choose receives.
- Balances are always kept in Silver. Currency types are exchange rates; a new rate closes the current period and starts a new one, so past transactions keep the rate they were booked at.
- When a player disputes a payment, their request appears in Change Requests here. Approving an edit updates it on both accounts; approving a delete reverses it on both and keeps the record, marked deleted.
- Copy for In-Game builds a plain-text statement, capped at 1,000 characters, to paste yourself or send with Send as Direct Message.
Only payments can be deleted here. A charge belongs to a run, not to the account.
Defaults, so you stop typing the same numbers
Every field on a new run is pre-filled from CP Settings — cuts, price, level requirements, stats age, equipment and artifacts, the default CP city, the default instructions. The same page sets the Minimum Allowed Balance (Silver) below which a player cannot sign up (a negative figure is the maximum debt you tolerate), and whether Free and Clan vault are offered at all.
The member's side — signing up, submitting CP, reading a balance, applying as a defender — is covered in What a CP run is, Joining a CP run, Your CP account and Becoming a defender.
Common questions
The Close Run button is not there. Why?
Two conditions have to hold, and the page hides the button until both do.
- The run must be open — not a draft, not already closed.
- Its scheduled time must already have passed. Until then the panel says closing opens once the run has taken place, because charging everyone for a run that has not happened is worse than waiting.
If the run genuinely happened earlier than scheduled, edit the scheduled time first.
I cannot delete a run. What are my options?
Only a draft can be deleted. Once a run has been opened it has participants and can have submissions against it, and deleting it would leave those records orphaned.
An open run you no longer want can be left unclosed, or emptied by removing its participants — removing someone charges them nothing.
The tank and defender cuts have to add up to 100%. How do I keep a share for the clan?
Put one side — usually the defender — on Fixed amount instead of a percentage. The two no longer have to balance, and whatever the run collects beyond the payouts goes into the clan vault. A shortfall works the same way in reverse and is covered from the vault.
The close confirmation shows exactly how much silver moves into or out of the vault before you commit.
A defender I want to use is not in the dropdown.
The defender list on a run only offers active defenders for your clan. Open Defender Management and check which of these applies.
- Their application is still sitting in Defender Applications, waiting for you to approve it.
- They were revoked at some point — use Restore Defender.
- They never applied. Send them your defender invite code from CP Settings, or add them yourself with + Add Defender if they do not use the portal.
Related