Skip to main content

Quickstart

This walks through the shortest path from a fresh login to a populated asset inventory.

TODO

Confirm the onboarding wizard steps and the exact minimum permissions each integration needs, then replace the placeholders below.

1. Sign in​

Open your deployment's console URL and sign in with the credentials you were issued. Each organization has its own deployment and therefore its own address, given to you during onboarding:

https://<your-organization>.lumenedge.co

If multi-factor authentication is enforced for your account, you are prompted to enrol an authenticator app on first sign-in. Scan the QR code, then enter the six-digit code to confirm.

2. Pick a tenant​

Every URL in the console is scoped to a tenant:

/t/<tenantId>/dashboard

Use the tenant switcher at the top of the left rail to move between the tenants your account can reach. If you only have access to one, it is selected for you.

3. Connect a source​

An empty tenant has nothing to show, so the first real step is connecting a discovery source. Go to Integrations → Add integration and pick one you already run — see Integrations for the full list.

Which source should I start with?

Start with whichever tool has the broadest coverage of your estate. In most environments that is EDR (CrowdStrike, Carbon Black, Windows Defender) because it is deployed on nearly every managed endpoint. Directory and cloud sources are better second additions — they add identities and unmanaged cloud workloads that EDR does not see.

4. Wait for the first sync​

Integrations run on a schedule. After the first successful run, assets appear under Assets. The integration's detail view shows the last run, the number of records fetched, and any errors.

First sync can be slow

The initial pull is a full sync of the source, so it takes considerably longer than the incremental runs that follow. Give it time before assuming something is wrong.

5. Run a scan​

With assets in place, you can scan them. Create a scan template describing what to check, then run it against a target set — see Scanning.

6. Export a report​

Finally, confirm the loop end-to-end by producing a report from Reports → New report. See Reports.

Next steps​