Workspace settings

A workspace is a tenant: its own members, chats, groups, agents, Brains, and settings. As a workspace admin you manage it from the Admin console.

The workspace

• Create and edit workspaces — name and basic properties. New users are guided to create or join one during onboarding.
• Members — see who's in the workspace and their access. See Invites & members and Groups & roles.
• Domain licences — a workspace can be associated with an email domain so that people from that domain can be onboarded in a controlled way.

Workspace agents

Agents are configured per workspace. From the console you can add and manage the agents available in the workspace — their identity and the roster that participates in chats and deliberation.

• Agents appear to users via @mention.
• The roster is what a /council or /boarddeliberation fans out to.

Settings scopes

LEMA Chat's settings apply at three scopes: user, workspace, and global (platform-wide). As a workspace admin you manage workspace-scoped settings; global and identity/security-sensitive keys are reserved for SuperAdmin (see the SuperAdmin appendix).

Workspace-relevant settings include the deliberation round caps (council_max_rounds, board_max_rounds) and the presence/turn-taking dispatch tuning that governs when agents speak.

Config lives in settings, not env vars

Operational configuration is stored in AdminSettings, read live — not baked into environment variables. That means an admin changes behaviour in the console, and it takes effect without a redeploy.