Separate identity from authorization
Identity answers who signed in; authorization answers which customer records may be accessed. Map external, internal and administrative scopes. Inspect whether data access is restricted rather than merely hidden visually, using the actual product documentation and a suitable test.
Inspect builder and integration authority
Baserow’s official application guidance describes the relationship between an integration account and builder editors. Inspect the creator’s scope as well as end-user access. Do not automatically reuse an unnecessarily broad administrative connection behind an external interface.
Define permitted changes separately
Read-only progress and editing contact details or files are different permissions. Define whether a change needs review or may be returned. Include a test that changing an entered customer identifier or URL parameter does not select another customer’s records.
A hypothetical two-customer access test
Create disposable fictional customers A and B with separate test identities and records. Check that A cannot access B’s list, detail or files and that internal staff retain only the required scope. Perform this before publication with synthetic data rather than exposing real customer material during an experiment.
Compare the architecture, not a portal label
A setup may combine Baserow application data, an Airtable internal register or Windmill execution, but those are not identical portal offerings. Identify which component handles identity, interface, storage and action authority, then verify the required paid controls instead of assuming a generic portal label supplies them all.
Plan offboarding and migration
Separate revoking access from appropriate retention of business records. Include shared links, file URLs and integration identities. On migration, transfer the customer-to-record and authorization specification alongside values, then repeat the two-customer test on the new implementation.
Test details and files as well as the list
Hiding fictional customer B from A’s list is not sufficient if a direct detail or file link still works. Inspect alternative entry routes rather than only visible navigation. Repeat the test after user additions, permission changes and offboarding. Synthetic records for two fictional customers can establish the required boundary without exposing real customer information during evaluation.
Estimate costs for your workload
Enter monthly jobs, billable steps and retries to see how different billing units affect your estimate.
Open cost calculatorOfficial sources
Pricing, availability and feature limits can change. Check the linked official pages before subscribing.
- Baserow application user sourcesInformation checked: 2026-10-28
- Baserow application settings and integration accessInformation checked: 2026-10-28
- Baserow pricingInformation checked: 2026-10-28
- Airtable plans overviewInformation checked: 2026-10-28
- Windmill plans and upgrade scopeInformation checked: 2026-10-28
- Baserow subscriptions overviewInformation checked: 2026-10-28
- Baserow table exportInformation checked: 2026-10-28
- Airtable pricingInformation checked: 2026-10-28
- Airtable billable collaboratorsInformation checked: 2026-10-28
- Windmill pricing and computeInformation checked: 2026-10-28
- Windmill jobs and cancellationInformation checked: 2026-10-28