# Work with a team organization

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

An organization is a shared team workspace. Chats, images, videos, API keys, usage, and balance belong to the active workspace, so check its name in the cabinet before starting work.

## Create an organization

1. Open [Settings](https://app.cicora.ai/settings) and find **Organizations**.
2. Select **Create organization**, enter a recognizable name, and save.
3. Select the new organization in the workspace switcher.

Your personal workspace remains available under the same account. Use the account menu to switch between it and organizations; after a switch, the cabinet loads the selected workspace's balance, keys, usage, and history.

## Invite members

Open the intended organization's management view in [Settings](https://app.cicora.ai/settings), choose a role, and use either method:

* an email invitation for a specific person;
* a one-use link that you deliver through your own communication channel.

Each member accepts the invitation from their own account. Never share a common password or complete API key with colleagues. If a link has been used, expired, or revoked, create a replacement instead of forwarding the old one.

## Choose a role by the required action

Decide what the person needs to do before assigning a role:

| Required action                                                            | Suitable roles |
| -------------------------------------------------------------------------- | -------------- |
| Manage the organization, members, billing, keys, and workspace content     | Owner or Admin |
| Manage balance and invoices and read usage without access to chats or keys | Billing        |
| Create keys, work with API, chats, and images, and read usage              | Developer      |
| Work with chats and images without access to billing or keys               | Member         |
| Read available workspace data without making changes                       | Viewer         |

Changing billing requires billing-management capability. Owner, Admin, and Billing have it; Viewer can only read the billing data available to that role. Grant the smallest role that supports the task and review it when responsibilities change.

## Check the active workspace

The shared balance pays for chat, API, image, and video work inside the organization. API keys created while that organization is active belong to it, and [Usage](https://app.cicora.ai/usage) shows its requests and spending.

Create a separate key for each project or service and apply a [spend limit](/en/docs/spend-limits). This produces clear attribution and lets you revoke one key without stopping other projects. Do not use a personal-workspace key for a team service or move an organization key into a personal project.

## Understand chat visibility

A chat created in an organization belongs to the organization, not only to its creator. Members with chat-read access can see those conversations; the Billing role does not receive chat access.

Switch to the personal workspace or use a separate organization with the intended membership for private or isolated work. A separate API key inside the same organization separates spending but does not make that organization's chats private.

## Troubleshooting


**An invitation or invite link does not open**


Confirm that the member is signed in to their own account and is using the newest invitation. A one-use link stops working after acceptance, expiry, or revocation; an organization administrator can check its status and create a new link or email invitation.


**A member can see the organization but not the intended section**


Check the member's role in organization management and match it to the required action. Do not promote someone to Admin for one section when a smaller role supplies the needed access.


**A colleague can see another member's chat**


This is expected for organization chats when the role has chat-read access. Switch to the personal workspace or a separate organization for isolated work; creating another key in the same organization does not change chat visibility.


**The balance, keys, or usage belong to an unexpected workspace**


Check the active workspace in the account menu first. Then compare the organization name, key name, and visible masked key prefix; never send the complete key when contacting support.

## 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.