instantly-enterprise-rbac
Configure Instantly 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 Instantly. Trigger with phrases like "instantly SSO", "instantly RBAC", "instantly enterprise", "instantly roles", "instantly permissions", "instantly SAML".
- License 许可
- MIT
- 最近更新
- 2026-05-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- instantly-enterprise-rbac
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- version
- 1.0.0
- description
- Configure Instantly 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 Instantly. Trigger with phrases like "instantly SSO", "instantly RBAC", "instantly enterprise", "instantly roles", "instantly permissions", "instantly SAML".
- allowed-tools
- Read, Write, Edit
- compatible-with
- claude-code, codex, openclaw
03 SKILL.md 正文
Instantly Enterprise RBAC
Overview
Manage team access to Instantly email outreach campaigns, sending accounts, and lead lists. Instantly uses per-seat pricing with workspace-level roles: Owner, Admin, and Member.
Prerequisites
- Instantly Growth or Hypergrowth plan (per-seat + sending volume pricing)
- Workspace owner or admin role
- Email sending accounts connected and warmed up
Instructions
Step 1: Define Team Roles and Sending Permissions
# instantly-access-matrix.yaml
roles:
owner:
permissions: [manage_billing, manage_members, all_campaigns, all_accounts, analytics]
admin:
permissions: [manage_members, all_campaigns, all_accounts, analytics]
member:
permissions: [own_campaigns, assigned_accounts, own_analytics]
# Sending account assignment
sending_accounts:
"john@outreach.company.com": assigned_to: john@company.com
"sales1@outreach.company.com": assigned_to: sarah@company.com
"sales2@outreach.company.com": assigned_to: sarah@company.com
Step 2: Invite Team Members with Role Assignment
set -euo pipefail
# Invite an SDR as a Member (limited to own campaigns)
curl -X POST https://api.instantly.ai/api/v1/team/invite \
-H "Authorization: Bearer $INSTANTLY_API_KEY" \
-d '{"email": "sdr@company.com", "role": "member"}'
# List team members
curl https://api.instantly.ai/api/v1/team/members \
-H "Authorization: Bearer $INSTANTLY_API_KEY" | jq '.[] | {email, role, status}'
Step 3: Assign Sending Accounts to Specific Members
Prevent cross-contamination of email reputation by assigning each warmed sending account to exactly one team member:
set -euo pipefail
curl -X POST https://api.instantly.ai/api/v1/account/assign \
-H "Authorization: Bearer $INSTANTLY_API_KEY" \
-d '{"account_email": "john@outreach.company.com", "assigned_to": "john@company.com"}'
Step 4: Set Campaign Visibility Rules
- Private campaigns: Only the creator and admins can see them
- Team campaigns: Visible to all workspace members
- Configure default visibility in Workspace Settings > Campaigns > Default Visibility
Step 5: Monitor Sending Limits and Deliverability
set -euo pipefail
# Check sending limits and current usage per account
curl https://api.instantly.ai/api/v1/account/status \
-H "Authorization: Bearer $INSTANTLY_API_KEY" | \
jq '.accounts[] | {email, daily_limit, sent_today, warmup_status, reputation_score}'
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| Member can't see campaign | Campaign set to private | Change visibility or add member as collaborator |
| Sending account bounce spike | Account not fully warmed | Reduce daily limit, extend warmup period |
403 on team endpoint |
User is Member, not Admin | Promote to Admin for team management |
| Duplicate leads across SDRs | No lead deduplication | Enable workspace-level lead dedup in settings |
Examples
Basic usage: Apply instantly enterprise rbac to a standard project setup with default configuration options.
Advanced scenario: Customize instantly enterprise rbac for production environments with multiple constraints and team-specific requirements.
Output
- Configuration files or code changes applied to the project
- Validation report confirming correct implementation
- Summary of changes made and their rationale
Resources
- Official Instantly Enterprise Rbac documentation
- Community best practices and patterns
- Related skills in this plugin pack
04 同仓库更多 Skills
zustand-store-ts
Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.
zustand-store-creator
Zustand Store Creator - Auto-activating skill for Frontend Development. Triggers on: zustand store creator, zustand store creator Part of the Frontend Development skill category.
zero-trust-config-helper
Zero Trust Config Helper - Auto-activating skill for Security Advanced. Triggers on: zero trust config helper, zero trust config helper Part of the Security Advanced skill category.
zapier-integration-helper
Zapier Integration Helper - Auto-activating skill for Business Automation. Triggers on: zapier integration helper, zapier integration helper Part of the Business Automation skill category.
zai-cli
Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP. Use when user needs image/video analysis, OCR, UI-to-code conversion, error diagnosis, real-time web search, web page to markdown extraction, or GitHub code exploration. Trigger with phrases like "analyze this image", "search the web for", "read this page", "explore this repo", or "use zai". Requires Z_AI_API_KEY.
yt-research
Research competitor YouTube channels, niches, and trending topics for your content strategy. Use this skill whenever the user says "research channels", "analyze competitors", "find trending topics", "niche analysis", "competitive research", "what are other creators doing", "scrape YouTube channels", or wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.