---
title: "Workspace AI context & branding | Floral"
description: "Tune AI summaries and briefings to your industry, vocabulary, and qualifying questions. Workspace-level and personal context. Org-level logo and brand colours for customer-facing surfaces."
canonical: https://floral.so/features/workspace-ai-context
---

# Workspace AI context & branding | Floral

> Tune AI summaries and briefings to your industry, vocabulary, and qualifying questions. Workspace-level and personal context. Org-level logo and brand colours for customer-facing surfaces.

Source: https://floral.so/features/workspace-ai-context

Core feature · Never locked to one model

# Teach Floral how your team sells

Your knowledge, your voice: Floral writes the way your company talks, whichever AI model is underneath.

Workspace AI context is a short instruction block that shapes every briefing and summary Floral writes for your team. Tell it your vocabulary, your qualifying questions, your no-go signals - and watch every AI output get sharper.

[Sign up](https://floral.so/signup)[Let's meet](https://floral.so/book-a-demo)

Two layers

## Workspace context + personal context

### Workspace context for the team

One block applies to every teammate. Use it for things every rep should treat the same way - your ICP, your qualifying questions, the language you use for your product, the competitors to call out by name.

![Floral workspace AI context settings](https://floral.so/img/features/workspace-ai-context/ai-context.png)

### Personal context for individuals

Each teammate can layer their own context - "I’m the SDR doing first calls, focus on disqualifiers" or "I run executive briefings, keep it boardroom-formal". The personal layer wraps around the workspace layer.

![Floral org branding settings](https://floral.so/img/features/workspace-ai-context/branding.png)

What you can tune

## The output, end to end

### Vocabulary

Use your product name correctly. Translate generic AI phrasing into your industry’s terminology.

### Tone

Formal vs casual. Short vs detailed. Workshop-style notes vs executive briefings.

### Qualifying questions

Tell Floral what BANT-style data to surface in briefings and watch for in summaries.

### Personal context

Per-user instructions layered on top. New hires get explainers; veterans get short, dense notes.

### Org branding

Logo, primary colour, contact info - applied to PDF exports and customer-facing lead forms.

### No prompt-engineering required

Write in plain Danish or English. Floral handles the wrapping, weighting, and token budgeting under the hood.

Related features

## Pairs well with

[AI meeting briefingsBriefings inherit the workspace + personal context layers.Learn more ](https://floral.so/features/ai-meeting-briefings)[AI meeting summariesSummaries follow the same tone and vocabulary every time.Learn more ](https://floral.so/features/ai-meeting-summaries)[Per-user feature accessSet context centrally, hide settings UI from teammates who do not need it.Learn more ](https://floral.so/features/per-user-feature-access)

[All core features](https://floral.so/features)[All CRM add-on features](https://floral.so/features/crm)

## Frequently asked

What is workspace AI context?

A short text block that gets prepended to every AI prompt - briefings, summaries, you name it. Use it to teach Floral your company’s vocabulary, target industries, qualifying questions, and what to ignore.

How is this different from personal AI context?

Workspace context applies to everyone in the workspace; personal context applies only to your own briefings and summaries. Use personal for things like "I am a junior rep, explain industry jargon" - workspace for "we sell to mid-market manufacturing".

Does AI context apply retroactively?

No - it applies to new generations. If you change the context and want a briefing or summary to reflect it, hit "Regenerate" on the document.

What about branding?

Org-level branding lets you set a logo, primary colour, and contact information. Logo and colour appear on PDF exports and customer-facing surfaces (lead forms with the CRM add-on).

Is there a length limit on AI context?

Yes - soft limit of \~2,000 characters per scope. The goal is a focused instruction, not a wiki. If you have a wiki worth of context, the workspace AI context should be the index, not the document.

Insights

## Read more

[Insights →](https://floral.so/insights)

- April 2, 2026 · 10 min read  
### [Sales knowledge base best practices: the four components of one your team will actually use](https://floral.so/insights/sales-knowledge-base-best-practices)  
Most sales knowledge bases die within a year. Here are the four components that make a sales knowledge base self-sustaining, and the honest criteria for evaluating tools.

## Make Floral sound like your team

Sign up, write your workspace context in five minutes, see every briefing get sharper.

[Sign up](https://floral.so/signup)[Let's meet](https://floral.so/book-a-demo)
