# Secure your team

- URL: https://betteranalyst.com/docs/teams/secure-setup
- Updated: 2026-11-17
- Author: Better Analyst

A checklist for Better Analyst team owners and admins, in order, from sign-in and roles to data access, private projects, and the audit log.

This page is one path through every security setting a team owner or admin should look at. Each step links to the full guide for that setting. Steps marked **Enterprise** need the Enterprise plan; the rest work on **Team** and **Enterprise**.

## 1. Protect the owner account

The team **Owner** is the only person who can change roles, single sign-on, and sign-in requirements, so start there.

- Turn on two-factor authentication with an authenticator app, and keep the recovery codes somewhere safe. Two-factor is available on every plan.
- Requiring SSO later also needs two-factor on the owner's own account, so the team can't be locked out if the identity provider has a problem.

## 2. Verify your domains and connect SSO (Enterprise)

In **Team settings → Security**:

1. Add a TXT record to your DNS to verify each email domain. Keep the record in place; it's re-checked daily.
2. Connect Okta, Microsoft Entra ID, Google Workspace, or any SAML 2.0 identity provider.
3. Run **Test sign-in**, then **Turn on SSO**.

See [SSO and SCIM](https://betteranalyst.com/docs/teams/sso-scim).

## 3. Let your identity provider manage people (Enterprise)

Create a SCIM token in the Security tab and add it to your identity provider. People are then added to the team and removed from it from one place, and removing someone ends their sessions. See [SSO and SCIM](https://betteranalyst.com/docs/teams/sso-scim).

## 4. Set sign-in requirements (Enterprise)

Choose **Require SSO**, **Require two-factor authentication**, or both. They apply in the web app, the API, the add-ons, and the ChatGPT plugin, and the database enforces them too. See [Sign-in requirements](https://betteranalyst.com/docs/teams/sso-scim#sign-in-requirements).

## 5. Give each person the smallest role that works

| Role | Use it for |
| - | - |
| Owner | One person. Security, roles, and ownership. |
| Admin | People who run the team day to day: members, Slack, data access. |
| Member | People who ask questions and build chats, dashboards, and tasks. |
| Viewer | People who only open the team's dashboards. Viewers are free. |

See [Roles & Permissions](https://betteranalyst.com/docs/teams/roles-permissions) and [Inviting Members](https://betteranalyst.com/docs/teams/inviting-members).

## 6. Decide what the AI can read on each source

For each team data source, open **Data access** and choose which tables and columns the AI may use, and add row filters that apply to every question. You can make a trusted member an **access manager** for one source without making them an admin. See [Data Access](https://betteranalyst.com/docs/my-data/data-access).

## 7. Show each person only their own rows

If several people share one database connection, give each member attributes such as region or client, then use them in the source's row filters. Use **Preview as member** and **Ask a test question as** to check what someone will see before they do. See [Set up per-member data access](https://betteranalyst.com/docs/teams/per-member-data-access) and [Member Attributes](https://betteranalyst.com/docs/teams/member-attributes).

## 8. Keep sensitive work in private projects

Limit a project to chosen members so nobody else sees its chats, dashboards, Data Flows, alerts, or tasks, in the app, in Slack, or in emails. A data source can be kept to that one project. See [Private projects](https://betteranalyst.com/docs/teams/private-projects).

## 9. Review the audit log

**Team settings → Audit log** records sign-ins, member and role changes, SSO and provisioning changes, data access changes, sharing, exports, and deletions, with the person, time, and IP address. Team shows the last 30 days; Enterprise keeps the full history with CSV export. Look at it after any change above, and on a regular schedule. See [Audit Log](https://betteranalyst.com/docs/teams/audit-log).

## For your security review

The [Security page](https://betteranalyst.com/security) lists every control in one place, with a plan-by-plan table and answers to common questionnaire questions. Our [DPA](https://betteranalyst.com/dpa) and [subprocessors](https://betteranalyst.com/subprocessors) are public. For a questionnaire or a signed DPA, [contact us](https://betteranalyst.com/contact?plan=enterprise).
