BIZROW SECURITY

Your data. Your people.
Your peace of mind.

BUILT INTO YOUR WORKSPACE

Less guesswork.
More control over your data.

Understand the safeguards behind everyday work, from signing in to sharing responsibility across your team.

01 / ACCOUNT PROTECTION

Your password stays a secret.

Account passwords are stored as salted bcrypt hashes. When you sign in, Bizrow checks your password against its hash instead of storing a readable copy.

One-way password hashing
02 / ACCESS CONTROL

The right access. For the right people.

Set role-based permissions and user-specific overrides for your modules. Control viewing, creating, editing, deleting, importing, and exporting to match each person's responsibilities.

Permissions checked on the server
03 / WORKSPACE BOUNDARIES

A workspace with clear boundaries.

Authenticated requests carry workspace context. Tenant-aware data access helps keep your company's records separate from other workspaces.

Workspace-aware data access
A CHOICE THAT MATTERS

Your data. A setup that fits.

Start with Bizrow-managed storage or connect a supported external MongoDB data source. Choose with a clear understanding of access and responsibilities.

KEEP IT SIMPLE

Use Bizrow-managed storage

Work with the database setup provided for your Bizrow workspace, with authenticated access and configurable team permissions.

  • Keep CRM workflows in one workspace
  • Manage access through roles and modules
  • Discuss storage and backup requirements with us
BRING YOUR DATA SOURCE

Connect your own MongoDB

Connect supported external collections to CRM workflows while your team manages the database infrastructure and provider settings.

  • Use a supported MongoDB connection
  • Scope database credentials to what is needed
  • Plan network access, backups, and recovery

Connection support depends on your workflow and configuration. Find the right setup with our team

SECURITY IS A SHARED PRACTICE

Good controls.
Thoughtful habits.

We build access checks into the application. Your team brings them to life through careful configuration and regular reviews.

Visit the help center
  1. 01

    Give access with intention

    Start with the permissions each person needs. Review roles and record access when responsibilities change.

  2. 02

    Keep accounts and connections private

    Use unique passwords. Keep database credentials and access tokens out of shared documents and messages.

  3. 03

    Review, test, and improve

    Remove access when people leave. Confirm your database backup arrangements and test important permission settings before rollout.

CHECKS THAT SUPPORT TRUST

Security needs evidence.

Our codebase includes automated regression checks for workspace sessions, tenant boundaries, protected routes, and permission handling. Ask us about the controls relevant to your deployment and the evidence your team needs to review.

Automated checks do not establish certification or replace an independent security audit.

CLEAR ANSWERS

CRM security,
explained.

Questions about your requirements?

Talk to a real person
How does Bizrow protect my password?

Bizrow uses salted bcrypt password hashing. Hashing is a one-way process, unlike reversible encryption. Sign-in checks compare the submitted password with the stored hash.

Can I connect my own database?

Bizrow supports connections to external MongoDB data sources for supported CRM workflows. You can also use Bizrow-managed workspace storage. Contact our team to confirm which setup fits your modules, hosting requirements, and plan.

Can I control what team members see and change?

Yes. Administrators can configure module permissions and user-specific overrides. Permissions cover viewing, creating, editing, deleting, importing, and exporting; supported record scopes can further limit access.

Is choosing my own database enough to secure my data?

Database location is one part of security. With your own database, your team also needs to manage database credentials, network access, backups, and provider settings. Discuss these responsibilities with us before connecting production data.

How are security-related features tested?

The codebase includes automated checks for workspace sessions, tenant boundaries, permission handling, and protected routes. These checks help catch regressions; they are not a substitute for an independent security audit.

How do I report a security issue?

Email hello@bizrow.app with the affected page, a description, and steps to reproduce the issue. Redact screenshots and never include passwords, database credentials, access tokens, or customer records.

A SAFER COMMUNITY STARTS WITH A CONVERSATION

See something? Tell us.

If you notice unexpected access or a potential vulnerability, help us investigate. Send the steps to reproduce it, with sensitive information removed.