Skip to content

Onboarding Walkthrough

When you create a new organization in Fencer, a guided onboarding flow helps you configure essential security capabilities step by step. The flow consists of an initial setup wizard followed by an ongoing Onboarding Checklist on your Home page that tracks your progress across up to ten key areas.

  • You have created a Fencer account and an organization.
  • You have admin access to the organization.

The onboarding experience has two phases. First, a setup wizard walks you through initial configuration — entering your company domain, inviting team members, and optionally scheduling an onboarding call. Once completed, you land on the Home page, where a checklist tracks your progress across all major platform capabilities.

Each checklist item is either not started, in progress (shown only for domain scanning, while the domain you added is not yet verified), completed (the integration is connected, the asset exists, or the action is done), or marked as done by an Administrator. Fencer detects completion automatically — you do not need to mark items as done yourself.

The setup wizard runs when your organization is first created, and Fencer keeps you on it until you finish or skip its last step. It has three steps:

  1. Tell us more! — Enter your apex domain (Your domain), choose a Company size, and answer How did you hear about us?, then click Continue. Fencer adds the domain and immediately starts a domain scan to begin discovering security issues.
  2. Invite your team — Choose a Role and add email addresses for colleagues you want to invite, then click Invite & continue. Invitations are sent in one batch. Click Skip to invite people later.
  3. Schedule a call with us — Optionally book an onboarding call with the Fencer team, then click Proceed to dashboard. Click Skip for now to go directly to the Home page.

After completing or skipping the wizard, you are redirected to the organization’s Home page. If you skipped the call, the sidebar footer shows a reminder with a Schedule it now link; an Administrator can close it for good.

The Onboarding Checklist appears on the Home page for users who can edit organization settings and connect integrations (Administrators by default). It shows your progress as a count (for example, 3 / 10) and includes the following items:

#ItemDescriptionEst. Time
1Setup Code ScanningConnect the GitHub integration to scan your codebase for vulnerabilities and issues.5min
2Setup Infrastructure ScanningConnect a cloud provider (AWS, GCP, Azure, Cloudflare, DigitalOcean, Heroku, Render, or Snowflake) to inspect infrastructure for misconfigurations.5min
3Review Architecture DiagramReview your auto-generated architecture diagram. Completed the first time someone opens a completed diagram.2min
4Setup Domain ScanningAdd and verify a domain to analyze for security risks.5min
5Setup Web Application ScanningAdd a web application to scan for vulnerabilities.5min
6Setup Security MonitoringConnect AWS or GitHub monitoring integrations for SIEM log ingestion. Shown only when your plan includes SIEM.5min
7Automate Compliance Evidence CollectionConnect Drata or Vanta to automate compliance reporting. Shown only when your plan includes GRC integrations.2min
8Setup NotificationsConnect Slack, or add an organization notification rule that sends email.2min
9Setup Workflow IntegrationConnect Linear or Jira to create and track tasks for vulnerabilities.2min
10Fix a VulnerabilityResolve at least one detected vulnerability to improve your security posture.5min

Integration items show a badge for each integration that completes them, with a check mark once it is connected. Their Setup button opens the Integration Settings dialog for that capability. The other items link to the relevant page: Review opens Assets, Setup opens Posture > Domains or Posture > Application, and Explore Vulnerabilities opens the open vulnerabilities list.

Use the arrow button next to the title to collapse or expand the checklist. The checklist disappears once every item is completed or marked as done.

Administrators can mark any checklist item they do not plan to complete as done. A marked item counts toward overall progress and hides its action button. To mark or restore an item:

  1. Go to the Home page where the onboarding checklist is displayed.
  2. Click the status circle next to the item you want to skip (its tooltip reads Mark as done).
  3. To restore a previously marked item, click the same circle again (Click to undo.) — it returns to its actual status.

If you no longer need the checklist, click Dismiss in its header and confirm. This hides the checklist from your own Home page only; other Administrators still see it, and you can still complete the remaining steps from their respective settings pages.

Reading the progress count:

Progress is a simple completed/total count. For example, if your plan includes SIEM and GRC integrations and you have connected GitHub for code scanning, verified a domain, and marked the compliance item as done, your progress shows 3 / 10.

Typical first-session flow:

  1. Sign up and create an organization.
  2. Enter your company domain (e.g., example.com) — a domain scan starts automatically.
  3. Invite two teammates by email.
  4. Click Skip for now on the call scheduling step.
  5. On the Home page, click Setup on “Setup Code Scanning” and connect GitHub.
  6. The code scanning item automatically shows as completed.
  7. Mark “Automate Compliance Evidence Collection” as done if you do not use Drata or Vanta.
  • Checklist does not appear on the Home page: The checklist is only shown to users who can edit organization settings and connect integrations, and only until every item is complete or marked as done. It also stays hidden if you dismissed it. If you see the wizard steps instead, complete or skip them first.
  • Item shows as in progress but not completed: Domain scanning requires full verification — simply adding a domain is not enough. Add the DNS TXT record shown on the domain and wait for verification to finish.
  • Cannot mark an item as done: Only users who can edit organization settings can mark items. Ask an Administrator, or check your role on Admin > Team.