Administration
The back office is the part of Stacklane where your staff run the platform. Here you connect Proxmox clusters, hosting panels, the domain registrar, PowerDNS and payment providers. You also set prices, handle invoices and answer support requests.
What the back office is#
The back office is not a separate application. It is a section of the same portal that your customers use. A staff member signs in with a normal account. When that account has a platform staff role, the portal shows an extra Administration entry.
All back-office actions use the API under /api/admin. See API for the endpoints.
Stacklane writes an audit record for the changes made in the back office. The record belongs to the organization of the staff member who made the change. See Clients and users.
Platform staff roles#
Every user belongs to one organization and has a role inside that organization (administrator, engineer, billing or viewer). A user can also have a platform staff role. The staff role gives access to the back office. It does not change what the user can do inside their own organization.
There are four staff roles:
| Staff role | Intended for |
|---|---|
owner | The person who installed Stacklane. stacklane setup creates the first owner. |
admin | Staff who configure the platform. |
billing | Staff who handle invoices and customer credit. |
support | Staff who answer support requests and handle customer services. |
owner and admin have the same permissions in the back office. The only difference is that the command line does not let you remove the staff role from the last owner.
What each role may do#
| Task | owner | admin | billing | support |
|---|---|---|---|---|
| Platform settings (brand, sign-up) | Yes | Yes | No | No |
| Regions, flavors, images, limits | Yes | Yes | No | No |
| Network and DDoS settings, signing secret | Yes | Yes | No | No |
| View the list of DDoS attacks | Yes | Yes | No | Yes |
| Panel servers and hosting plans | Yes | Yes | No | No |
| List hosting services, suspend, unsuspend, terminate | Yes | Yes | No | Yes |
| Registrar settings and extension prices | Yes | Yes | No | No |
| List all domains, mark a domain as registered | Yes | Yes | No | Yes |
| DNS hosting settings | Yes | Yes | No | No |
| Billing settings and payment providers | Yes | Yes | No | No |
| View invoices, mark as paid, void | Yes | Yes | Yes | No |
| Adjust a customer's credit balance | Yes | Yes | Yes | No |
| Run billing now | Yes | Yes | No | No |
| Helpdesk: read, reply, add notes, assign | Yes | Yes | Yes | Yes |
The API checks these permissions on every request. A request without the right role returns 403 with the error code forbidden.
Note: every staff role sees the Administration entry in the menu. Inside the back office, each user only sees the pages that their role may use. Users with the support role start in the Helpdesk. Some actions that the table allows for them, such as suspending a hosting service, are only available through the API.
Give someone a staff role#
You assign staff roles on the command line of the server. There is no screen for it in the portal.
-
Make sure the person has an account. They can sign up in the portal, or you can create the account with
stacklane user create. -
Run the command as the service user:
sudo -u stacklane stacklane user staff --email agent@example.com --role support -
Use
--role noneto remove the staff role again.
To create a new account that has a staff role from the start:
sudo -u stacklane stacklane user create --email ops@example.com --name "Operations" --staff-role admin
See Command line for all options.
Staff accounts can sign in without a confirmed email address, even when you require confirmed addresses for customers.
Open the back office#
- Sign in to the portal, for example at
https://panel.example.com, with an account that has a staff role. - In the left menu, under Platform, click Administration.
You can also go to https://panel.example.com/admin directly. Owners and admins start on the Regions page. Billing staff start on the Invoices page.
The back-office menu has these groups:
| Group | Pages |
|---|---|
| Support | Helpdesk |
| Cloud | Regions, Flavors, Images, Limits, Network and DDoS |
| Hosting | Panel servers, Hosting plans, Domains, DNS hosting |
| Billing | Invoices, Billing settings |
| Platform | Platform settings |
Each staff member only sees the pages that their role allows.
Set up a new platform#
Some settings depend on others. For example, every price must use the billing currency. We suggest this order:
- Branding and access: set the product name, colors, links and sign-up rules.
- Billing: set your company details, the currency, VAT and at least one payment method.
- Cloud: add a region, images, templates, flavors and an IPv4 pool.
- Hosting: add panel servers and hosting plans.
- Domains and DNS: connect the registrar, set extension prices and connect PowerDNS.
- Network protection: connect your DDoS detector.
- Set a support email address so your team receives new support requests. See Support.
Pages in this section#
| Page | Contents |
|---|---|
| Branding and access | Product name, accent color, links, support email, sign-up and default language and time zone. |
| Billing | Company and VAT settings, EU VAT rules, credit, invoices, metering, payment providers, reminders and suspension. |
| Cloud | Proxmox regions, templates, images, flavors, IPv4 pools, limits, and what to do when a task fails. |
| Hosting | cPanel/WHM, DirectAdmin and Pterodactyl servers and plans, provisioning and suspension. |
| Domains and DNS | Openprovider or manual registrar, extension prices, renewals, PowerDNS and nameservers. |
| Network protection | The DDoS webhook, request signing, FastNetMon, customer notifications and panel rate limits. |
| Support | The helpdesk, ticket statuses, replies and internal notes. |
| Clients and users | Organizations, users, roles, staff accounts and the audit log. |