Pages

Bnder pages is your solution to connect your team with your users.

What are Pages?

Pages are static content that you can create and manage inside your Bnder workspace. They are perfect for creating landing pages, documentation, FAQs, and other types of content that need to be easily accessible to your users.

Pages can be hosted on a Bnder subdomain (e.g., company.bnder.page) or on a custom domain that you own (e.g., www.company.com).

Each page can have a custom display name that will be shown to the user when visiting the page.

Each page domain can also have its own branding. You can set:

  • a logo
  • a primary color
  • a secondary color
  • a background color
  • a text color
  • an optional background image

The dashboard also includes light and dark presets to quickly seed the page background and text colors. You can also reset the colors back to the default Bnder Pages theme without removing your logo or background image. If you only set a background color, Bnder automatically chooses a readable light or dark text color for the page until you override it manually.

Branding is configured per domain, so different entry points for the same workspace can look different. The same brand colors also show up on public document navigation and content accents. If a logo is configured for a domain, public pages on that domain also use it as the browser favicon. Uploaded images are stored on Bnder's CDN and served from there.

Public page language

Each page domain has a public page language setting. It controls Bnder-owned buttons, labels, messages, errors, dialogs, placeholders, and page metadata on public pages. Available languages match the Bnder app and bot languages.

Workspace-authored content is not translated automatically. Public document titles and content, ticket project names, ticket template names and descriptions, custom field labels, status names, and page display names are shown as written.

Page domain entry point

Each page domain has an entry point setting that controls where visitors go when they open only the domain, such as company.bnder.page.

You can send visitors to:

  • Public docs (/doc)
  • New ticket (/tickets/new)

New and existing domains use public docs by default. Change the entry point from Workspace settings -> Pages when a support portal should open the new ticket flow first. You can also choose a default project for that domain. When set, visitors who open documents without a project in the URL start in that project's public docs, and visitors who open the new ticket entry point go directly to that project's ticket form when public ticket creation is enabled. If the project is no longer public, Bnder falls back to the project selector.

  • Workspaces with no paid seats can use one .bnder.page domain.
  • Starter seats add .bnder.page domain slots.
  • Pro seats add page-domain slots.
  • Each Pro slot can be used for either a .bnder.page domain or a custom domain.

Starter and Pro domain slots can be mixed in the same workspace. Custom domains require at least one Pro seat.

If your workspace uses the ticket system, notification emails always link to your workspace page domain (for example company.bnder.page or your custom page domain), not a generic global URL. They also use that page domain's logo, display name, and primary color when configured. If no ticket page branding is available, the email falls back to the Bnder logo and default accent color. When the email footer says it was sent via Bnder, the Bnder label links to bnder.net.

This applies to:

  • Ticket thread links (/ticket/thread/{token})
  • Ticket unsubscribe links (/ticket/unsubscribe/{token})

For full ticket setup and public portal behavior, see:

Booking links live on your Bnder Pages domain and are public links you can share with visitors to request time with you. They use a path like /calendar/book/{key} on your page domain.

Learn more:

Create a Page

Requirements

  • MANAGE_SETTINGS permission in your workspace
  • Access to your domain DNS settings (if using a custom domain)

To create a new page in your Bnder workspace, follow these steps:

Using Bnder Subdomain

  1. Navigate to the "Pages" section in your Bnder workspace.
  2. Click on the "Create Page" button.
  3. Select the option to use a Bnder subdomain.
  4. Type the subdomain you want to use (e.g., company for company.bnder.page).
  5. Type a display name for your page.
  6. Optionally add your logo, brand colors, background and text colors, and a background image for that specific domain.
  7. Choose the public page language for Bnder-owned UI copy.
  8. Choose whether the bare domain should open public docs or the new ticket page.
  9. Optionally choose the default project for documents and the new ticket entry point.
  10. Click "Create" to finalize the setup.

Using Custom Domain

  1. Navigate to the "Pages" section in your Bnder workspace.
  2. Click on the "Create Page" button.
  3. Select the option to use a custom domain.
  4. Make sure your workspace has at least one Pro seat.
  5. Enter the name of your custom domain (e.g., www.company.com).
  6. Type a display name for your page.
  7. Optionally add your logo, brand colors, background and text colors, and a background image for that specific domain.
  8. Choose the public page language for Bnder-owned UI copy.
  9. Choose whether the bare domain should open public docs or the new ticket page.
  10. Optionally choose the default project for documents and the new ticket entry point.
  11. Follow the instructions to configure your DNS settings to point to Bnder's servers.
  12. Click "Create" to finalize the setup.
  13. Wait for the DNS changes to propagate, which may take up to 48 hours.

What counts as a Session?

A session is counted each time a user visits your page. Public document lists and ticket create pages count toward your page session usage, and paid Starter or Pro seats increase the available page traffic shown on the pricing page. You can see your current hourly and monthly page session usage and limits in Workspace settings -> Pages and Workspace settings -> Plans & Seats. Ticket thread pages are not counted as sessions because they can refresh while open. It doesn't matter how many documents the user views during their visit. If a ticket form reaches the page visit limit, visitors see a message explaining the limit instead of a generic unavailable page. A session will be terminated once the page is fully loaded again.