In this section · 6 articles

Connect your Laramin to Brine Webs support

Enter the support desk's address and the customer key Brine Webs gave you, check the connection, and set the defaults for new tickets.

Applies to
Support Center 1.1 and later
Who can do this
Platform owner, Administrator
Permission
feature.sc.connection.edit
Where
Settings hub › Support Center › Connection
On this page

Before you start

  • Ask Brine Webs for your company's customer API key. Brine Webs also links that key to your project at their desk. Until they do, Support Center can't show any tickets.
  • You need feature.sc.connection.edit. With feature.sc.connection.view only, the panel opens read-only.
  • An admin key from Brine Webs' desk won't work. It would show every customer's tickets, so the desk refuses it here.

Steps

  1. Open the Settings hub. For example, open Configurations › General Settings › System Settings. In the panel list on the left, under Support Center, select Connection. Its address is /admin/settings/sc_connection if your Laramin keeps the standard /admin path.

    If Support Center isn't connected yet, its Overview says Connect Support Center to Brine Webs, and Open connection settings takes you to the same panel.

    The Brine Webs support desk section with Desk address https://crm.bsscn.com and a saved Customer API key shown as dots, and the New ticket defaults section with Default priority and Always copy.
  2. Under Brine Webs support desk, check the Desk address. It's filled in with https://crm.bsscn.com, Brine Webs' own desk. Change it only if Brine Webs tells you to. It must start with https://.

  3. In Customer API key, paste the key from Brine Webs.

  4. Under New ticket defaults, you can set:

    • Default priority: chosen on every new ticket until someone changes it. The list comes from the desk, so it's empty until the first time the connection works.
    • Always copy: email addresses copied on every new ticket. Choose people from your Laramin, or type addresses. Each ticket can still change them.
  5. Select Save changes.

Saving checks the connection first. If the check fails, nothing is saved and the panel says why.

Check the connection

Select Check the connection at any time. The panel then says, in words:

  • which company and customer number the key belongs to at Brine Webs,
  • which department new tickets go to,
  • which project your tickets belong to,
  • whether your team may close tickets, or Brine Webs closes them when you ask.

Read the company name. If it isn't yours, the key is wrong: ask Brine Webs for the right one before anyone raises a ticket.

The key is kept secret

  • The key is stored encrypted and is never shown again. To keep the saved key, leave Customer API key blank when you save other changes.
  • The key is only ever sent to the address it was saved with. If you change Desk address, you must enter the key again. Otherwise you see The desk address changed, so enter the customer key again.

What happens next

The Overview now says Connected, and people with the permissions can raise tickets. See Raise a ticket. If the panel says the key isn't linked to a project yet, ask Brine Webs to link it, then select Check the connection again.