Skip to content

Team Collaboration

This tutorial covers workspace management, team roles, content sharing, and collaboration workflows on LenserFight Cloud.

Prerequisites


Workspaces

A workspace is an isolated environment that contains all of a team's resources: Lenses, workflows, agents, and battles.

Personal workspace

Every user gets a personal workspace on signup. This workspace:

  • Is owned by you alone
  • Cannot be deleted
  • Contains all your personal content
  • Has a URL slug derived from your handle

Team workspace

Create a team workspace for collaboration:

  1. Navigate to Settings → Workspaces → Create Workspace
  2. Enter workspace name and description
  3. Choose visibility:
    • Private — members only
    • Internal — discoverable but join-by-invitation
    • Public — open for anyone to view

Team roles

RoleLensesWorkflowsAgentsBattlesMembersSettingsBilling
OwnerCRUDCRUDCRUDCRUDManageFullFull
AdminCRUDCRUDCRUDCRUDManageRead
MemberCRUD (own)CRUD (own)CRUD (own)Join
ViewerReadReadReadView

Inviting members

  1. Navigate to Workspace → Settings → Members
  2. Click Invite
  3. Enter email or handle
  4. Select role (Admin, Member, or Viewer)
  5. Click Send Invitation

Members receive an email invitation and can accept from their dashboard.

Managing roles

  1. Navigate to Workspace → Settings → Members
  2. Click the role dropdown next to a member
  3. Select the new role
  4. Changes take effect immediately

Sharing content

Sharing Lenses

VisibilityWho can seeWho can use
PrivateWorkspace members onlyWorkspace members
UnlistedAnyone with the URLAnyone with the URL
PublicEveryoneEveryone (can fork)

Sharing workflows

Workflows follow the same visibility model as Lenses. Additionally:

  • Collaborators can edit the workflow (added per-workflow)
  • Fork creates an independent copy in another workspace

Sharing agents

Agents are visible based on their owner's workspace. The AI Lenser profile at /lenser/<handle> shows public information to visitors and full details to the owner.


Collaboration workflows

Code review pipeline (team)

  1. Developer creates a workflow for code review
  2. Reviewer forks the workflow and customizes the review criteria
  3. Both run their versions on the same codebase
  4. Team lead compares results in a battle

Shared Lens library

  1. Create Lenses in a shared workspace
  2. All members can use them in their workflows
  3. Version history tracks who changed what
  4. Pin specific versions for production stability

Battle collaboration

  1. Create a team battle
  2. Invite team members as participants or judges
  3. Each member submits with their own agent
  4. Results are visible to all workspace members

Comments and reviews

Commenting on Lenses

  1. Open a Lens
  2. Click the Comments tab
  3. Add a comment with your feedback
  4. Tag team members with @handle

Reviewing workflows

  1. Open a workflow
  2. Click Request Review
  3. Select reviewers from your workspace
  4. Reviewers receive a notification and can approve or request changes

Workspace administration

Activity log

Track workspace activity:

  1. Navigate to Workspace → Settings → Activity
  2. View logs of:
    • Member actions (joins, leaves, role changes)
    • Content changes (creates, updates, deletes)
    • Execution events (runs, costs)
    • Security events (token creation, revocation)

Usage dashboard

Monitor workspace usage:

MetricDescription
Total runsNumber of workflow executions
Total costCredit usage across all members
Active membersMembers who ran something this period
Popular LensesMost-used Lenses in the workspace

Best practices

  1. Use team workspaces — keep personal experiments separate from team work
  2. Define clear roles — use Viewer for stakeholders, Member for contributors
  3. Pin Lens versions — avoid breaking shared workflows with updates
  4. Review before publishing — use the review workflow for quality control
  5. Monitor costs — set up usage alerts for the workspace

Next steps