Secure your app: an overview
The layers that protect a Tadabase app, from your builder account to sign-in rules, page and record security, files and logs, with a pre-launch checklist.
- Verified Nov 17, 2026
- Classic builder
On this page
Use this page as a map of the security settings in a Tadabase app: what each layer protects, and where to set it up. Start here before you launch an app or let real users in.
Security is shared #
Tadabase secures the platform: hosting, databases, and the controls described below (see Security for how). You decide how your app uses them: who can sign in, which pages and records each role gets, and who can change the app in the builder. An app is only as safe as those settings.
The protection layers #
| Layer | What it does | Where to read more |
|---|---|---|
| Builder account | Emailed codes at builder sign-in, an email on each sign-in, and a list of your sessions you can end | Secure your Tadabase builder account |
| Builder sharing | Give team members their own access to the builder instead of sharing a login | Sharing your app builder |
| Login methods and password rules | Email and password, magic links and single sign-on; password complexity, expiry and reuse rules | Login methods, Single sign-on, Magic links, Password rules |
| Two-factor sign-in for app users | Asks app users for an emailed code when they sign in (Business Starter, Growth, Pro and Elite plans) | Login methods |
| Sessions and login logs | See who signed in, failed logins, blocked users and active sessions, and end a session | User logs |
| Auto logout | Signs users out after a set time away from the app | Log users out automatically after inactivity |
| IP restrictions | Lets only listed addresses open the live app, or blocks them (Business Pro and Elite plans) | Allow or block app access by IP address |
| Page and layout security | Decides which roles can open each page and layout | Pages, Layouts |
| Record-level security | Filters each table's records and fields per role or user, in the app and the API (Business Starter, Growth, Pro and Elite plans) | Control which records each user can see |
| Field and component visibility | Hides fields, values or components based on the record or the logged-in user | Display rules, Roles |
| Secure files | File fields with Secured on, with downloads limited to roles or to the connected user, and a log of file access | Attachments field, File logs |
| Logs | Record changes, deleted records, page views, files and more. How long logs are kept depends on your plan. | Record history, User logs |
| Backups | Restore the app or its data after a mistake | Backing up and restoring your app |
| HIPAA | Hosting for health information under a signed BAA | Build HIPAA-compliant apps |
Before you launch #
- Turn on Require Two Factor Authentication (2FA) for your own builder account and ask everyone you share the builder with to do the same.
- Set password rules for app users under Settings > User Settings.
- Turn on two-factor sign-in for app users if your plan includes it, at least for admin roles.
- Set App Auto Logout to a time that fits how sensitive the data is.
- If users work from known networks, use IP Security to allow only those addresses.
- Check the Security tab of every page and layout that shows private data.
- Turn on row level security for tables where users must only see their own records, and test it with View Permissions As.
- Turn on Secured for file fields that hold private documents.
- Turn on record change and delete logging for important tables.
- Confirm that backups run, and try a restore.
- Sign in to the live app as a test user of each role and check what they can see.
Was this page helpful?
Something wrong or missing on this page? Tell us.