Skip to main content

1. Access Your Instance

The first step of the Quickstart: sign in to your portal and spend five minutes learning where things are, so that the rest of the path is a matter of following directions rather than hunting for menus. This page is for anyone on their first session, whether you will go on to administer the instance or only to work tickets in it.

Before You Begin​

  • Your portal URL: the address assigned to your organization's instance, in one of the formats in Step 1 below.
  • Your credentials: either an account with a Microsoft or Google identity provider, or a username and password.
  • Chrome or Firefox, current version. See Fluency Web Interface for the supported-browser list.

If you have not received access, raise a support ticket.

Step 1: Open Your Portal URL​

  1. Find your instance URL. Standard deployments use:

    https://<companyname>.app.ingext.io

    Older deployments use one of:

    https://<companyname>.cloud.fluencysecurity.com
    https://<companyname>.app.fluencyplatform.com

    Custom deployments, self-hosted instances, and MSSP-managed portals use their own hostname, which may be one your organization chose.

    The v2 interface is served under /v2/ of that address (https://<companyname>.app.ingext.io/v2/) and the classic v1 interface at its root. Both sign in with the same account and work on the same data.

  2. Open it in Chrome or Firefox.

  3. You land on the login page, which offers two OAuth options (Microsoft and Google) and an Alternative login option for a username and password.

If you do not know your URL​

Look in your onboarding email, ask whoever administers the instance, or, if you deployed it yourself, take it from the deployment output. Support can also confirm it: see Fluency Web Interface.

Step 2: Sign In​

  1. Choose your authentication method. OAuth with Microsoft or Google is the preferred route; use Alternative login for a username and password. Which one applies to you was decided when your account was created: by the initial setup if you are the first user, or by the administrator who added you.
  2. Complete the provider prompt. If this is the first time your organization has signed in to Fluency through Microsoft, you are asked to accept two application permissions: Sign you in and read your profile and Maintain access to data you have given it access to. Granting them redirects you back to the portal.
  3. You land on the Home dashboard.

Login covers each method in full, including the permission prompts and changing a password.

First-user setup​

If you are the very first user in a brand-new instance, the OAuth provider is chosen during initial setup, and every account after yours is created by an existing administrator from Admin console → Users (v1: Settings → Users). See Managing Users.

Step 3: Get Your Bearings on the Home Dashboard​

Home dashboard with the Attention needed banner across the top, the Open cases, Usage and Datalake storage panels on the left, and the Health &amp; status, Cases handled and Median MTTR panels on the right

The dashboard is a banner across the top above two columns of panels:

  • Overall status: a full-width banner that sums up what needs attention. When something does, it reads Attention needed with a line saying what: for example, which applications are inactive.
  • Open cases, Usage, and Datalake storage (left). Open cases lists the cases still open from the last 24 hours. Usage gives the data received Today, Yesterday, and This month, each as a volume with its event count. Datalake storage, in the lower half of the same panel, charts what the data lakes stored over the last 24 hours and lists each index, busiest first, with its volume and event count.
  • Health & status, Cases handled, and Median MTTR (right). Health & status counts the installed applications that are Healthy, Inactive, and in Error, and lists the ones that are not healthy with their state; click one to open its details. Cases handled counts the cases handled in the last 24 hours, and Median MTTR gives the median time to resolve a case.

Two panels link to a full page from their upper-right corner: All cases on Open cases opens Overview Summary, and Applications on Health & status opens the Applications page. Home describes each panel in full.

On a fresh instance most of this is empty: Open cases reads No open cases., Usage and Datalake storage have little or nothing to show, Health & status may list no applications at all, and Median MTTR shows a dash with the note no closed cases yet. That is the expected starting state, and step 2 of this quickstart is what fills it in.

Step 4: Tour the Navigation​

The navigation rail down the left edge of the screen is the same on every page except the Admin console. Walking it once now means you will recognize each destination when a later step names it. The rail opens collapsed, as a column of icons: hover over an icon to see its name, or click Expand menu near the bottom of the rail to show every name beside its icon.

v2 interface with the navigation rail expanded, listing Home through Configuration at the top and Admin console, Documentation, What’s new, Collapse menu, the signed-in account, and Sign out at the bottom

Detection and triage

Overview Summary, Metric Alerts, Cases Search, and Notable Events; a case opens in a detail panel, whose Open case link opens the Behavior Summary page. Step 5 works here, and on Behavior Rules, one of the Configuration cards.

Search

Datalake Search and KQL Search. Step 4 uses both.

Resources and Assets

What integrations and collectors have discovered. The quickstart does not use them, but they are named here so they are not a surprise later.

The data pipeline

Applications and Platform. Step 2 installs an application and looks at the pipeline it built; step 3 checks its status.

Reports

The Event Ingress, Ticket Analysis, and Usage reports, and the FPL report processors. Step 3 uses the Event Ingress Report.

Configuration

A hub of fourteen cards, one per configuration page: Data Lakes, Processors, Notifications, Behavior Rules, Collectors, Integrations, and the rest. Steps 3, 5, and 6 all open pages from it.

The bottom of the rail

Admin console, Documentation, What’s new, Expand menu, the account avatar with your initials, and Sign out. Two things are worth fixing in your memory now, because they are the most common source of hunting later:

  • Account and organization administration lives in the Admin console, not on Configuration. It replaces the rail with a side navigation of its own and opens on the Users page, with API Tokens, the RBAC pages (Roles, API Policies, Data Policies), and the Management pages (Audit Logs, Lake Tasks, Report Tasks, Archived Reports, Investigation History) beside it. Back to portal returns to Home.
  • Your own settings live behind the account avatar, not in the Admin console.

Navigation is the area-by-area reference this tour summarizes.

Step 5: Set Your Preferences​

Click the account avatar with your initials near the bottom of the navigation rail. The Profile page opens at /v2/profile.

Profile page with the read-only Account Information card and the Change Password card on the left, and the Preference and Portal Layout cards on the right

  1. Check Account Information: your name, email, and roles, with First Name, Last Name, and Email below. The card is read only: an administrator changes these details on Admin console → Users. The badge in its upper-right corner shows how you sign in: Local for a username and password.
  2. Set Preference → Theme: Light, Dark, or System, which follows your operating system's light or dark setting; and Text size, such as Normal or Large. Click Update Profile; the page reports Profile updated successfully.
  3. Under Portal Layout, turn on Keep rail expanded if you want the rail to show each page's name beside its icon all the time.
  4. If you signed in with a username and password, set your own password in the Change Password card: Current Password, New Password, Confirm Password, then the Change Password button. Leaving Current Password empty produces Please enter your current password. If you signed in through Microsoft or Google, your password belongs to that provider and this card does not apply.

The portal's version number is printed beneath the Portal Layout card, worth noting before you open a support case.

API tokens are somewhere else

Tokens for the REST API are account administration, not personal settings, and live in the Admin console, under API Tokens (v1: Settings → Advanced → Permissions). See API Tokens.

How to Tell It Worked​

  • You reach the Home dashboard without an error, and the navigation rail is visible down the left edge.
  • Every rail item opens its page, and you can say in one sentence what each is for.
  • The account avatar near the bottom of the rail shows the expected user's initials, and opens your Profile.
  • If you are an administrator, Admin console opens on the Users page.

If It Did Not Work​

SymptomCauseWhat to do
The URL does not resolve, or shows an unrelated pageWrong hostname: an older deployment format, or a custom hostnameCheck the onboarding email against the formats in step 1, or ask your administrator.
The Microsoft or Google prompt refuses with a consent or admin-approval errorYour tenant restricts user consent to applicationsAn administrator has to approve the two sign-in permissions once for the organization. See Login → OAuth App permissions.
Sign-in succeeds but pages are empty or actions are refusedThe account has no role, or its roles do not grant read access to the dataAn administrator assigns a role that carries the data_review API policy, as the built-in analyst role does, from Admin console → Users (v1: Settings → Users). See Managing Roles → What a role needs to read data.
The login page loads but the OAuth buttons do nothingA browser extension or network policy is blocking the redirect to the providerTry a private window with extensions off, or a different network.
Nothing above matches-Create a support ticket with your instance URL and the exact error text.

Next Step​

2. Connect Your First Source: put real data into the instance.

Last updated on