> ## Documentation Index > Fetch the complete documentation index at: https://learn.kubit.ai/llms.txt > Use this file to discover all available pages before exploring further. # Set up your organization > Sign up for Kubit, name your organization, create a workspace, add your traces or events and invite your team. This guide is for the first person at your company to use Kubit. You'll sign up, name your organization, create a workspace, add your data and invite your team. The steps are the same for Agent Observability and Product Analytics. Only the step that adds your data differs, and each way of adding data has its own page. The account steps take about 10 minutes. Kubit creates your organization when you first sign in, and you become its **Owner**. Everyone you invite joins that organization. ## Before you start * [ ] An early-access link from Kubit, or an invite from someone already in your organization * [ ] A work email address. Kubit refuses personal and free email domains. ## Steps ### 1. Sign up Open the early-access link. It takes you to the **Sign Up** screen. Enter your **Work Email** and click **Continue**. To use your Google account instead, click **Continue with Google**. Without an early-access code or invite in the link, Kubit shows an **Invite only** card instead of the form. ### 2. Verify your email Kubit sends a code in an email with the subject `Verify your Kubit account`. On the **Check Your Inbox** screen, type it into **Verification Code**. Click **Continue**. No email? After 30 seconds, a **Resend** link appears under `Don't see it?`. ### 3. Choose how you sign in On **Secure Your Account**, pick **Create Passkey** or **Create Password**. A password needs at least 8 characters, upper and lowercase letters, a number and a special character. A passkey signs you in with your fingerprint, face or a security key. [Join your team on Kubit](https://learn.kubit.ai/start-here/user.md#create-a-passkey) covers passkeys in detail. ### 4. Name your organization Your new organization is called `My Org` until you rename it. Go to **Settings** > **Organization** > **General**, change **Organization Name** and click **Save**. | Field | Rule | | - | - | | **Organization Name** | **50 characters** at most | | URL prefix | Kubit picks a random 10-character prefix for your organization's URLs. It **can't be changed**. | | Logo | PNG, JPEG or SVG, under **1 MB** | ![Settings, Organization, General page with the Organization Logo upload and the Organization Name field set to My Org, with Save and Cancel buttons.](https://mintcdn.com/kubit/9i8QHxqek50tMBGy/images/admin/organization-general.png?fit=max\&auto=format\&n=9i8QHxqek50tMBGy\&q=85\&s=c3828f37b2269f4eee630cc99cff8c3b) ### 5. Create a workspace A workspace holds one set of data (agent traces, clickstream events or both) and the reports built on them. Open the workspace switcher at the top of the left nav and click **New workspace**. The first time you sign in, onboarding shows **Create Demo Workspace**. Click **Set up my own workspace** there instead. On **Create Workspace**, fill in: | Field | What to enter | | - | - | | **Workspace Name** | 2 to 50 characters, unique in your organization | | **Workspace Timezone** | Defaults to your browser's timezone | | **Origin** | Where your data comes from. See the table below. The dropdown defaults to **Sandbox**. | ![Create Workspace dialog with Workspace Name set to Support agent traces, a Workspace Timezone dropdown and Origin set to Warehouse, described as OTel traces in Databricks, Snowflake, BigQuery or ClickHouse.](https://mintcdn.com/kubit/9i8QHxqek50tMBGy/images/admin/create-workspace.png?fit=max\&auto=format\&n=9i8QHxqek50tMBGy\&q=85\&s=2d5b89283401948a9522113c9029af88) Click **Continue**. Kubit opens the **Modeler** on the **Warehouse Connection** tab. Each **Origin** tells Kubit where the workspace's data comes from. | Origin | Description in the app | Type | | - | - | - | | **Agent** | LLM traces via OTel | Agent Observability | | **User** | Clickstream events via OTel | Product Analytics | | **Warehouse** | OTel traces in Databricks, Snowflake, BigQuery or ClickHouse | Either or Both | | **Langfuse** | Langfuse traces in ClickHouse | Agent Observability | | **MLflow Tracing** | MLflow traces in Databricks | Agent Observability | | **Cortex Agents** | Cortex Agent traces in Snowflake | Agent Observability | | **Google ADK** | ADK agent events in BigQuery | Agent Observability | | **Sandbox** | `Upload OTel trace files for quick testing — no pipeline` | Agent Observability | ### 6. Add your data How you add data depends on where it is. Pick the row that matches your data and follow its page. | Your data | Origin | In the Modeler | Page | | - | - | - | - | | Traces or events in Snowflake, BigQuery, Databricks or ClickHouse | **Warehouse** | **Warehouse Connection** > **New connection**, then set **Warehouse type** | [Bring your own warehouse](https://learn.kubit.ai/warehouses/overview.md) | | An agent you instrument with `kubit-otel` or `@kubit-ai/otel` | **Agent** | **TBD** | [Quickstart](https://learn.kubit.ai/agent-observability/get-started/quickstart.md) | | Self-hosted Langfuse traces in your ClickHouse | **Langfuse** | **TBD** | [Connect ClickHouse](https://learn.kubit.ai/warehouses/clickhouse.md) | | Traces sent to Langfuse Cloud or Braintrust | **TBD** | **TBD** | [Set up with your coding agent](https://learn.kubit.ai/agent-observability/get-started/coding-agent.md) | | Clickstream events from RudderStack, Segment, Snowplow or mParticle | **TBD** | **Customer Data Platform** | [Data sources](https://learn.kubit.ai/product-analytics/data-sources/overview.md) | | OpenTelemetry trace files, for a quick test | **Sandbox** | **Warehouse Connection** > **From upload** | | To reuse a warehouse connection your organization already added, click **Use existing** in the Modeler. ### 7. Invite your team Go to **Settings** > **Organization** > **Team** and click **Invite Member**. | Field | What to enter | | - | - | | **Organization Role** | **Owner**, **Admin**, **Member**, **Viewer** or **None**. The default is **Member**. Pick **None** to give access to only some workspaces (see [Limit someone to some workspaces](#limit-someone-to-some-workspaces)). | | **Email Addresses** | One or more work emails separated by commas, up to **999** per invite | ![Invite Member dialog with Organization Role set to Member above an empty Email Addresses box, and Cancel and Invite buttons.](https://mintcdn.com/kubit/9i8QHxqek50tMBGy/images/admin/invite-member.png?fit=max\&auto=format\&n=9i8QHxqek50tMBGy\&q=85\&s=8395249864347cdca563eb89c6ad8637) Click **Invite**. A toast reads `Invitation sent`. Each person gets an email with the subject `Welcome to Kubit` and a link to join. Invites don't expire. You give each person one role for the whole organization. To change someone's role in one workspace, use that workspace's column in the **Team** table after they're added. ## Roles A role decides what someone can change in the organization and its workspaces. Roles rank Owner, then Admin, Member, Viewer and None. | Action | Owner | Admin | Member | Viewer | None | | - | - | - | - | - | - | | See organization settings and the Team page | Yes | Yes | Yes | Yes | No | | Rename the organization, change the logo | Yes | Yes | No | No | No | | Invite, deactivate and change roles of members | Yes | Yes | No | No | No | | Create, archive and restore workspaces | Yes | Yes | No | No | No | | Delete a workspace | Yes | No | No | No | No | | Grant the Owner role | Yes | No | No | No | No | Admins can't change an Owner's role, and Owners can't change their own role. The person who created the organization is an Owner like any other. ## Limit someone to some workspaces The **None** organization role gives someone access only to the workspaces you pick. A person with **None** is an active member of the organization but has no permissions and sees no workspaces until you give them a role in one. | Organization role | Which workspaces the person sees | | - | - | | **Member** or **Viewer** | Every workspace, except ones where their workspace role is set to **None** | | **None** | Only workspaces where their workspace role is higher than **None** | An invite sets only the organization role. Giving someone access to some workspaces takes two steps: 1. Invite them with **Organization Role** set to **None**. 2. In the **Team** table, set their role in the column of each workspace they need. Until you do step 2, they can sign in and join but can't open any dashboard or report. **None** doesn't suspend anyone. To remove someone's access completely, use **Deactivate Member** (see [Manage invites and members](#manage-invites-and-members)). ## Manage invites and members The **Team** page has three tabs: **Active**, **Pending** and **Deactivated**. | Tab | How | What it does | | - | - | - | | **Pending** | Row menu > **Resend Invitation** | Sends the invite email again | | **Pending** | Row menu > **Cancel Invitation** | Withdraws the invite | | **Active** | Deactivate icon on the row, then **Deactivate** | Removes the person's access to the organization | | **Deactivated** | Reactivate icon on the row, then **Reactivate** | Restores the person's access | ## Verify Open **Settings** > **Organization** > **Team** and click **Pending**. Each person you invited is listed by email. When they accept, they move to the **Active** tab. ## If it fails | Symptom | Cause | Fix | | - | - | - | | `Sorry, registration is by invite only for now. Please contact support@kubit.co` | The sign-up link has no early-access code or invite | Use the exact link from your early-access email | | `Please use your work email address` | The email is on a personal or free domain | Sign up with your company email | | `Account already registered, please sign in` | The email already has a Kubit account | Sign in instead of signing up | | `Organization name must be 50 characters or fewer` | The name is too long | Shorten it to 50 characters | | `A workspace with this name already exists — choose another name.` | Another workspace in the organization has that name. Case doesn't matter. | Pick a different **Workspace Name** | | **New workspace** is grayed out, with the tooltip `You don't have permission to create workspaces.` | Your role is Member, Viewer or None | Ask an Owner or Admin to create it, or to raise your role | | `{email} is already a member.` | The person is already in the organization | Nothing to do. Change their role in the **Team** table if needed. | | `{email} is deactivated — reactivate them instead.` | The person was deactivated | On **Deactivated**, choose **Reactivate Member** | | `{email} is a personal email address — members need a work email.` | New members need a work email. People who already have a Kubit account on a personal address can still be invited. | Invite their company email | | **Seat cap reached.** banner in **Invite Member** | Your plan has no free seats | Deactivate someone, or upgrade your plan (an **Upgrade plan** link shows when billing is on) | | `You've reached your plan's seat limit.` on resend or reactivate | Your plan has no free seats | Same as above | ## Next steps * [Join your team on Kubit](https://learn.kubit.ai/start-here/user.md): what the people you invite see, from the email to their first report. * [Bring your own warehouse](https://learn.kubit.ai/warehouses/overview.md): connect Snowflake, BigQuery, Databricks, ClickHouse or Redshift. * [Quickstart](https://learn.kubit.ai/agent-observability/get-started/quickstart.md): send spans with `kubit-otel` into an **Agent** workspace. * [Data sources](https://learn.kubit.ai/product-analytics/data-sources/overview.md): send clickstream events from a customer data platform. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.