# Team AI workspaces with shared controls

Source: https://cicora.ai/en/products/teams

Create a shared workspace with roles, invitations, organization balance, API keys, and scoped usage.

Give colleagues access through a workspace instead of a shared login, with roles and organization-scoped resources.

## Share work without sharing a password

- Invite people and assign workspace roles.

- Use an organization balance for the active workspace.

- Manage organization-scoped API keys and usage.

## Set up a workspace around the work

Create a workspace, invite colleagues with an appropriate role, then use its shared balance and organization-scoped controls.

## For teams that need visible access boundaries

Use Teams when several people need the same workspace resources while their permissions and membership remain explicit.

## Roles control access, not outcomes

Workspace permissions govern available actions. Billing, model availability, and usage remain subject to the active organization and current product settings.

## Continue with the connected products

## Related pages

- [/en/pricing](/en/pricing.md)
- [/en/models](/en/models.md)

## FAQ

### What is cicora.ai?

cicora.ai is a multi-model AI workspace and compatible API for chat, text, images, video, coding tools, and teams. Start with the [overview](/en.md), [documentation](/en/docs.md), or [model catalog](/en/models.md).

### How is usage billed?

Confirmed usage is charged in USD from the active workspace's prepaid balance. Use the live catalog for current model prices and the [usage guide](/en/docs/usage-costs.md) for settlement details.

### Which protocols and integrations are available?

Documentation covers OpenAI-compatible Chat Completions and Responses, Anthropic Messages, image interfaces, Claude Code, OpenCode, and Codex CLI. Compatibility does not imply support for every upstream parameter.

### Which sources are authoritative and current?

For model IDs, availability, capabilities, limits, and prices, use the [live catalog](/en/models.md). For API behavior, use the matching [documentation page](/en/docs.md). Never include API keys, private workspace data, or preview URLs in public documents.