The space your client signs into

Every other guide is written for you. This one describes what your client sees when they sign in — because the size of your support load depends on how much of it they can do without writing to you.

The space is called My space, and it is white-label: your brand, your domain, no mention of us. What follows is the same screen from your side of it.

Two ways in, and one of them is not yours

A client who was created on your environment — by you, or through a signup link — signs in and lands on My instances: the ones you serve them.

Someone who bought on the public marketplace instead has no link to any single provider. Their instances live across whoever sold them, so the space shows them theirs and, if it cannot place them with a provider at all, says so and points them at the marketplace rather than at an empty page.

You will meet the difference the day a client tells you they "cannot find their instance". The question to ask is where they signed up.

The instances, and what a client may do to one

Opening one gives them four actions and two panels.

Yes — a client can delete their own instance. It asks a plain question first and states that it cannot be undone. If that is not what you want for a particular customer, the answer is not to hide the button but to keep the backups the backup guide describes; deletion is theirs to ask for, recovery is yours to have prepared.

The two panels are Capacity — users and storage against what their plan includes, with a way to buy more — and their company details, which is what becomes the company inside their Odoo. An axis nobody has measured is shown as not measured rather than as zero.

What they are paying

Under the instances sit their subscriptions: one line per thing they pay for, with its status, the amount, the duration it covers, and the next date.

Four states, and the date beside them is not the same date:

• Active — renews on that date.
• Trialing — the free period you granted on the offer.
• Payment overdue — the grace period ends on that date.
• Canceled — it stopped, and paying brings it back.

Below that, the payment history: every purchase and renewal, with its status. A payment that failed carries the reason next to it, in the rail's own words, so a client who was refused knows whether to try another number or another card.

Paying, and why nothing happens by itself

This is the rule to take away, and it explains the whole screen: no payment rail here debits a client off-session. There is no stored mandate that quietly takes money on the renewal date.

So an unpaid period is not a failure — it is an amount waiting. The client comes to the space and presses the button, and only then does anything move: a PIN prompt on their phone, or a secure payment page in a new tab. Which of the two they get is their choice, and both are on the card, above the button: the rail, the method, and the phone number that will be debited — visible so it can be corrected.

Two consequences worth planning for. A renewal will not happen while nobody looks at it, so the notice that a payment is due matters more than it would elsewhere. And a client whose SIM changed can fix it themselves, which used to be a support ticket.

If the amount cannot be collected on the rail they chose — some rails cap what they will take at once — the card says so before they press anything, and the durations that do not fit are shown disabled with the reason. A button that could only end in a refusal is worse than one that is not offered.

Growing and shrinking, without you

Change my plan lets them move the axes your offer actually sells — users, storage — and the two directions are not symmetrical:

• Bigger costs the difference for the days remaining in the period already paid for, and lands immediately once paid.
• Smaller costs nothing, refunds nothing, and takes effect at the next renewal. It is shown as scheduled until then, so a reduction asked for in March does not arrive in April as an unexplained drop.

Every figure on that panel comes from the server, and the amount is priced again when they confirm. A price that travelled through a browser is a price the browser chose, and this one never does.

An offer that sells neither axis shows no panel at all — there is nothing to move, and a disabled control would only invite them to press it.

What this changes for you

Three things follow from all of the above, and they are worth knowing before your first client arrives.

The credentials shown when an instance is created are shown once. Your client is told so, in those words. If they lose them afterwards, the recovery is the one in the Odoo access guide — a new password, issued by you, which kills the old one.

Suspension is not deletion. A client past their grace period stops being served and keeps everything; paying reactivates them. Your quota policy can do the same thing for a different reason, and it resumes them by itself when they come back under their limit.

And the space is only as good as what you put in the offer. The capacity panel, the duration choices, the resizing — each of them appears because the offer sells that axis. An offer with no per-user rate is an offer whose clients must write to you in order to grow. That can be exactly what you want; it should not be something you discover later.