Finlay.worksBareBones Ticketing manual

Use

Sign In And Find Your Way

How to sign in, where the product sends you, how search works, and how to change your landing page.

RC2 approved for evaluation Status: release-candidate Audience: Requester Source: c4b4d41

Sign In And Find Your Way

This page covers signing in, the two workspaces you land in, searching, and choosing where sign-in takes you.

If you reach BareBones Ticketing from your supplier's Customer Area rather than by typing a password, use Customer Area access instead.

Before you start

  • The sign-in address your organisation uses.
  • Your account name and the sign-in method your organisation set up. This may be single sign-on (SSO) or a password.

Your organisation creates accounts and resets passwords. This page does not cover either.

Sign in

  1. Open your organisation's BareBones Ticketing sign-in page.
  2. Sign in with the method shown for your account.
  3. If a two-factor code is asked for, enter it. Do not share the code.
  4. The product opens your landing page. For most people this is My Tickets. If you hold a staff role it is the Agent Queue, and for system administrators it is the administration workspace.

If a username is refused, try the full form. Where your account comes from your organisation's directory, the name that works is usually the fully qualified one — you@example.com rather than you. Some prompts accept the short form and some do not, and a refusal does not always explain itself. The full form is accepted everywhere the short form is, so prefer it.

Service Catalog is never the landing page for a role. It opens on sign-in only if you choose it yourself, under Change your landing page below.

If you were sent to sign-in from a page you tried to open, signing in does not by itself let you open that page. The product still checks whether you have access to it.

The two workspaces

My Tickets lists requests you submitted, plus requests where you were added as a copied person or a participant. See Track and update your request.

Service Catalog is where you submit a new request. See Submit a request.

If you also hold a staff role, other workspaces appear as well. See Roles and access.

Ticket results are limited to tickets you already have access to. Search never shows you a ticket you could not open anyway. An empty result means nothing you can see matched. It does not mean nothing exists.

Service results work differently. They are not narrowed to you: a service that any signed-in person can request may appear in your results. Seeing a service does not give you access to the department behind it.

  1. Type at least three characters into Global search in the header.
  2. Read the short result list. It shows up to three tickets, three services, and three pages.
  3. Select Review the full search surface if you need more. The longer list shows up to 12 pages, eight tickets, and eight services, under the same access rules.
  4. Open a result once its title tells you it is the item you wanted.

Ticket results cover requests you submitted and requests where you are an active copied person or participant.

Change your landing page

  1. Open Preferences, then Landing.
  2. Open Default landing page. It lists only pages you can already open.
  3. Choose a page, or leave it blank to keep the default for your role.
  4. Select Save landing preference.
  5. Check that Landing preference saved appears and that the summary shows your choice.

The next time you sign in, the product opens that page. A saved choice does not give you access. If your access changes later, the product sends you somewhere you can still open.

If it does not work

  • Sign-in is refused. Stop retrying and use your organisation's account recovery process.
  • The account shown is not yours. Sign out without opening any ticket and tell whoever owns that account.
  • A page you expected is missing from the landing list. You do not have access to it. Ask the person who manages access.
  • Saving the landing preference fails. Your previous landing page stays in place. Try again once the error is resolved.