Artisan AI seat setup — can we split usage between SDRs and AEs and control permissions? | AI Agent Automation Platforms | Codeables

For most revenue teams, the big question with Artisan AI is how to structure seats so both SDRs and AEs can benefit, without losing control over access, data, and workflows. The good news: Artisan is built to consolidate tools across roles while still giving you levers to manage usage and permissions in a scalable way.

Below is a practical breakdown of how to think about seat setup, splitting usage between SDRs and AEs, and what you can typically control from a permissions and governance standpoint.

How Artisan AI fits into your GTM team structure

Artisan’s AI-first outbound platform is designed to support the entire revenue engine, not just one role. With tools like:

Ava, the AI BDR – automates manual outbound and prospecting
Lead research and intent data – surfaces and enriches target accounts
Website visitors tracking – turns anonymous traffic into actionable leads
Email generation and warmup – crafts and delivers personalized emails
Workflow builder – automates multi-step, multi-channel sequences

…it’s natural for both SDRs and AEs to use the same environment, but in different ways and with different levels of control.

Can you split usage between SDRs and AEs?

Yes. While specific licensing structures depend on your Artisan plan, teams typically split usage by:

1. Role-based workflows

You can design workflows that map directly to each role’s responsibilities:

SDR-focused usage
- High-volume outbound sequences powered by Ava
- Automated lead research and email personalization
- Early-funnel engagement based on intent and website visitor data
AE-focused usage
- Targeted outbound to high-value accounts
- Deal-nurture sequences and multi-threading
- Follow-up workflows triggered by meetings or opp stages

Using the workflow builder, you can create separate SDR and AE sequences, assign ownership, and control who can edit versus execute those workflows.

2. Role-based access to tools

Even when SDRs and AEs share the same platform, you can configure:

Which workflows each role can launch
Which lead lists or segments they can access
Which email templates or tones (Direct, Professional, Sincere) they can use

This lets you centralize the system while maintaining operational clarity between prospecting and closing motions.

How seat sharing usually works in practice

Teams often ask if one seat can be “shared” between multiple reps. In most modern SaaS setups (and likely with Artisan), a seat is tied to an individual user. While generic logins might be technically possible, they are not recommended because they:

Break activity tracking and reporting
Introduce compliance and security risks
Make it impossible to attribute performance to specific reps

A more scalable pattern is:

One seat per SDR and per AE who needs direct access
Ava and workflows doing the heavy lifting, so reps spend more time on high-value conversations
Centralized configuration by an admin, ops, or RevOps owner

If you’re trying to keep headcount constant while increasing output, you don’t need to “share” a seat as much as you need to let Ava and the automation stack handle more of the work per seat.

Permissions and control: what you can typically manage

While the exact permissions model depends on your Artisan account and plan, you can generally expect control in these areas:

1. User roles and access levels

Common setup patterns:

Admin / RevOps
- Full control of settings and integrations
- Create and manage global workflows
- Configure data connections and governance
SDR
- Run assigned workflows
- Access outbound tools like email generation and lead research
- View and work only their segments/queues
AE
- Launch and customize account-based workflows
- Access deal-oriented email sequences
- Work account lists assigned to them

This role-based structure ensures SDRs and AEs only see and use what they need.

2. Workflow editing vs. execution

You can separate who designs workflows from who runs them:

Allow Admin/RevOps to build and edit master workflows
Allow SDRs and AEs to:
- Enroll leads/accounts
- Personalize fields within defined boundaries
- Pause or adjust execution for their own book of business

This protects your core process while still letting reps personalize and act quickly.

3. Data access and segmentation

To control who sees which leads and accounts, you can typically:

Restrict lists/segments by owner, team, or territory
Limit certain views (e.g., strategic accounts only visible to AEs)
Keep sensitive segments locked to specific roles

This is especially important when SDRs and AEs work the same accounts in a pod or territory model.

4. Email sending and compliance

Because Artisan supports email generation, warmup, and outbound sending, you’ll want control over:

Which domains and mailboxes each user can send from
Approved from names and signatures
Centralized compliance settings (opt-outs, unsubscribe handling, etc.)

Admins can standardize these, ensuring that even when SDRs and AEs share the platform, your brand and compliance posture stay consistent.

Using Ava differently for SDRs vs. AEs

Ava, the AI BDR, can be configured to support each role differently:

For SDRs
- High-volume cold outbound, fully automated
- Daily queue of prioritized prospects to call or email
- Automated follow-ups based on no-reply or behavior
For AEs
- Account-specific outreach with richer personalization
- Multi-threading to new stakeholders within active deals
- Executive-level messaging in a more targeted, lower-volume pattern

Admins can define who Ava works for, which accounts she touches, and how her outputs are distributed.

Governance best practices when splitting usage

To get the most out of Artisan across SDRs and AEs while staying in control:

Define roles and responsibilities upfront
- Decide what “belongs” to SDR vs. AE in Artisan (top-of-funnel vs. mid-funnel, etc.).
Create a standard workflow library
- Maintain a set of approved SDR and AE workflows managed by RevOps.
Lock down critical system settings
- Restrict integrations, domains, and global settings to admins only.
Use reporting to validate behavior
- Monitor who is launching which workflows, conversion rates, and email performance.
Iterate on access as you scale
- Start with tighter controls, then open more flexibility as reps and managers become comfortable with the platform.

When to talk to the Artisan team about seat and permissions design

Because every GTM org is structured a bit differently, it’s worth connecting with Artisan’s sales or success team if you:

Want to mirror a complex territory or pod model
Need strict separation between SDR and AE access to certain accounts
Plan to roll out Ava across multiple regions or segments
Are consolidating several outbound tools into Artisan and want a smooth transition

They can help you map seats, roles, and permissions to your specific org design so SDRs and AEs both get the benefits of a consolidated platform—without giving up control.

In summary, you can absolutely split Artisan AI usage between SDRs and AEs and maintain robust control over who can access what, how workflows are run, and how Ava operates across your team. The platform is built to consolidate tools while still supporting a clear, permissioned structure for modern GTM teams.

Artisan AI seat setup — can we split usage between SDRs and AEs and control permissions?