Skip to main content

Projects

A project is the top-level container for your organization's attack surface. Every asset and agent belongs to exactly one project — there's no unscoped, project-less view of your data. Projects are also where you configure per-scope automation (Workflows) and control whether continuous scanning is active. For most organizations, creating a project is the first thing you do after onboarding.

If your organization only uses a single project, most of this is invisible day-to-day — new assets and agents are automatically placed into it. Projects become important once you need to separate scope by business unit, subsidiary, environment, or client engagement.

Creating a project​

Go to Projects and click Create Project (also available from the project switcher in the top navigation). Fill out the form:

  • Logo — optional image (JPEG, PNG, GIF, or WebP).
  • Name — required, 3–255 characters.
  • Description — optional, up to 1000 characters.
  • Move assets to project — optional. Pick from your organization's existing assets to move them into the new project immediately; you can always assign assets afterward from Assets.

Creating and deleting projects requires the Organization Admin role.

Switching between projects​

The project switcher in the top navigation shows your current project and lets you search and jump to another one. Selecting All Projects clears the scope so pages like Assets, Agents, and Scans show everything across your organization instead of a single project.

Each user can mark one project as their default — from a project's detail page, click Make Default. Your default project is what HoundER falls back to when no project is otherwise selected (for example, right after logging in).

Project detail​

Clicking into a project opens its detail page, organized into tabs:

Assets​

Lists the assets assigned to this project, along with their tags, per-type finding counts, and scan status. Manage Assets takes you to the full Assets page, scoped to this project.

Workflows​

Workflows are automation rules that notify you by email, Slack, or Microsoft Teams when specific findings occur. See Workflows for triggers, conditions, and actions.

Settings​

Edit the project's logo, name, and description. Organization Admins also see a Danger Zone to delete the project — this is permanent and also deletes all of the project's assets, findings, agents, reports, and scans. You can't delete your current default project; make another project the default first.

Scanning​

Visible to Organization Admins and Project Admins. Toggle Enable scanning to pause or resume continuous scanning for every asset in the project. Disabling it:

  • Stops new scans (continuous or recurring agent scans) from being scheduled for the project's assets.
  • Does not cancel scans that are already running.

While scanning is paused, a banner appears on the project's pages (and on Assets/Agents when that project is selected) linking back to this tab.

Roles​

  • Organization Admin — full control: create, edit, and delete any project, and manage settings, scanning, and workflows within it.
  • Project Admin — full control within the project(s) they're assigned to (settings, scanning, workflows), but can't create new projects or delete existing ones.
  • Other roles can work within a project's scope (assets, agents, scans, findings) without seeing the Projects list itself.