JU

juicebox-enterprise-rbac

Guides the implementation of team roles and security policies for Juicebox workspaces.

Install

mkdir -p .claude/skills/juicebox-enterprise-rbac && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5327" && unzip -o skill.zip -d .claude/skills/juicebox-enterprise-rbac && rm skill.zip

Installs to .claude/skills/juicebox-enterprise-rbac

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Configure Juicebox team access.
31 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Verify user permissions for specific actions
  • Assign roles to workspace members
  • Revoke workspace access
  • Log access actions for audit compliance
  • Manage dataset access lists

How it works

It checks user roles against a permission map and verifies dataset access lists to determine if an action is authorized.

Inputs & outputs

You give it
User ID, action, and dataset ID
You get back
Boolean indicating access permission

When to use juicebox-enterprise-rbac

  • Set up workspace admin roles
  • Restrict export access for analysts
  • Implement SOC 2 compliance logging
  • Configure team seat access

About this skill

Juicebox Enterprise RBAC

Overview

Juicebox provides AI-powered people search and analysis for recruiting and sales teams. Enterprise RBAC controls who can search candidate databases, enrich profiles with contact info, trigger outreach sequences, and export data. Workspace admins manage team seats and API usage limits. Analysts run searches but may be restricted from exporting PII. Viewers can review saved searches without accessing raw contact data. SOC 2 compliance requires audit logging on all data enrichment and export actions.

Role Hierarchy

RolePermissionsScope
Workspace AdminManage seats, billing, API keys, configure integrationsEntire workspace
RecruiterSearch, enrich, access contact info, run outreach campaignsAll datasets
AnalystSearch and enrich profiles, view analytics dashboardsAssigned datasets
SourcerSearch and enrich only, no contact reveal or outreachAssigned datasets
ViewerView saved searches and reports, no data access or exportRead-only

Permission Check

async function checkJuiceboxAccess(userId: string, action: string, datasetId: string): Promise<boolean> {
  const response = await fetch(`${JUICEBOX_API}/v1/workspaces/${WORKSPACE_ID}/permissions`, {
    headers: { Authorization: `Bearer ${JUICEBOX_API_KEY}`, 'Content-Type': 'application/json' },
  });
  const perms = await response.json();
  const user = perms.members.find((m: any) => m.id === userId);
  if (!user) return false;
  const rolePerms = ROLE_PERMISSIONS[user.role];
  return rolePerms?.[action] && (user.datasets.includes(datasetId) || user.role === 'admin');
}

Role Assignment

async function assignWorkspaceRole(email: string, role: string, datasets: string[]): Promise<void> {
  await fetch(`${JUICEBOX_API}/v1/workspaces/${WORKSPACE_ID}/members`, {
    method: 'POST',
    headers: { Authorization: `Bearer ${JUICEBOX_API_KEY}`, 'Content-Type': 'application/json' },
    body: JSON.stringify({ email, role, datasetAccess: datasets }),
  });
}

async function revokeAccess(email: string): Promise<void> {
  await fetch(`${JUICEBOX_API}/v1/workspaces/${WORKSPACE_ID}/members/${email}`, {
    method: 'DELETE',
    headers: { Authorization: `Bearer ${JUICEBOX_API_KEY}` },
  });
}

Audit Logging

interface JuiceboxAuditEntry {
  timestamp: string; userId: string; role: string;
  action: 'search' | 'enrich' | 'contact_reveal' | 'export' | 'outreach' | 'role_change';
  datasetId: string; recordCount?: number; result: 'allowed' | 'denied';
}

function logAccess(entry: JuiceboxAuditEntry): void {
  console.log(JSON.stringify({ ...entry, workspaceId: process.env.JUICEBOX_WORKSPACE_ID }));
}

RBAC Checklist

  • Workspace admin role limited to designated team leads
  • Contact reveal and export restricted to recruiter role and above
  • Dataset access scoped per team to prevent cross-team data leakage
  • API key usage monitored with rate limits per role
  • Viewer role enforced for stakeholders who only need reporting
  • All enrichment and export actions logged for SOC 2 compliance
  • Quarterly access review to remove departed team members

Error Handling

