> For the complete documentation index, see [llms.txt](https://boundaryai.gitbook.io/boundaryai-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boundaryai.gitbook.io/boundaryai-docs/account-and-administration/updating-settings.md). # Settings Settings is where you manage your personal account, your organisation, who has access to it, which add-ons are enabled, and how much capacity you have left. Everything that lives outside an individual survey or feedback group lives here. This page walks through every section you'll find in Settings and what each one is for. For configuration that lives inside a specific dataset (per-survey appearance, per-survey rotation, per-survey passcode), see [Customizing a Survey](/boundaryai-docs/bringing-in-your-feedback/surveys/images-and-media.md). *** ### Where to find Settings Open **Settings** from the main navigation. You'll land on a page with three sections: * **Organization access**: the add-ons enabled for your organisation. * **Usage**: your current capacity (how much you've used, how much is left). * **Account**: your personal profile, your organisation's details, report designs, and the in-app walkthrough. A few related surfaces live next door: your **Profile**, **Organisation details** for the workspace, and the **Integrations** hub for connections, AI assistants, API keys, and webhooks. Settings is the central jumping-off point for all of them. *** ### Organization access BAI Analytics has no self-serve plans. Every organisation is set up by the BAI Analytics team, and what you can do is governed by the **add-ons** enabled for it and the allowances attached to it. The **Enabled add-ons** panel lists everything switched on for your organisation, each as a badge. The panel's own wording explains the model: > Add-ons enabled for your organization, with your monthly usage allowances shown below. Contact your BAI Analytics representative to enable add-ons or adjust allowances. The add-ons you may see here include: | Add-on | What it unlocks | | -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Reports & scheduled delivery** | Generate, save, schedule, and deliver [reports](/boundaryai-docs/analysing-your-feedback/reports.md). Enabled by default for new organisations. | | **Custom monitors** | Create reusable monitors and analyse the comments that match them ([Custom Monitoring](/boundaryai-docs/analysing-your-feedback/custom-monitoring.md)). Enabled by default. | | **Monitor notifications** | Email or SMS notifications when monitors find matching feedback. Enabled by default. | | **Connected platforms & API** | Connect support and CX tools, data warehouses, API keys, and webhooks ([Connecting your tools](/boundaryai-docs/bringing-in-your-feedback/connect-to-your-existing-systems.md)). | | **Web & social monitoring** | Recurring scraping agents that collect feedback from websites and social sources ([Social Listening](/boundaryai-docs/bringing-in-your-feedback/social-listening.md)). | | **AI Visibility** | Track brand visibility and share of voice across AI models ([AI Visibility](/boundaryai-docs/bringing-in-your-feedback/ai-visibility.md)). | | **Survey expert mode** | Advanced survey authoring controls. | | **White-label surveys** | Remove BAI Analytics branding from hosted surveys and widgets. | | **Custom report designs** | Reusable branded report templates and custom layouts. | Some organisations also carry client-specific add-ons (for example custom report templates built for a particular programme); they appear in the same list. If no optional add-on is enabled, the panel says **No optional add-ons enabled.** Surfaces that depend on an add-on you don't have are simply not available. To add one, or to change an allowance, contact your BAI Analytics representative. *** ### Usage The Usage section shows two cards side by side: your **Usage Allowance** and your **Web & Social Media Credits**. Both are how BAI Analytics meters your work, but they apply to different things. #### Usage Allowance This is your AI budget for the platform's analytical work: generating themes, scoring sentiment, running Custom Monitoring, summarising responses, translating, producing AI insights, and AI-based PII redaction. Every time the platform analyses a piece of feedback, it consumes a small amount of your allowance. You'll see: * **The number of credits remaining**, displayed prominently. * **A battery-style bar** that starts full at the beginning of each period and drains as credits are used. * **Remaining / total** and a **Resets** date: when the next monthly allowance lands. Hover the info icon for **What counts as 1 credit?**: one credit equals a fixed number of tokens of AI work, so short responses use a fraction of a credit and longer or more complex ones use more. The card has a **View usage** link that opens the **AI usage** page. Pick a range (**Current billing period**, **Last 7 days**, **Last 30 days**, **Last 90 days**) to see **Usage by feature** (theme detection, sentiment, summaries, monitor generation, report generation, translation, PII redaction, and so on) and **Recent activity**, the latest AI calls with the feedback group and data source they ran on. Failed calls are not billed. {% hint style="info" %} Getting close to your limit? Contact your BAI Analytics representative; allowances are adjusted to fit your actual workload. {% endhint %} #### Web & Social Media Credits This card appears when the **Web & social monitoring** add-on is enabled. It is a separate balance, used only by **scraping agents**: the agents that collect public feedback from Trustpilot, Google Reviews, X, Reddit, Google News and the rest of the supported platforms. Each agent run consumes credits from this pool, never from your Usage Allowance. From the card you can: * See the **current balance**. If your organisation has a monthly credit allocation, the card also shows the amount per month and the date of the next top-up. * Open the **History** to inspect every top-up, every agent run, and every refund (failed runs refund credits automatically). * Click **Add** to buy credits in fixed packages (25 / 50 / 100 / 250 / 500 / 1,000 credits, where 1 credit = $1 USD). You are redirected to a secure Stripe checkout and the balance refreshes when you return. #### Auto top-up Auto top-up keeps scraping agents running without buying credits by hand every time the balance gets low. You'll find it in the scraping agent wizard, just below the agent's schedule. The panel explains it like this: > Automatically add credits when the balance drops below a threshold Set these two values: * **Top up when balance is below** * **Add per top-up** Auto top-up requires a payment method on file. If no card is saved, the panel shows **Set up a payment method to enable auto top-up.** You can update or remove the saved card from the same panel. See [Social Listening](/boundaryai-docs/bringing-in-your-feedback/social-listening.md) for what credits cost per run. *** ### Account The Account section has up to four quick links. #### Profile Click **Your account** to manage your personal account. The Profile page covers everything that's specific to *you*, regardless of which organisation you're in: * **Personal details**: your name, profile picture, and contact email. * **Email addresses**: add a secondary address, change which one is primary, and re-verify if needed. * **Sign-in & security**: * Change your password. * Enable two-factor authentication. * View and revoke active sessions on devices you no longer use. * Connect or disconnect sign-in providers (Google, Microsoft, etc.) where your organisation allows them. * **Language & Timezone**: your personal display language for the BAI Analytics interface, and the timezone used to render dates and times for you. * **Cookie Consent**: allow or reject cookies (see [Log into your account](/boundaryai-docs/getting-started/login.md#cookie-preferences)). The same settings open from your avatar menu (**Manage account**) anywhere in the app. After you save a new language, the account window closes on its own and the app reloads in the language you chose. These settings only affect your own experience. They do not change how surveys appear to respondents. That's controlled per survey, in Customizing a Survey. #### Organisation details Click **Organization details** to manage your workspace. The page opens on the organisation's general tab, with an **organisation switcher** in the header if you belong to more than one workspace. What you can do here depends on your role: * **Edit the organisation name**: the new name appears across the app and in shared report headers. * **Manage members**: see who's in the workspace, invite new people, change roles, and remove members. Member management is **admin-only**. * **Switch organisations**: if you belong to more than one, the switcher lets you flip between them; the workspace context (surveys, feedback groups, add-ons, members, credits) reloads to match the active organisation. * **Analysis settings**, **PII redaction**, and **Email sending**: organisation-wide tabs described below. You rarely need the switcher to land in the right place. When you accept an invitation, BAI Analytics opens the organisation you were invited to. When you open a link to a feedback group, analysis, or source that belongs to another organisation you are a member of, BAI Analytics switches for you and shows a **Switched to {organisation}** notice. If you belong to more than one organisation, use [Organization Hub](/boundaryai-docs/account-and-administration/organization-hub.md) for the cross-workspace view: switching, searching, bulk invites, and exports across all your organisations. #### Report designs When the **Custom report designs** add-on is enabled, a **Report designs** link takes you to your organisation's report templates and layouts. See [Reports](/boundaryai-docs/analysing-your-feedback/reports.md). #### Replay walkthrough Click **Show onboarding walkthrough again** to re-run the in-app onboarding tour. This is useful when you're showing BAI Analytics to a new teammate, or when you skipped onboarding the first time and want to revisit it. The walkthrough is per-user, so triggering it doesn't show the tour to anyone else in the workspace. *** ### Analysis settings Open **Organization details** and switch to the **Analysis settings** tab. These two switches decide how comments are assigned to themes and monitors in new analyses, for everyone in your organisation: * **Multiple themes per comment**: count a comment in every theme, sub-theme and grouped sub-category it mentions, not just the closest match. Totals can exceed the number of comments. * **Multiple monitors per comment**: match a comment to every monitor and sub-category it satisfies, not just the most relevant one. Totals can exceed the number of comments. Both apply to new analyses only. Everyone can see the tab; only organisation admins can change it. *** ### PII redaction Open **Organization details** and switch to the **PII redaction** tab to remove personal information from feedback as it arrives, before it is stored or analysed. It applies to survey responses, uploads, connected platforms, and scraped reviews. {% hint style="warning" %} Redaction is permanent: the original text is never kept. It applies to feedback that arrives after you save; feedback already stored is unchanged. {% endhint %} Two mechanisms are available, and you can enable either or both: * **Pattern-based redaction**: fast and deterministic. Tick the **Premade patterns** you want (**Email addresses**, **Phone numbers**, **Credit card numbers**, **IBANs**, **IP addresses**) and add **Custom patterns (regex)** for things like internal order IDs. * **AI-based redaction**: an AI pass catches what patterns can't. Choose the **Categories to redact** (**Personal names**, **Physical addresses**, **ID / account numbers**, **Financial identifiers**, **Dates of birth**, **Health information**) and add **Custom instructions** for anything else, such as employee badge numbers. This pass uses your Usage Allowance. Click **Save** to apply. Everyone can see the tab; only organisation admins can change it. #### Per-group override A feedback group can carry its own redaction settings. Open the group's **Feedback group settings** menu and choose **Personal data redaction** (admin-only); the row shows whether the group is on **Organization default** or a **Custom override**. The group starts by following the organisation's settings; **Save override** freezes a separate configuration for this group only, and **Use organization default** switches it back. Later changes to the organisation default do not apply to a group with an override. *** ### Members & roles Member management is part of Organisation details, but it's worth covering on its own because it's where you control who can do what. #### The three roles BAI Analytics workspaces have three roles: | Role | What they can do | | ---------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Admin** | Everything, including inviting and removing members, changing roles, editing the organisation name, changing Analysis settings, PII redaction and Email sending, configuring integrations, and running every analytical workflow. | | **Member** | Create surveys, run analyses, configure Custom Monitoring, generate reports, and manage feedback groups they have access to. They cannot manage members or organisation-level settings. | | **Viewer** | Read-only access. They can view surveys, analyses, and reports, but cannot create or edit anything. | These roles apply to every feedback group in the workspace; there is no separate per-group sharing setting. See [Feedback Groups](/boundaryai-docs/feedback-groups/feedback-groups.md#who-can-see-and-edit-a-group) for what each role can do inside a group. #### Inviting someone From Organisation details, open the members tab: 1. Click **Invite member**. 2. Enter one or more email addresses. 3. Choose the role they should have. 4. Send the invitation. Each invitee receives an email with a sign-up link. Until they accept, they appear in the *Pending* list. You can resend or revoke a pending invitation at any time. When they accept, they land directly in your organisation. #### Changing a role Admins can change anyone's role from the Members list. Demoting yourself from Admin requires another admin to be in place. There's always at least one. #### Removing someone Removing a member revokes their access immediately. Anything they created (sources, analyses, reports, feedback groups) stays in place. Ownership defaults to the organisation so the work doesn't get orphaned. #### Single sign-on and automatic provisioning Organisations that sign in through their own identity provider can also let it manage their BAI Analytics users. BAI Analytics supports **SCIM 2.0 user provisioning**: your identity provider (Okta, Microsoft Entra ID, or any SCIM 2.0 compatible directory) creates users when they are assigned to the application, keeps their names and emails in sync, and deactivates them the moment they are deprovisioned. Deactivated users can no longer sign in and their sessions are revoked. Setting this up needs an enterprise single sign-on connection between your identity provider and BAI Analytics, which the BAI Analytics team configures with you. Contact your BAI Analytics representative to get started. *** ### Email sending Email sending is configured on the organisation profile: open **Organization details** and switch to the **Email sending** tab (admin-only). It controls how BAI Analytics sends survey invites on your organisation's behalf (see [Sending invites](/boundaryai-docs/bringing-in-your-feedback/surveys/managing-surveys.md#sending-invites)). * **Shared sending** is the default: invites go out from BAI Analytics' own address, shown as "your organisation via BAI Analytics," with a small disclaimer footer noting BAI Analytics delivered the message. * **Your own domain**: enter your sending domain and from-address, add the CNAME records BAI Analytics gives you to your DNS, then click **Verify domain**. Verified sends are fully branded and carry no disclaimer. * **Your own AWS account** (for very large senders): connect your own Amazon SES through a guided flow. Download the CloudFormation template, deploy it in your AWS account (it creates a send-only role; no credentials are ever shared with BAI Analytics), paste the role ARN back, and test the connection. Sending volume then runs through, and bills to, your own AWS account, with no platform allowance involved. Sending through BAI Analytics (shared address or your verified domain) includes a monthly volume of sends (10,000 by default); the tab shows how many you have used this month. Going over doesn't block a campaign mid-send: the Share & Send flow warns you, and overage is tracked and invoiced separately. *** ### Integrations The Integrations hub is a separate page: open it from the main navigation, or from the **Discover BAI Integrations** prompt elsewhere in the app. It has three sections: | Section | What it's for | | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Connections** | Bring customer feedback into BAI Analytics: connect support, CX, data-warehouse and file-delivery platforms so their feedback flows into your feedback groups automatically. You can connect several accounts of the same platform. See [Connecting your tools](/boundaryai-docs/bringing-in-your-feedback/connect-to-your-existing-systems.md). | | **AI assistants** | Explore your insights from the AI assistant you already use (Claude, ChatGPT, and others). An admin enables assistant access for the organisation; each member connects their own assistant and approves its read-only access. See [Connect AI assistants (MCP)](/boundaryai-docs/api-and-webhooks/mcp.md). | | **Developer tools** | **API**: generate keys for programmatic access to the [BAI Analytics API](/boundaryai-docs/api-and-webhooks/getting-started.md). Each key has a label, a [permission scope](/boundaryai-docs/api-and-webhooks/authentication.md), and per-key usage statistics; admins can rotate or revoke keys at any time. **Webhooks**: outbound event listeners that notify your stack in real time. You set a target URL, pick the events you care about, get a signing secret, and can fire a test event. See [Webhooks](/boundaryai-docs/api-and-webhooks/webhooks.md). | Connections, API keys and webhooks need the **Connected platforms & API** add-on. *** ### What's admin-only Some actions are reserved for admins: * Inviting, removing, or re-roling members. * Editing the organisation name. * Changing Analysis settings, PII redaction (organisation and per-group), and Email sending. * Creating, rotating, or deleting API keys and webhooks. * Connecting and disconnecting platforms, and enabling or turning off AI assistant access. Members and viewers see those settings either hidden or read-only. *** ### Best practices * **Keep your timezone accurate.** It affects when scheduled reports arrive in your inbox and how *next auto-import* and *digest* timestamps look on shared dashboards. * **Use roles to scope access, not invitations.** Inviting someone as a Viewer is faster than inviting them as a Member and then revoking access from every feedback group. * **Decide on PII redaction before you connect a source.** Redaction only applies to feedback that arrives after it is switched on, so enable it first if your programme handles personal data. * **Top up Web & Social Media Credits before launching a high-intensity agent.** An *Extra high*-tier run is more expensive than a *Standard* one; if your balance is thin, the run won't start. * **Rotate API keys on a schedule.** Treat them like passwords: rotate quarterly, or whenever a teammate with key access leaves the organisation. * **Test webhooks with the *****Send test event***** button.** Most webhook problems are configuration mistakes on the receiving side; testing surfaces them immediately. * **Don't share an organisation between unrelated brands or business units.** Create separate organisations and use the switcher: add-ons, branding, and members stay properly isolated.