Baserow

Overview

The Baserow integration connects your Baserow workspaces to Oneleet, syncing workspace members as user account assets. This lets Oneleet track who has access to your Baserow workspaces and whether they protect their accounts with two-factor authentication.

What does Oneleet monitor?

• Baserow workspace members (user accounts), including their role in each workspace, whether they have two-factor authentication enabled, whether they have scheduled their account for deletion, and, when the connection account is an instance admin, whether an admin deactivated them

Setup

To set up the Baserow integration, navigate to Integrations > Add integration > Baserow.

Baserow’s API has no key that can read workspace members, so Oneleet signs in with the email and password of a dedicated Baserow account. The account only needs the Viewer role in each workspace you want to monitor.

1. Sign up for a new Baserow account at baserow.io/signup (or on your self-hosted instance), using an address such as [email protected], and confirm the email address with the link Baserow sends.
2. As an admin of each workspace you want to monitor, open the workspace, click Members, then Invite members, and invite the account with the Viewer role. See Invite users to workspace.
3. Sign in as the new account and accept the invitations.
4. In Oneleet, enter the API hostname (api.baserow.io for Baserow Cloud, or your self-hosted instance’s hostname) and the account’s Email and Password, then click Connect.

Don’t enable two-factor authentication on this account: Baserow then requires a one-time code at every sign-in, which Oneleet can’t provide. Oneleet excludes this account from the two-factor authentication check. Changing its password disconnects Oneleet until you update it in Oneleet. Self-hosted instances that disable email and password logins can’t be connected.

Known limitations

Baserow only shows whether a user is deactivated to instance admins (staff). Unless the connection account is an instance admin of your self-hosted Baserow, users an admin deactivated appear as active and are still checked for two-factor authentication. On Baserow Cloud, customers aren’t instance admins, so remove users from your workspaces instead of relying on deactivation.