teams

Create a team workspace

Create a team workspace, set it up correctly, and avoid the configuration mistakes that cause confusing permission and data problems later.

Last verified 13 October 2026 · OpenbirdAI documentation

A team workspace is the shared context for a group of people working on the same business. Creating one is quick; the decisions you make at creation time — name, purpose and initial members — determine how clean it stays.

This guide describes a capability that depends on the connected provider, the permissions granted to it, and your current plan. If the provider cannot supply the required data, OpenbirdAI reports it as unavailable rather than estimating.

Creating the workspace

Open the workspace area and choose to create a team workspace.
Give it a specific, recognisable name — usually the business or client name.
Confirm the plan and workspace limits for your account.
Set the workspace context you want new members to assume: what this workspace is for and what it must never be used for.

Naming and scoping

A workspace name is how people avoid mistakes. Use names that a new member would immediately understand, and record the workspace's purpose in its memory so OpenFeather answers in the right context.

Create a separate workspace per client. One workspace holding several clients is the most common source of accidental data exposure.

What to configure first

Connections — connect only the accounts this workspace legitimately needs.
Workspace memory — write the stable business context once.
Roles — decide what an ordinary member may do before inviting anyone.
Usage — confirm the plan limits for this workspace.

Inviting people safely

Invite only the people who genuinely need this workspace. Every member can read the workspace's connected data and memory, which is a broader grant than it looks.

Team features depend on plan and configuration availability. If an option is not shown in your account, it is not currently available to you.

A sensible first week

Create the workspace with a name that states whose data it holds.
Write two or three sentences of workspace memory about what the business does.
Connect exactly one provider and verify it with a narrow question.
Invite one colleague with the lowest role that lets them work.
Only expand connections and membership once the first week is quiet.

Starting narrow keeps the debugging surface small. Each extra connection is another variable when an answer comes back wrong.

Common questions

How many workspaces can I have?

That depends on your plan. The plan and usage area shows the limit for your account.

Should every teammate get their own connection?

Usually not. A shared connection inside the workspace is often sufficient and avoids inconsistent data.