IssueCauseFix
403 on contact reveal endpointUser role lacks contact permissionUpgrade to recruiter role or request admin approval
Export returns empty resultsDataset not assigned to userAdd dataset to user's access list in workspace settings
API rate limit exceededToo many enrichment calls per hourCheck role-based rate limits, batch requests
Saved search not visibleSearch created in different dataset scopeVerify dataset access or share search explicitly
Seat limit reachedAll workspace licenses usedRemove inactive members or upgrade plan

Resources

  • Juicebox Enterprise
  • Juicebox API Docs

Next Steps

See juicebox-security-basics.

When not to use it

  • When attempting to assign roles without workspace admin privileges

Prerequisites

JUICEBOX_API_KEYWORKSPACE_ID

Limitations

  • Contact reveal and export restricted to recruiter role and above

How it compares

It centralizes permission logic and audit logging, ensuring consistent security enforcement across the workspace.

Compared to similar skills

juicebox-enterprise-rbac side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
juicebox-enterprise-rbac (this skill)127dReviewIntermediate
api-security-best-practices156moReviewIntermediate
api-security-testing17moReviewAdvanced
scanning-api-security227dReviewAdvanced

Try saying

Example prompts that trigger this skill in your AI assistant.

More by jeremylongshore

View all by jeremylongshore

analyzing-logs

jeremylongshore

Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.

14123

ollama-setup

jeremylongshore

Configure auto-configure Ollama when user needs local LLM deployment, free AI alternatives, or wants to eliminate hosted API costs. Trigger phrases: "install ollama", "local AI", "free LLM", "self-hosted AI", "replace OpenAI", "no API costs". Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

1167

backtesting-trading-strategies

jeremylongshore

Backtest crypto and traditional trading strategies against historical data. Calculates performance metrics (Sharpe, Sortino, max drawdown), generates equity curves, and optimizes strategy parameters. Use when user wants to test a trading strategy, validate signals, or compare approaches. Trigger with phrases like "backtest strategy", "test trading strategy", "historical performance", "simulate trades", "optimize parameters", or "validate signals".

1071

generating-database-seed-data

jeremylongshore

Process this skill enables AI assistant to generate realistic test data and database seed scripts for development and testing environments. it uses faker libraries to create realistic data, maintains relational integrity, and allows configurable data volumes. u... Use when working with databases or data models. Trigger with phrases like 'database', 'query', or 'schema'.

1033

cursor-codebase-indexing

jeremylongshore

Execute set up and optimize Cursor codebase indexing. Triggers on "cursor index setup", "codebase indexing", "index codebase", "cursor semantic search". Use when working with cursor codebase indexing functionality. Trigger with phrases like "cursor codebase indexing", "cursor indexing", "cursor".

885

testing-mobile-apps

jeremylongshore

Execute mobile app testing on iOS and Android devices/simulators. Use when performing specialized testing. Trigger with phrases like "test mobile app", "run iOS tests", or "validate Android functionality".

810

You might also like

api-security-best-practices

davila7

Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities

1554

api-security-testing

Ed1s0nZ

API安全测试的专业技能和方法论

18

scanning-api-security

jeremylongshore

Detect API security vulnerabilities including injection, broken auth, and data exposure. Use when scanning APIs for security vulnerabilities. Trigger with phrases like "scan API security", "check for vulnerabilities", or "audit API security".

26

openrouter-data-privacy

jeremylongshore

Implement data privacy controls for OpenRouter requests. Use when handling PII or meeting compliance requirements. Trigger with phrases like 'openrouter privacy', 'openrouter pii', 'openrouter gdpr', 'openrouter data protection'.

05

apollo-security-basics

jeremylongshore

Apply Apollo.io API security best practices. Use when securing Apollo integrations, managing API keys, or implementing secure data handling. Trigger with phrases like "apollo security", "secure apollo api", "apollo api key security", "apollo data protection".

13

perplexity-enterprise-rbac

jeremylongshore

Configure Perplexity enterprise SSO, role-based access control, and organization management. Use when implementing SSO integration, configuring role-based permissions, or setting up organization-level controls for Perplexity. Trigger with phrases like "perplexity SSO", "perplexity RBAC", "perplexity enterprise", "perplexity roles", "perplexity permissions", "perplexity SAML".

04

Search skills

Search the agent skills registry