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.
Understand the safeguards behind everyday work, from signing in to sharing responsibility across your team.
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.
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.
Authenticated requests carry workspace context. Tenant-aware data access helps keep your company's records separate from other workspaces.
Start with Bizrow-managed storage or connect a supported external MongoDB data source. Choose with a clear understanding of access and responsibilities.
Work with the database setup provided for your Bizrow workspace, with authenticated access and configurable team permissions.
Connect supported external collections to CRM workflows while your team manages the database infrastructure and provider settings.
Connection support depends on your workflow and configuration. Find the right setup with our team
We build access checks into the application. Your team brings them to life through careful configuration and regular reviews.
Visit the help centerStart with the permissions each person needs. Review roles and record access when responsibilities change.
Use unique passwords. Keep database credentials and access tokens out of shared documents and messages.
Remove access when people leave. Confirm your database backup arrangements and test important permission settings before rollout.
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.
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.
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.
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.
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.
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.
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.
If you notice unexpected access or a potential vulnerability, help us investigate. Send the steps to reproduce it, with sensitive information removed.