Integrating SailPoint with Baserow
Baserow is an open-source no-code database tool and Airtable alternative. It helps teams manage data by providing a collaborative platform that combines the ease of a spreadsheet with the power of a relational database, allowing users to build custom applications and automate workflows without writing code. This document provides instructions to configure a new direct connection to a Baserow source. For a reference to the terminology specific to SailPoint products, refer to Source and Connector Definitions.
Note
To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the SaaS Release Notes page.
Supported Features
The Baserow connector supports the following:
Account Management
- Aggregate Accounts
Entitlement Management
- Aggregate Roles
Important
Quick Compliance connectors have the following manual aggregation limits within a 24-hour period:
- Organization Admins: Limited to 3 manual account or entitlement aggregations per day per source. This limit is cumulative across all admins in the organization.
- Regular Users: Limited to 1 manual account or entitlement aggregation per day per source.
These limits ensure that individual compliance statuses are kept up to date while maintaining continuous compliance monitoring. If you need to run additional aggregations beyond these limits, contact SailPoint Support.
Supported Managed Systems
- Baserow: SaaS (api.baserow.io) and self-hosted versions
Prerequisites
Ensure the following prerequisites are met before proceeding with the configuration:
- Access to a Baserow account (SaaS or self-hosted) with administrative or member permissions for the specific workspace containing the databases you intend to manage.
- For more information, refer Baserow Backend API (REST API) for workspace-related endpoints, generating tokens, and the full API specification.
Required Permissions
- The connector uses API Token Authentication (and OAuth 2.0 for enterprise SSO integrations) to securely interact with your Baserow data. To ensure the connector can sync your workspaces, databases, and tables, you must generate an API token with the specific scopes listed in the following table.
- API Scopes Required:
| Scope | Description |
|---|---|
| create | Required to create new databases, tables, fields, or rows through the API |
| read | Required to list workspaces, view database structures, and retrieve row data |
| update | Required to modify existing table schemas, update field names, or edit record values |
| delete | Required to remove records, tables, or other resources from the workspace |
Advanced Access Control (RBAC)
If you’re using Baserow Enterprise, permissions are further governed by Role-Based Access Control. Ensure the user associated with the API token is assigned one of the following roles at the workspace or database level:
- Admin - Full access to all operations
- Builder - Can modify structure and data (required for create, read, update, delete)
- Editor - Can modify data but not structure (required for row-level read, update)
-
Viewer - Read-only access (restricts token to read scope only)
Note
Only Admin can fetch roles. Builder, Editor, and Viewer cannot fetch roles. All roles (Admin, Builder, Editor, and Viewer) can generate tokens and fetch users.
-
Configuration Steps:
- Sign in to your Baserow account.
- Go to Settings > API Tokens.
- Create a new token and select the relevant workspace.
- Select the create, read, update, and delete scopes based on your integration needs.
- Copy the generated token for use in the connector setup.
For more information about token management and security best practices, refer the Baserow API Documentation.
Note
The linked document is not maintained by SailPoint and is subject to change without notice.