Your account's settings and capabilities

Every hosting account has two kinds of boundary. How much you may use — disk space, mailboxes, websites — and what you may use: mail, FTP, databases, SSH. The first are numbers, the second are switches. They live on one page, and every row says where its value came from.

You will find it under Accounts → (your account) → Settings.

What is on the page

The page has two blocks.

Capacity is the numbers: disk space, memory, websites, mailboxes, databases. Behind each one is its origin — for example Inherited from Business. That means: this number comes from your plan, and it moves when the plan moves.

Capabilities is the nine switches: mail, FTP, DNS management, databases, SSH, cron, SSL management, backups and statistics. When a capability is off, its section disappears from your account's menu. That is not a trick of the screen: the server refuses the matching requests too, with a clear message saying this capability is not part of your plan.

At the top of the page there is a label:

• Follows plan — nothing has been set by hand on this account. When your hosting provider changes the plan, this account changes with it.
• Custom — at least one permanent exception has been made.

Where a value comes from

A value is decided from the top down:

platform  →  server  →  reseller  →  plan  →  account  →  you

The lowest one that says something wins. Usually only the plan says anything, and you read Inherited from \<plan name\>. If an exception has been made for your account, the row says Set here and shows what the value would be without it.

One rule matters: a lower level may only restrict, never widen. An account can therefore never switch on a capability its plan does not have. If you need more, the plan goes up — that is one screen away and it leaves a record.

A temporary exception

Sometimes the extra room is only needed for a while: a webshop in December, a migration that parks two copies of a site for a few days. That is what a temporary override is for.

Your hosting provider chooses Temporary and a duration: 24 hours, 7 days or 30 days. The page then shows a label like:

Temporary until 11 Aug 2026 — then falls back to 2048 from the plan

On that date it happens by itself. Nobody has to remember, no reminder goes in a calendar, and the server is told the old value the moment it is due. A temporary override also does not make your account permanently "Custom": a plan change still reaches you.

Who may do what

• You, as a customer, can read this page. You see what your plan gives you and whether anything has been changed for you. Changing it is your hosting provider's to do — an account can never grant itself wider limits, not even temporarily.
• A reseller changes their own customers' accounts, inside their own ceiling.
• An administrator changes everything, and still cannot widen anything at a lower level: that goes through the plan.

When something is missing

If a section you expected is not there — FTP, say — that capability is not in your plan. The Settings page shows it: under Capabilities it reads Off, with the plan it came from beside it. Ask your hosting provider for a plan that includes it; the moment that is changed the section is back, without you signing in again.

If you use such a capability anyway — through the API, for instance — you get a clean refusal with the code feature_disabled, rather than an error that pretends something is broken.

From the command line

Administrators can get the same answer from a terminal. This is the quick way to find out why an account has a particular value:

# everything that can be set, and at which levels
corecp-panel settings --registry

# one account, with the origin of every value
corecp-panel settings --account stck1.corecp.dev/test100

# put expired temporary overrides back now
corecp-panel settings --expire

The last command does exactly what the background pass does every five minutes; it exists for the moment you do not want to wait.