Docs home

Concepts

Workspace, organization, and plans

How FlexyAgents scopes users, agents, and limits to your organization—and how that maps to billing, environments, and day-to-day operations.

organizationworkspaceplansflexyagents

Everything you configure in FlexyAgents hangs off an organization: the unit of subscription, usage limits, and member access. Understanding that boundary prevents accidental mixing of customer-facing and internal agents, and clarifies why some connectors or channels require upgrades.

This guide explains members and roles at a high level, how agents inherit org-level model keys, and where plan gates surface in the product.

The organization boundary

Each organization has its own agents, knowledge bases, API credentials, and analytics. Switching orgs in the dashboard is explicit so you never edit production agents while intending to work in a sandbox tenant.

Billing and plan features are evaluated per organization. If you need separate SLAs or data isolation for subsidiaries, separate orgs are usually clearer than one overloaded workspace.

Members and access

Invite users with roles that match least privilege: who can publish agent changes, who can view transcripts, and who can manage integrations. Sensitive transcripts may be restricted by role or plan.

Service accounts for automation should use API keys scoped to the minimum agents and endpoints required.

Plans and limits

Limits may include message volume, connector count, channel types, automations, retention, and—on hosted inference—special monthly caps for AI enrichment of knowledge such as Gemini image description on uploads vs crawls, and Gemini transcription of uploads vs crawled media.

The dashboard surfaces overages or blocks with actionable messaging rather than silent failures. Organization-level LLM keys (especially Google Gemini) can shift vision and transcription spend to your provider account and skip hosted counters for those operations.

When approaching limits, prioritize disabling non-production agents or archiving unused knowledge before customer-facing traffic is affected.

  • Admins adjust plan limits in the admin/plan tooling; operators see current usage on relevant knowledge screens.
  • BYOK plans may require your own API keys per provider before chat works at all—hosted fallback is disabled where contractually required.

Build on your stack

Ready to ship grounded assistants?

Start a trial or talk to us about rollout, governance, and enterprise requirements.