smithery/jeremylongshore

juicebox-enterprise-rbac

Configure Juicebox team access. '

Installation

$ npx skills add smithery/jeremylongshore --skill juicebox-enterprise-rbac

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/jeremylongshore · top by installs.

npx skills add smithery/jeremylongshore

Browse all from smithery/jeremylongshore

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.16.0
LicenseMIT
CompatibilityDesigned for Claude Code
Allowed toolsRead, Write, Edit, Grep
Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 5,558 B
  • docs SUMMARY.md 331 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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

Role Permissions Scope
Workspace Admin Manage seats, billing, API keys, configure integrations Entire workspace
Recruiter Search, enrich, access contact info, run outreach campaigns All datasets
Analyst Search and enrich profiles, view analytics dashboards Assigned datasets
Sourcer Search and enrich only, no contact reveal or outreach Assigned datasets
Viewer View saved searches and reports, no data access or export Read-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

Issue Cause Fix
403 on contact reveal endpoint User role lacks contact permission Upgrade to recruiter role or request admin approval
Export returns empty results Dataset not assigned to user Add dataset to user's access list in workspace settings
API rate limit exceeded Too many enrichment calls per hour Check role-based rate limits, batch requests
Saved search not visible Search created in different dataset scope Verify dataset access or share search explicitly
Seat limit reached All workspace licenses used Remove inactive members or upgrade plan

Prerequisites

  • An approved role matrix, sandbox workspace with synthetic fixtures, access-review owner, source/destination allowlists, suppression controls, secret references, and a tested access-revocation path.

Instructions

  1. Test role changes in a sandbox and enforce least privilege; reject broad grants, unapproved data sources/destinations, and literal credentials.
  2. Verify denial paths, suppression, audit-log redaction, retention, and contacts_exported=0 using aggregate evidence only.
  3. Canary one role assignment at a time; halt on unauthorized access, scope, policy, or retention drift and revoke the change immediately.
  4. Promote only after named-owner approval, then retain a redacted access review and delete temporary fixtures.

Output

Produce an RBAC receipt with environment, role and permitted scope, denial-test outcome, source/destination/suppression/no-export assertions, reviewer approval, revocation/rollback reference, and retention/deletion proof. Exclude user identities, records, and secrets.

Examples

env=staging; role=report-viewer; scope=aggregate-only; denialtest=pass; suppression=pass; contactsexported=0; revocation=tested is a valid role-change receipt.

Resources

  • Juicebox Enterprise
  • Juicebox API Docs

Next Steps

See juicebox-security-basics.