Skip to main content

​
Workspaces

A workspace is the top-level unit of isolation in LLMTune. Everything—datasets, training runs, models, endpoints, usage, billing—belongs to a workspace.

​
Key Properties

  • Isolation – Users only access assets in their workspace unless invited elsewhere
  • Unified resources – All products (FineTune Studio, Models, API, Deploy, Evaluate, Dataset Hub) share the same workspace
  • Single authentication – One account, one workspace (by default)
  • Unified API keys – Same keys work across all products
  • Billing – Usage (tokens, requests, training spend) is recorded per workspace and visible under Usage

​
Workspace Creation

When you first sign up for LLMTune:
  1. A default workspace is automatically created for you
  2. You can create additional workspaces later from the dashboard
  3. Only verified accounts can create new workspaces

​
Managing Workspaces

​
Creating Workspaces

  1. Navigate to workspace settings in the dashboard
  2. Click Create Workspace
  3. Provide a name and optional description
  4. The new workspace is ready to use immediately

​
Inviting Users

Workspace admins can invite users:
  1. Go to workspace settings
  2. Click Invite Users
  3. Enter email addresses
  4. Assign roles:
    • Admin – Full access to all features
    • Editor – Can create and modify resources
    • Viewer – Read-only access

​
Workspace Settings

Configure workspace-level settings:
  • Name and description – Identify the workspace
  • Billing – Configure payment methods and usage limits
  • API keys – Manage workspace-scoped API keys
  • Webhooks – Configure workspace-level webhooks
  • Audit logs – View activity history

​
Switching Workspaces

Use the workspace switcher in the sidebar or dashboard to toggle between environments. The interface shows:
  • Current workspace name
  • Recent activity for quick context
  • Quick access to switch workspaces

​
Audit Trails

Each workspace keeps comprehensive logs:
  • Training runs – All fine-tuning jobs and their status
  • Deployments – All deployment events and version changes
  • API usage – Request logs and usage patterns
  • Key management – API key creation, rotation, and revocation
  • User activity – Who did what and when
Audit logs are available in the workspace settings for compliance and debugging.

​
Workspace Resources

All resources are scoped to a workspace:
  • Datasets – Uploaded or connected datasets
  • Training jobs – Fine-tuning runs and their results
  • Models – Deployed models and their versions
  • API keys – Workspace-scoped authentication keys
  • Webhooks – Event subscriptions
  • Usage data – Metrics and billing information

​
Best Practices

  1. Use separate workspaces for different projects or environments
  2. Invite team members with appropriate roles
  3. Monitor usage regularly to stay within budget
  4. Review audit logs for security and compliance
  5. Rotate API keys periodically for security

​
Next Steps