Train your chatbot with protected pages

Boei can read some pages that need a password or access token. An access token is a secret code that lets an app read selected pages. Ask your website administrator which method your website uses and which pages it allows Boei to read.

Only add information your chatbot may share with its visitors. Saving website access in Boei does not give each visitor their own website permissions.

Add protected pages

  1. Open Knowledge → Add source → Website.
  2. Paste one page address, or several addresses with one per line. Use full addresses starting with https://. All addresses must use the same website.
  3. Turn on Access to protected pages. The access fields appear only when this switch is on.
  4. Choose the method your administrator gave you and enter the details below.
  5. Add the source. Open it, select the pages you want to use and click Train chatbot.

For an index page that links to the pages you need, enter its address and turn on Add the pages linked from this address. Boei reads the links on that index page. Check the list before training. Pages that are not linked there may need to be added separately. New links are not added automatically later.

This option works with page addresses and index pages. It does not work with protected sitemaps, downloadable files or automatic discovery of a whole website.

Choose an access method

  • Username and password (HTTP Basic): use this when your browser shows a built-in username and password prompt. It does not fill in a login form on a website.
  • Bearer token: paste the token your administrator gave you. You can also paste Bearer <token> or the full Authorization: Bearer <token> line. Boei removes those labels and extra spaces automatically. For example, some Confluence installations use a personal access token, also called a PAT. Your administrator must confirm which method your installation accepts.
  • API key / custom header: enter the header name and secret value your administrator gave you. A header is an extra piece of information sent with a page request. An example name is X-API-Key.
  • Session cookies: open Advanced access, then enable Use session cookies. Paste the value in the form session=value; other=value. Ask your administrator for the correct value. Cookies can expire, so this method may need more frequent updates.

Only one method is used for each source. Choosing another method clears the details you were entering.

Website login forms, sign-in buttons and two-step login are not supported by this setting.

Check the content

After training your first page, open it in Knowledge and check the extracted content. It should show the information you wanted, rather than a login page or an access-denied message. Some websites return a login page without reporting an error, and Boei cannot always detect this. Remove any incorrect trained content and check the access details with your administrator before continuing.

Replace a password or token

  1. Open the website source in Knowledge.
  2. Choose ··· → Website settings.
  3. Click Replace access details.
  4. Enter the new details and click Save.

Saved passwords and tokens stay hidden. You must enter the details again when replacing them. Use Cancel to keep the saved details.

Changes apply the next time Boei reads a page. Select a page and train it again to use the new details now. Protected sources have no update schedule for the whole source. You can set an automatic update schedule for individual pages if your plan includes it. Updating a page does not discover new links on the index page.

Remove saved access

Turn off Access to protected pages in the source's website settings, then click Save. Boei removes the saved access details. Protected pages may then stop updating.

If you turn the switch back on before saving, Boei keeps the saved details. Switching off does not delete information already trained. Remove that content from Knowledge separately if the chatbot should stop using it.