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

# Internal Users

> Invite, manage, and govern internal users, roles, budgets, and key ownership across the tenant.

## Overview

The **Internal Users** section allows tenant administrators to manage users who can access the LLMGrid console. This includes inviting users, assigning roles, managing team membership, tracking spend, and controlling virtual key ownership.

Internal users typically represent employees, operators, or administrators within your organization.

***

## Users

The **Users** tab lists all internal users associated with the selected tenant.

### Primary Actions

* **Invite User** – Invite a single user
* **Bulk Invite Users** – Invite multiple users via CSV
* **Select Users** – Enable bulk actions such as bulk edit

***

### User Table Columns

* **User ID** – Unique identifier for the user
* **Email** – User’s email address
* **User Name** – Display name
* **Global Proxy Role** – Platform-wide permission level
* **User Alias** – Optional identifier
* **Spend (USD)** – Usage attributed to the user
* **Budget (USD)** – Spending limit (if configured)
* **SSO ID** – Identifier used for SSO-based authentication
* **Virtual Keys** – Number of keys owned by the user
* **Created At / Updated At** – Lifecycle timestamps
* **Actions** – Edit, delete, or manage the user

Use **Search**, **Filters**, and **Reset Filters** to narrow results.

***

## Invite User

Select **Invite User** to create a new internal user who can be part of the same organization, team or tenant.

### Required Fields

* **User Name**\
  Full name of the user.
* **User Email**\
  Email address used for login and notifications.
* **Global Proxy Role**\
  Defines platform-wide permissions. Common roles include:
  * `Admin (All Permissions)`
  * `Internal User (Create/Delete/View)`
  * `Internal User (View Only)`

***

### Optional Fields

* **Team**\
  Assign the user to a team at creation time.\
  The user is added with a standard `user` role for that team.
* **Metadata (JSON)**\
  Structured metadata associated with the user.
  **Example**
  ```json theme={null}
  {
    "department": "engineering",
    "location": "us-east"
  }
  ``
  ```

## Invitation Link

Admin can invite other team members to the tenant, LLMGrid displays an **Invitation Link** dialog.

### Invitation Link Behavior

* The link is unique to the user and tenant
* The link can be safely copied and shared
* The link is also sent to the recipient's email.
* The link directs the user to the LLMGrid login page with an invite notice

Administrators can regenerate the link by re‑inviting the user if needed.

## Accepting an Invite

When the invited user opens the link:

* The login page displays a **“You’ve been invited”** banner
* The user signs in or creates an account
* Upon success, the user is automatically added to the tenant

If the user belongs to multiple tenants, they can switch contexts using the tenant dropdown at any time.

## Multi‑Tenant Behavior

* A single user can belong to **multiple tenants**
* Each tenant has its own roles, teams, budgets, and policies
* The **active tenant** controls what data and actions are visible
* Switching tenants does **not** require re‑authentication

## Best Practices

* Always verify the **active tenant** before sending invitations
* Add team assignments during invite to simplify on-boarding
* Use metadata for internal automation and reporting
* Periodically review user access per tenant