Claude Workspace Admin

Administer a Claude Team or Enterprise workspace: members, roles, connectors, SSO, offboarding. Scoped, verified, logged.

Business & Ops / Operationsclaude-adminaccess-management
by AgentVoltv1.0.0
Free to sign up · every skill included with AgentVolt Pro

Before & after

Same prompt, same agent — the only difference is the skill.

Prompt“Walk me through customer success workspace setup.”
Beforegeneric AI agent
Setting up a CS workspace is a pretty important step. There are a lot of components to consider—you'll want to think about your team structure, how you'll organize customer accounts, what communication tools you'll use, and how you'll track interactions. You might also want to consider automation for common tasks, maybe templates for responses, and some kind of tagging or labeling system. I can help you think through this, but it would be useful to know more about the size of your team, the types of customers you support, and what your main pain points are right now. Once I understand your situation better, I can offer more specific guidance.
Afterwith Claude Workspace Admin
CS WORKSPACE SETUP CHECKLIST

STEP 1: TEAM STRUCTURE & ROLES
□ Define CS team hierarchy (manager, specialists, support staff)
□ Assign account ownership: tier mapping (enterprise → dedicated, mid-market → shared, SMB → queue)
□ Create role templates: Read+edit = agent; Read-only = reporter; Admin = manager
□ Set escalation paths: Issue type → owner → manager approval

STEP 2: CUSTOMER DATA ORGANIZATION
□ Create customer list view: Filter by segment, status, health score
□ Set up custom fields: Onboarding date, MRR, renewal month, support tier
□ Tag taxonomy: By-product, by-issue-type (billing, technical, feature-request)
□ Import customer data with de-dupe check

STEP 3: COMMUNICATION & TRACKING
□ Enable ticket routing rules: Bug → engineering, billing → finance, product → PM
□ Set template library: Standard responses for 5 common queries
□ Enable activity logging: Auto-sync emails and meeting notes to customer record
□ Configure webhooks: Send customer updates to your CRM

STEP 4: AUTOMATION & REPORTING
□ Set up health score workflow: Monthly NPS + support ticket volume
□ Create alert: Inactive 30 days OR escalated ticket
□ Automation: Assign new tickets within 2 hours
□ Report: Monthly customer satisfaction by product, renewal pipeline

About this skill

Run your Claude or Cowork workspace without over-broad changes, leftover access, or connectors that can read more than they should. Every change is scoped to the smallest target, checked against current state, verified, and logged.

What it does

  • Scopes each change to one person, project, group, or the org, and flags when an org-wide fix is being used for a one-person problem
  • Runs offboarding in a safe order: re-share content, keep a second admin, remove the member, revoke connector grants on the other system, verify
  • Reviews connectors and integrations for least privilege, ownership, and write access nobody asked for
  • Checks member roles, admin count, stale invites, shared logins, and exposed credentials
  • Plans SSO and SCIM changes with a break-glass path and a pilot group, and explains which system owns membership

What you get

A change plan and a change record with before-state, scope, reversibility, verification, and reason for each change. Product-specific details are marked to verify in your admin settings instead of guessed.

Best for

Owners and admins of Claude Team or Enterprise workspaces at small and mid-size companies, and ops or IT leads who inherited the Claude org.

SKILL.md preview

SKILL.md
---
name: cs-workspace-admin
description: Administer a Claude or Cowork workspace (a claude.ai Team or Enterprise organization) - members and roles, access, org settings, connectors and integrations, shared projects, usage, SSO and SCIM - with every change scoped to the smallest target, checked against current state, verified, and logged. Use when the user says "add someone to our Claude workspace", "offboard this person from Claude", "who should be an admin", "should we enable this connector for everyone", "someone can't see our shared project", "audit our Claude org", "we set up SSO and now people can't log in", or "clean up seats and access".
---

# Claude Workspace Admin

… (sign up to view the full skill)
Sign up to view, copy, and install the full skill

More business & ops skills

View all Business & Ops skills →