Teams & Workspaces
RenderDoc uses a two-level organizational hierarchy: Teams and Workspaces. Understanding this structure helps you organize your work effectively and collaborate with your team.
Overview
Team (Organization Level)
├── Billing & Subscription
├── Team Members & Roles
├── Team Analytics (Financial)
└── Workspaces
├── Workspace A
│ ├── Templates
│ ├── API Keys
│ ├── Document Logs
│ ├── Webhooks
│ └── Workspace Analytics (Operational)
└── Workspace B
├── Templates
├── API Keys
└── ...
Teams
A Team is your organization-level container. It represents a billing entity and controls who has access to your resources.
What Belongs to a Team
| Feature | Description |
|---|---|
| Billing & Subscription | Your plan, document credits, and invoices |
| Team Members | Users who can access team resources |
| Team Roles | Permissions for team members (Owner, Admin, Member, Viewer) |
| Team Analytics | Financial metrics like credit usage and cost attribution |
| Workspaces | Project containers within the team |
Team Roles
| Role | Capabilities |
|---|---|
| Owner | Full access, manage billing, delete team |
| Admin | Manage members, create workspaces, access team analytics |
| Member | Access assigned workspaces, create documents |
| Viewer | View-only access to assigned workspaces |
When to Use Team-Level Features
- Managing who has access to your organization
- Viewing billing and subscription information
- Understanding overall credit usage and costs
- Creating or managing workspaces
Workspaces
A Workspace is a project container within a team. Use workspaces to isolate different projects, clients, or environments.
What Belongs to a Workspace
| Feature | Description |
|---|---|
| Templates | Document templates (PDF and Excel) |
| API Keys | Authentication keys for API access |
| Document Logs | History of generated documents |
| Webhooks | Event notification subscriptions |
| Asset Gallery | Images and files used in templates |
| Workspace Analytics | Operational metrics like success rates and processing times |
| API Playground | Interactive API testing |
When to Use Workspaces
- Different Projects: Keep client A's templates separate from client B's
- Environments: Separate development, staging, and production
- Departments: Marketing templates vs. Finance templates
- Access Control: Give specific team members access to specific workspaces
Workspace Examples
Acme Corp (Team)
├── Development Workspace
│ ├── Test templates
│ ├── Dev API keys
│ └── Test webhooks
├── Production Workspace
│ ├── Production templates
│ ├── Production API keys
│ └── Production webhooks
└── Marketing Workspace
├── Campaign templates
└── Marketing API keys
Context Modes
RenderDoc operates in two context modes depending on your selection:
Team-Only Mode
When you have a team selected but no workspace:
- Available Features: Team settings, team analytics, billing, workspace management
- Hidden Features: Templates, API keys, document logs, webhooks, API playground
Use this mode when you need to:
- Manage team members
- View billing information
- Check team-level analytics (credit usage, cost attribution)
- Create or switch workspaces
Team + Workspace Mode
When you have both a team and workspace selected:
- All Features Available: Everything from team-only mode plus workspace-specific features
- Context: Operations happen within the selected workspace
Use this mode for day-to-day work:
- Creating and editing templates
- Generating documents
- Managing API keys
- Viewing document logs
- Setting up webhooks
Selecting Teams and Workspaces
Using the Header Selector
The header contains two dropdown selectors:
- Team Selector (left): Shows your current team and lets you switch
- Workspace Selector (right): Shows workspaces in the current team
┌─────────────────────────────────────────────────────────────┐
│ [Acme Corp ▼] / [Production ▼] │
│ ↑ Team ↑ Workspace │
└─────────────────────────────────────────────────────────────┘
Switching Teams
- Click the team dropdown in the header
- Select a different team
- Your workspace selection resets (enters team-only mode)
- Select a workspace to continue working
Switching Workspaces
- Click the workspace dropdown in the header
- Select a workspace, or choose "No Workspace (Team Mode)" for team-only mode
- Features update based on your selection
From the Pages
You can also select teams and workspaces from their respective pages:
- Teams Page (
/teams): View all your teams, click to select - Workspaces Page (
/workspaces): View all workspaces in current team, click to select
Navigation Changes by Context
The sidebar navigation adapts to your current context:
Always Visible (Any Mode)
- Dashboard
- Teams
- Workspaces
- Analytics (Team analytics in team-only mode)
- Settings
- Billing
Workspace Required
These features only appear when a workspace is selected:
- Templates
- Template Gallery
- Asset Gallery
- Document Logs
- API Keys
- API Playground
- Webhooks
If you try to access a workspace-required feature without a workspace selected, you'll be prompted to select one.
Analytics: Team vs. Workspace
Analytics are split into two tabs based on what you're measuring:
Team Analytics
Financial and billing-focused metrics:
- Wallet: Subscription quota, premium credits, billing breakdown
- Attribution: Which templates consume the most credits
- Projections: When you might run out of resources
Access: Available to team Owners and Admins
Workspace Analytics
Operational and performance metrics:
- Health: Success rates, error breakdowns, processing times
- Insights: Top templates, peak usage times, volume trends
Access: Available in Team + Workspace mode to all workspace members
API Keys and Workspaces
API keys are scoped to workspaces. This means:
- Each workspace has its own set of API keys
- An API key from Workspace A cannot access Workspace B
- When you generate documents via API, they belong to the workspace of the API key used
Best Practice
Create separate API keys for:
- Different environments (dev/staging/prod)
- Different applications
- Different access levels
Webhooks and Workspaces
Webhook subscriptions are workspace-scoped:
- Webhooks in Workspace A only receive events from Workspace A
- Events from Workspace B go to Workspace B's webhooks
This allows you to:
- Route production events to your production systems
- Route development events to testing endpoints
- Keep different projects completely isolated
Document Logs and Workspaces
Document logs show documents generated within the current workspace:
- Each workspace maintains its own log history
- Filtering and search only applies to the current workspace
- Bulk actions only affect documents in the current workspace
Common Scenarios
Setting Up for the First Time
- Create your team (done during signup)
- Create your first workspace (e.g., "Production")
- Create templates within the workspace
- Generate API keys for your application
Onboarding a New Team Member
- Go to Team Settings
- Invite the new member with appropriate role
- They can then access workspaces based on their role
Separating Development and Production
- Create a "Development" workspace
- Create a "Production" workspace
- Use separate API keys for each environment
- Set up webhooks pointing to appropriate endpoints
Managing Multiple Clients
- Create a workspace for each client
- Keep templates, API keys, and logs isolated
- Assign team members to relevant workspaces
FAQ
Can I move templates between workspaces?
Not directly. You would need to export the template schema and import it in the new workspace.
Can one user belong to multiple teams?
Yes, you can be a member of multiple teams. Switch between them using the team selector.
Who can create workspaces?
Team Owners and Admins can create new workspaces.
Are credits shared across workspaces?
Yes, document credits are at the team level and shared across all workspaces.
Can I delete a workspace?
Yes, team Owners and Admins can delete workspaces. This permanently removes all templates, logs, API keys, and webhooks in that workspace.
Related: Team Management | Settings | API Keys