General Settings (IA)

Under Usage Settings, configure behavior related to user onboarding. The following can be configured:

Under Teams, create and manage teams to organize users.

Teams allow you to better track how specific groups within your organization are using Biggy. Team usage information is available in the Team Analytics page.

You can create one team at a time or multiple teams at once.

To create multiple teams:

To create a single team:

After a team is created, users can select their team as part of the Guided Onboarding process. Or, users can be manually assigned to a team on the Users page.

To edit a team, click the Pencil icon.

To permanently delete a team, click the Trash can icon.

Under Team Groupings, create and manage team groups to organize your teams into groups.

For example, if your NOC, SRE, and Support teams are all part of the Customer division at your organization, you can create a team grouping to organize those teams together for analytics purposes.

To create a team grouping:

To edit a team grouping, click the Pencil icon.

To permanently delete a team grouping, click the Trash can icon.

On the Configuration > General Settings page under Incident Priority Values, define the incident priority ordering used for mapping incident notifications from BigPanda Event Management and for Biggy Managed Incident Channels. Managed Incident Channel

Import your priorities from BigPanda Event Management by selecting Sync from BigPanda EM. To use the Biggy default priorities, select Use Default Priorities. 

Priorities should be arranged in the list with the highest at the top and the lowest at the bottom. To add a new priority to the list, select + Add Priority and populate the Display Value, Emoji color, and the BigPanda EM Value (Optional).

Use the Home page settings to control what the Happening now section of the Biggy Home page shows for everyone in your organization.

The Happening now section's content pulls from eight categories. When the Home page loads, the section opens on the first source in the list that has activity.

Manage the sources directly in the source list:

Viewer permissions apply to every source. If a viewer can't open a source, the source shows as locked for them: counts still appear, but links don't. If a viewer isn't entitled to a module, its source is skipped for them even when the source is switched on.

Under Slack Channel Auto-Archive, automatically archive Slack channels that Biggy created for major incidents once the incident is closed and the channel has gone quiet. Static war rooms, shared (Slack Connect) channels, and channels Biggy did not create are never archived. Current installations need no new Slack permissions. Older installations may need to reauthorize the Slack app if Slack reports a missing scope.

When Auto-archive Slack channels is enabled, select the amount of time that should pass before a channel is archived in the Auto-archive channels after setting.

When someone @mentions Biggy at the top level of a Slack incident channel, Biggy answers in that message's thread. Choose whether the answer stays only in the thread or is also shown in the channel. Applies to Slack incident channels; Microsoft Teams is unaffected.

Choose one of the following options:

When responders move a bridge call to a different meeting, such as Teams to Webex, Biggy can follow it so the transcript and swarm keep hearing the incident. Choose whether Biggy ignores the new link, asks a responder to confirm, or moves the bridge on its own. Bridges fixed by their template are never moved.

Choose one of the following options:

When an automation starts failing, and again when it recovers, Biggy emails the automation's owner. Add addresses that should receive every one of those emails.

Under Additional recipients, add up to 10 email addresses. Leave this field empty to notify only the owner of the failing automation.

Under Organization Branding, define the Organization Logo, Display Name, and Accent Color used by Biggy-generated presentations.

Under Name Format, configure how Biggy interprets directory display names when greeting people and when generating summaries, decisions, owners, and action items. This setting does not modify Microsoft 365 or stored participant labels. Transcripts, attendee lists, and audit records always keep the exact provider value. Changes apply to new requests immediately.

The following name formats are available:

Under Output Time, define the timezone and format Biggy uses for timestamps in generated answers and other generated output across Slack, Teams, web chat, and the API. 

Daylight-saving changes follow the selected zone automatically, and rendered times include the zone abbreviation. This does not change each user's personal display timezone in the web app.

Under Access Requests, control who can request additional access from the My Access page.

When Limit Access Requests to Curated Roles is enabled, users with only the built-in Standard User role can no longer browse or submit access requests. 

The My Access page explains that access is managed by their administrator, and everything they can already do continues to work. Users who have been admitted to at least one curated role are unaffected.

Under Email Sharing, control whether Biggy can send generated emails, and restrict which recipient domains are allowed. Applies to all generated emails sent by Biggy.

When Allow Email Sharing is enabled, Biggy can send emails, subject to the domain restrictions configured in the Allowed Recipient Domains section.

Add your organization's name in front of Biggy AI on every email Biggy sends. The address does not change.

Under Prefix, type your organization's name (Limit 40 characters). The name always ends in Biggy AI.

Under Login Methods, select which web app login methods will appear to users in your organization.

If a method is disabled, it will not appear as an option on the web app login screen for any of your users. At least one login method must be enabled.

The following methods can be enabled or disabled:

On the Configuration > General Settings page under Linked Chat Platform Installations, view all chat platforms installed for your organization.

Primary installations determine which Slack workspace or Teams tenant is used for multi-platform-aware features such as MIM actions. The Default SSO installation determines which chat platform context is used for SSO logins.

On the Configuration > General Settings page under LLM Settings, configure settings related to your large language model provider.

Options include: