Current Doc

Organizations

Use Browse Docs to switch sections and search the full docs list.

Documentation

Blue Lantern Security Docs

Learn how to use the marketplace, run security tools, and integrate via the API.

Organizations

Bring a team onto one account, manage members and monitors, and centralize all of your monitored scan data under a single bill.

Every login starts in your personal account — a permanent, single-user account that's just for you. When you want to collaborate with a team, share billing, and give teammates monitor access, you create an organization (a shared account). This page explains how.

Personal vs. organization accounts

Personal accountOrganization (shared)
Who it's forJust youA team
MembersNone — single userAdd admins and monitored members
SeatsOne Seat License maxPer-seat billing for the whole team
VisibilityYour own runsAdmins see every member's runs
CreatedAutomatically at signupYou create it, and become its admin

You always keep your personal account, and you can belong to or administer multiple organizations. You switch between them at any time — see Switching accounts.

Creating an organization

  1. Open the account switcher at the top of the page and choose New organization (you can also use the Create an organization button shown on a personal account).
  2. Give it a name (required — for example, "Acme SecOps") and confirm.

Your organization runs on Seat Licenses only (there is no Free Tier on a shared account), and you're switched into it immediately as its admin. You can create up to 20 organizations, and rename any of them later.

Switching accounts

The account switcher lives at the top of the Organization page. It lists your personal account first, then your organizations alphabetically, each with a Personal or Shared badge, your role, and a check mark next to the one you're currently in.

Selecting an account switches your entire session into it — every page, balance, and run list re-loads against that account. Whichever account you're in is the one that new scans, purchases, and monitors apply to, so check the switcher before you buy seats or create monitors for a team.

Default account at sign-in

Each row in the switcher has a star: starring an account makes it your default at sign-in, so every fresh login lands you there instead of your personal account. It's a per-user preference — every member picks their own, no admin needed — and clicking the star again clears it. If your access to the starred account is ever revoked, the preference is ignored and sign-in falls back to your personal account.

Managing members

On an organization's Organization page, the Members table is where you add teammates and control what each one can do. Members have a role, a status, and a seat.

Roles

  • Admin — Can sign in and manage the account. An admin sees all runs, members, and billing for the organization. Admins don't consume a seat by default.
  • Member — Monitor-only. A member cannot sign in and has no visibility into the account — they're simply granted monitor keys to use on the platform. A member uses one seat.

Add someone with Add member, enter their email, and pick a role. Change a role later from the role dropdown on their row. Changing a role never disturbs their seat assignment.

Statuses

  • Active — A full member of the organization.
  • Invited — Added but not yet active.
  • Revoked — Removed from active use. A revoked member keeps their prior settings but stops occupying a seat. Use the Reinstate button to restore them (their previous role and seat come back).

Use Remove to revoke a member. They lose access and stop consuming a seat immediately.

Seats

Each member row has a seat toggle — 1 seat (licensed) or No seat. Click it to assign or release a Seat License for that member. Assigning a seat is what puts a member's monitor activity under the flat Seat License. If every purchased seat is already in use, you'll be prompted to add more seats before you can license another member.

See Seat Licenses & Pricing for how seats are billed.

Tying a Seat License to a monitor

Seats are metered by email address. A monitor's scans are covered by a Seat License only when the monitor's seat assignment (attribution) email exactly matches the email of a seated (monitored) member.

Every monitor (created from the Monitors view in the Monitoring Hub) has two separate fields:

  • Monitor Name — a free-text display label so you can tell monitors apart (for example, "Alice's laptop browser extension"). It has no effect on billing.
  • Seat Assignment — the seated member the monitor's runs bill to. It appears as the submitter on every scan the monitor runs.

A seat assignment must be the exact email of an active seated (monitored) member — assignments that don't match an existing seat are rejected, so seat the member first. Leave the field blank to keep the monitor unassigned; an unassigned monitor has no seat coverage, so its scans are refused until you assign a seated member.

Both fields can be edited at any time from the Monitors table (the Edit action) without regenerating the key — renaming a monitor or reassigning it to a different seated member never breaks the extension using it.

So the chain is: seat a member (assign them a seat on the Members table) → create a monitor whose seat assignment is that member's exact email → that monitor's runs are covered by that member's Seat License.

Centralized visibility

Rolling monitors up under an organization gives an admin one place to see everything:

  • Admins see all runs. In the Monitoring Hub, an admin sees every member's URL, email, and file scans across the whole organization, and can filter by submitter to focus on one member or monitor.
  • Members see only their own. Non-admin members are automatically scoped to their own activity.
  • One bill, one dashboard. Seats and billing roll up to the organization, so you manage the team's usage and cost from a single account instead of chasing individual users.

Tip — Because runs are attributed by submitter email, giving each monitor a distinct, meaningful submitter (a real seated user's email) keeps the Monitoring Hub easy to filter and makes seat coverage unambiguous.

Need Help?

Can't find what you're looking for? Reach out and we'll get back to you.

Contact Support