Enterprise Quickstart

Get your enterprise organization up and running. --- Before starting, ensure you have: - Signed Enterprise contract - Admin contact designated - SSO details...

Last updated: January 14, 2026

Enterprise Quickstart

Get your enterprise organization up and running.

Pre-requisites

Before starting, ensure you have:

  • Signed Enterprise contract
  • Admin contact designated
  • SSO details (if using)
  • Team structure planned

Phase 1: Account Setup

1. Create Organization

Your account manager will:

  1. Create your Enterprise organization
  2. Add initial admin user
  3. Configure plan settings
  4. Enable Enterprise features

2. Admin Access

First admin receives:

  • Welcome email
  • Temporary password
  • Organization admin access
  • Getting started resources

3. Configure Organization

As admin:

  1. Log in to BlockSecOps
  2. Go to Settings → Organization
  3. Update:
    • Organization name
    • Company details
    • Logo (for reports)
    • Default settings

Phase 2: Identity Setup

Without SSO

Use email invitations:

  1. Go to Settings → Team
  2. Click Invite Members
  3. Enter email addresses
  4. Assign roles
  5. Send invitations

With SSO

Configure SSO first:

  1. Configure SSO
  2. Test with admin accounts
  3. Enable for organization
  4. Members authenticate via SSO

Phase 3: Team Structure

Create Teams

Organize by function:

  1. Go to Teams → Create Team
  2. Configure:
    • Name: "Smart Contract Auditors"
    • Members: Add team members
    • Projects: Assign access
  3. Repeat for other teams

Suggested Structure

Organization
├── Security Team
│   ├── Senior Auditors
│   └── Auditors
├── Development
│   ├── Frontend
│   └── Backend
└── Management
    └── Executives (Viewer access)

Assign Roles

Role Access Best For
Owner Full + billing Organization lead
Admin Full management Team leads
Member Standard access Contributors
Viewer Read-only Stakeholders

Phase 4: Project Setup

Create Projects

Organize by purpose:

  1. Go to Projects → Create
  2. Configure:
    • Name
    • Description
    • Team access
    • Settings

Project Templates

Common structures:

  • By Client: Each client gets a project
  • By Product: Each product/protocol
  • By Environment: Dev, Staging, Production

Phase 5: Integrations

API Keys

Create organization-wide keys:

  1. Go to Settings → API Keys
  2. Create keys for:
    • CI/CD pipelines
    • Automation scripts
    • Reporting tools

Webhooks

Configure notifications:

  1. Go to Settings → Webhooks
  2. Add endpoints for:
    • Slack/Teams
    • Ticketing (Jira)
    • SIEM

CI/CD

Connect your pipelines:

  1. Add API key to CI secrets
  2. Configure scan step
  3. Set failure thresholds

Phase 6: Policies

Scan Policies

Set organization defaults:

  1. Go to Settings → Policies
  2. Configure:
    • Default preset
    • Required scanners
    • Failure thresholds
    • Retention period

Access Policies

Configure security:

  1. Session timeout: 8 hours
  2. 2FA requirement: All admins
  3. IP allowlist: Optional
  4. API key expiry: 90 days

Phase 7: Training

Admin Training

Your CSM provides:

  • Platform walkthrough
  • Admin features
  • Best practices
  • Q&A session

User Training

For team members:

  • Self-paced documentation
  • Video tutorials
  • Office hours
  • Support access

Phase 8: Go Live

Pilot Group

Start with small group:

  1. Select pilot team
  2. Run initial scans
  3. Gather feedback
  4. Adjust configuration

Full Rollout

Once validated:

  1. Announce to organization
  2. Send access instructions
  3. Provide support contacts
  4. Monitor adoption

Ongoing Management

Regular Tasks

Task Frequency
Review access Monthly
Rotate API keys Quarterly
Audit logs review Weekly
Usage reporting Monthly

Support

Your dedicated team:

  • CSM: Strategic guidance
  • TAM: Technical support
  • Support: Issue resolution

Checklist

Week 1

  • Organization created
  • Admin access confirmed
  • SSO configured (if using)
  • Initial team invited

Week 2

  • Teams created
  • Projects set up
  • Integrations configured
  • Policies defined

Week 3

  • Admin training complete
  • User training scheduled
  • Pilot group identified
  • Initial scans run

Week 4

  • Pilot feedback collected
  • Adjustments made
  • Full rollout planned
  • Go live!

Getting Help

Your Contacts

  • Account Manager: Contract, billing
  • Customer Success: Adoption, best practices
  • Technical Account Manager: Technical issues
  • Support: Day-to-day questions

Resources

  • Documentation (you're here!)
  • Training videos
  • Office hours
  • Support portal

Next Steps