> 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, what plan you're on, 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: * **Usage**: your current capacity (how much you've used, how much is left). * **Account**: your personal profile, your organisation's details, and the in-app walkthrough. * **Billing & Plans**: your current plan and a shortcut to the billing portal. A few related surfaces live next door: your **Profile** at the top of the page, **Organisation details** for the workspace, and the **Integrations** hub for connectors, API keys, and webhooks. Settings is the central jumping-off point for all of them. *** ### 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. 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 progress bar** that fills with usage and changes colour as you approach the limit (green, then yellow, then red). * **A reset date**: when the next monthly allowance lands. The card has a **View usage** link that opens a more detailed page with a date-range picker and a per-feature breakdown, so you can see which workflows (theme detection, summaries, monitor scanning, and so on) drive most of your consumption over time. {% hint style="info" %} **What's a credit?** One credit covers a small amount of AI work. Short responses use a fraction of a credit; longer or more complex ones use more. If you're getting close to your limit, contact us, we're happy to adjust the plan to fit your actual workload. {% endhint %} #### Web & Social Media Credits This 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**. * Open the **history** to inspect every top-up, every agent run, and every refund (failed runs refund credits automatically). * **Add credits** in fixed packages (25 / 50 / 100 / 250 / 500 / 1,000 credits, where 1 credit = $1 USD) via Stripe checkout. #### Auto top-up Auto top-up lets you keep scraping agents running without manually buying credits every time the balance gets low. 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. Auto top-up is also plan-gated. On unsupported plans, the panel shows: > Auto top-up is available on paid plans only. See [Social Listening](/boundaryai-docs/bringing-in-your-feedback/social-listening.md) for what credits cost per run. *** ### Account The Account section has three quick links. #### Profile Click **Profile** 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 (using an authenticator app, SMS, or backup codes). * View and revoke active sessions on devices you no longer use. * Connect or disconnect single-sign-on 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. 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 **Organisation details** to manage your 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 organisation switcher lets you flip between them; the workspace context (surveys, feedback groups, plan, members, credits) reloads to match the active organisation. * **Billing**: admins also see a Billing tab here that mirrors what's available from the main Settings page (see Billing & Plans below). 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. #### Replay walkthrough Click **Walkthrough** 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. *** ### 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, managing billing, 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, billing, or organisation-level settings. | | | **Viewer** | Read-only access. They can view surveys, analyses, and reports, but cannot create or edit anything. | These workspace-level roles set the **floor** for what a person can do. On top of them, individual feedback groups can be shared with finer-grained access (*Read-only* or *Read-write*) to scope a person's reach inside a specific project. Feedback-group access takes precedence over the workspace role within its own scope. See [Feedback Groups](/boundaryai-docs/feedback-groups/feedback-groups.md) for the project-level permission model. #### Inviting someone From Organisation details → Members: 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. #### 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. *** ### Billing & Plans The Billing & Plans section shows your **current plan** with a coloured badge. #### The plan tiers | Plan | What's included | | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Starter** | Suitable for small teams running surveys and uploads, without integrations or scraping. | | **Standard** | Adds connectors (Zendesk, Freshdesk, Jira, etc.), web & social scraping agents, Custom Monitoring, API keys, and webhooks. The most common plan for teams running cross-channel feedback programmes. | | **Enterprise** | Custom plan for large organisations: billing, support, and feature configuration are handled directly with the BAI Analytics team. | #### Manage Billing If you're an admin on a self-serve plan (Starter or Standard), the **Manage Billing** button opens the Stripe customer portal in a new tab. From there you can: * **Update payment methods**: add a new card, change the default, remove an old one. * **Change billing email**: where invoices are sent. * **Download invoices and receipts** for past charges. * **Upgrade or downgrade your plan**: pricing comparisons are shown at the upgrade step. * **Cancel your subscription**: your workspace continues to work until the end of the current billing period. When you finish in the portal and return to the BAI Analytics tab, your plan and limits are refreshed automatically. The Manage Billing button is **admin-only** and is hidden for Enterprise plans, since those are managed directly with the team. *** ### Email sending Email sending is configured on the organisation profile: open **Organisation 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-share-send)). * **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 **10,000 sends per 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 four sections: | Section | What it's for | | ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Native Connectors** | Connect Zendesk, Freshdesk, Jira, Intercom, HubSpot, and 30+ other ticketing and project-management platforms so their tickets flow into your feedback groups automatically. See [Connecting your tools](/boundaryai-docs/bringing-in-your-feedback/connect-to-your-existing-systems.md). | | **API Keys** | 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. A key with the read-only `mcp_read` scope also lets [AI assistants query your feedback analytics](/boundaryai-docs/api-and-webhooks/mcp.md) directly. | | **Webhooks** | Outbound event listeners that notify your stack in real time when activity happens in your workspace. You set a target URL, pick the events you care about, and get a signing secret. A *Send test event* button lets you confirm the receiving endpoint is wired up correctly without waiting for a real event. See [Webhooks](/boundaryai-docs/api-and-webhooks/webhooks.md) for the event catalogue and signature verification. | | **Web & Social Media Credits** | Top up the credit pool that fuels scraping agents. Same balance and history described under Usage above; surfaced here too because it's part of integration management. | Most of these surfaces are gated to the **Standard plan and above**. Starter users see the catalogue and an upgrade prompt instead of a *Connect* or *Create* action. *** ### What's gated by plan | Capability | Starter | Standard | Enterprise | | -------------------------------------------- | ------- | -------- | ------------------------------------- | | Profile, language, timezone, password / 2FA | ✓ | ✓ | ✓ | | Manage members and roles *(admin only)* | ✓ | ✓ | ✓ | | Stripe billing portal *(admin only)* | ✓ | ✓ | : *(handled by your account manager)* | | Detailed Usage breakdown | ✓ | ✓ | ✓ | | Web & Social Media Credits + scraping agents | : | ✓ | ✓ | | Native connectors | : | ✓ | ✓ | | API keys & webhooks | : | ✓ | ✓ | | Custom Monitoring | : | ✓ | ✓ | Sections you don't have access to are visible but show an upgrade prompt instead of a working action, so you can see what's available without needing a sales call. *** ### What's admin-only Some actions are reserved for admins regardless of plan: * Inviting, removing, or re-roling members. * Editing the organisation name. * Opening the billing portal and changing the plan. * Creating, rotating, or deleting API keys and webhooks. * Connecting and disconnecting native connectors. 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. * **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: billing, branding, and members stay properly isolated.