Branding and access
On the Platform settings page you set how the portal looks to your customers and who can sign up. Only staff with the owner or admin role can open this page.
Open the page#
- Open the back office. See Administration.
- In the Platform group, click Platform settings.
- Change the fields you need and click Save.
The changes take effect right away. Stacklane writes the audit event admin.platform.settings.
Brand#
| Field | Required | Description |
|---|---|---|
| Product name | Yes | The name of your service, up to 40 characters. Default: Stacklane. |
| Accent color | Yes | A hex color in the form #rrggbb, for example #0f766e. Default: #6366f1. |
| Support email | No | Email address for support. |
| Website | No | The address of your public website. Must start with http:// or https://. |
| Documentation URL | No | Link to your customer documentation. Must start with http:// or https://. |
| Status page URL | No | Link to your status page. Must start with http:// or https://. |
Where the brand appears#
- Product name. It appears in the browser tab title, in the left menu, on the sign-in page and in every email that Stacklane sends, for example "Reset your Example Cloud password". It is also the issuer name that authenticator apps show for two-factor authentication.
- Logo. When the product name is
Stacklane, the menu shows the Stacklane logo. With any other name, the menu shows the first letter of your product name and the full name next to it. - Accent color. The portal uses it for buttons, links and other highlights.
- Support email. The top bar shows a support icon that opens a new email to this address. The sign-in pages and the dashboard show it too. Stacklane also sends a notification to this address when a customer opens a support request or replies to one. See Support.
- Documentation URL and status page URL. The top bar, the sign-in pages and the dashboard show links to these pages.
If you leave an optional field empty, the portal does not show the link or icon.
Sign-up and defaults#
| Field | Default | Description |
|---|---|---|
| Default language | English | The language of the portal before a user chooses one. You can choose English or Dutch. |
| Default time zone | Europe/Amsterdam | The time zone for users who sign up or are invited. Users can change it in their profile. Use a name from the time zone database, for example Europe/Berlin or America/New_York. |
| Allow new customers to sign up | On | When this is off, the sign-up page shows "Registration is closed" and the API returns 403 with the code registration_closed. |
| Require a verified email address before using the portal | On | When this is on, customers must click the link in the confirmation email before they can sign in. |
Sign-up#
When sign-up is open, anyone can create an account on the sign-up page. Stacklane then:
- creates a new organization, named after the company name or, if that is empty, the person's name;
- makes the new user the administrator of that organization;
- sends a confirmation email with a link that is valid for 48 hours.
If someone signs up with an email address that already has an account, Stacklane does not create a second account. It sends an email to the existing address with a link to reset the password.
Verified email addresses#
When you require verified email addresses, a customer who has not clicked the confirmation link gets the message "Confirm your email address first" when they sign in. They can ask for a new link on the sign-in page.
This rule does not apply to:
- users with a platform staff role;
- users who were invited by an organization administrator. The invitation link confirms the address.
Resetting a password through the email link also marks the address as confirmed.
Closed sign-up#
Close sign-up when you only want to create accounts yourself. You can then:
- create accounts on the command line with
stacklane user create(see Command line); - let customer administrators invite their own team members (see Clients and users);
- import customers from WHMCS (see Migrating from WHMCS).
Settings in the API#
The page uses these endpoints. Both need the owner or admin staff role.
| Method | Path | Description |
|---|---|---|
GET | /api/admin/platform/settings | Read the brand and access settings. |
PUT | /api/admin/platform/settings | Replace the brand and access settings. |
Example body for PUT:
{
"branding": {
"product_name": "Example Cloud",
"accent_color": "#0f766e",
"support_email": "support@example.com",
"docs_url": "https://docs.example.com",
"status_url": "https://status.example.com",
"website_url": "https://www.example.com"
},
"access": {
"registration_open": true,
"require_verified_email": true,
"default_locale": "en",
"default_timezone": "Europe/Amsterdam"
}
}
The portal reads the public part of these settings, without signing in, from GET /api/iam/frontend/variables. That response contains the product name, accent color, support email, the three links, whether sign-up is open and the default language.