Approvals and spending limits
What needs approval, who can approve it and how limits are counted.
On this page
Anything that costs money, or could take something offline, waits for a person to approve it. The approval covers the exact resource and parameters, so what runs is what was approved.
What needs approvalLink to this section: What needs approval
| Action | Who can approve |
|---|---|
| Buying a server or a domain | An owner (approve spending) |
| Stopping or rebooting a server | An owner (every site on it goes down) |
| A site's first public launch | Always an owner's review |
| Creating hosting, a database or a service | An owner or administrator (approve launch) |
| Adding, changing or removing DNS records | An owner or administrator (approve launch) |
| Purging an archived site | An owner, after 7 days, separately |
Starting a server, and starting, stopping or restarting an app or database, run straight away for people with infrastructure or deploy rights, and are recorded in the audit log.
Exact pricesLink to this section: Exact prices
Domain purchases, renewals and transfers approve the price you were quoted. Just before buying, the price is checked again, and nothing is bought if it changed. Alternatives are never suggested or bought for you.
BudgetsLink to this section: Budgets
Sites has no spending limits of its own. Every request carries its cost estimate, and for the platform owner's businesses the approval is decided in the AI platform, which also checks the budgets and caps. A workspace's own approvers decide its requests here. Requests not decided within 7 days expire and nothing runs.
Usage and spending still shows what was committed this month: every request that hasn't settled yet, however old, plus those made or finished in the month.