> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kurrier.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspaces & Sharing

> How workspaces, access, and sharing work in Kurrier

## Overview

Kurrier is **workspace-first**.

Everything you do in Kurrier — providers, identities, mailboxes, API keys — lives inside a **workspace**.
This makes it easy to collaborate with teammates while keeping ownership, security, and billing clear.

If you understand workspaces, the rest of Kurrier will feel intuitive.

***

## What is a Workspace?

A workspace is a **shared environment** for a team or project.

A workspace owns:

* Email providers (SES, SendGrid, SMTP, etc.)
* Identities (domains and email addresses)
* Mailboxes and received messages
* API keys
* Billing and usage

Most users only need **one workspace**, but you can create multiple if needed (for example: prod vs staging).

***

## Users vs Workspaces

Kurrier separates **users** from **resources**.

* A **user** is an individual account (you)
* A **workspace** is where shared resources live

You can belong to multiple workspaces, and each workspace can have multiple users.

***

## Ownership vs Sharing

Every resource in Kurrier has an **owner**, but some resources can be **shared** with the workspace.

This distinction is important.

### Ownership

* The owner created the resource
* The owner can edit or delete it
* Ownership never changes automatically

### Sharing

* A shared resource can be used by other workspace members
* Sharing does **not** transfer ownership
* The owner can revoke sharing at any time

### Example

Alice adds a domain identity `example.com`.
She owns the identity, but shares it with the workspace.

Bob can now send emails from `example.com` using the API —
but Alice still controls verification and deletion.

***

## Roles and Access

Workspaces support basic roles:

* **Owner** — Full control, including billing and access
* **Admin** — Manage providers, identities, and configuration
* **Member** — Use shared resources (send email, access APIs)

Fine‑grained permissions and custom roles will be added later.

***

## Why This Model Exists

This design allows Kurrier to provide:

* Safe multi-domain and multi-provider setups
* Clear audit trails for sending and receiving email
* No sharing of raw provider credentials
* One API key that works across shared identities
* Clean separation between people and infrastructure

***

## Summary

* Everything lives inside a **workspace**
* Workspaces own providers, identities, and API keys
* Resources have **owners**, but can be **shared**
* Sharing enables collaboration without losing control

Once you understand workspaces, you’re ready to set up providers and identities.