User-based permissions in Genesy allow you to control what each user can see, change, import, export, and spend inside your workspace.
Use them to:
Protect sensitive data (lists, contacts, companies).
Avoid unwanted imports/exports or mass changes.
Limit who can create campaigns and send messages.
Control who can view billing and who can spend credits.
1. Before you start
To configure other users’ permissions you must:
Have administrator permissions.
Be able to see the Team Members section in the left menu.
If you do not see Team Members, you do not have admin rights.
In that case, contact your Customer Success Manager so they can grant you admin permissions.
2. How to set user limits (step by step)
2.1. Open “Team”
Log in to Genesy.
In the left-hand menu, click Settings > Team.
You will see the list of all users in your workspace, along with their roles and status.
2.2. Locate the user
In the user list:
Find the user whose permissions you want to change.
You can scroll or use any available filters/search (if present in your version) to quickly locate them.
You can repeat the process for as many users as needed.
2.3. Open the permissions panel
In the Actions column for that user, click the user icon with a star (permissions icon).
This opens the Edit Permissions panel for that specific user.
All changes in this panel apply only to the selected user.
2.4. Permission categories
In the Edit Permissions panel you will see three main categories:
Lists configuration
Campaigns configuration
General Settings
Click on each category (▶️) to expand it and adjust the options.
3. Lists configuration (data access & actions)
Use Lists configuration to control how much of the database a user can see and what they can do with it.
3.1. List visibility
User can view all lists
The user can see all lists in the workspace.User can only view assigned lists
The user can only see lists explicitly assigned to them (or their role, depending on your internal process).
When to use:
Give “view all lists” to admins or managers who need full visibility.
Use “only assigned lists” for SDRs, BDRs, or external users so they only see the segments they should work on.
3.2. Edit & delete access
User can edit & delete records (leads, companies, or lists)
The user can edit and delete:Leads/contacts
Companies
Lists
User cannot edit or delete any records
The user can view data but cannot modify or delete it.
When to use:
Enable edit & delete for trusted users who own data quality (Ops, managers).
Disable for users who should not be able to accidentally delete or change large volumes of data (e.g. junior SDRs, external agencies).
3.3. Import access
User can import new leads or companies
The user can upload CSVs and create new records (leads or companies).User cannot import
The user cannot launch imports.
When to use:
Restrict imports to data owners / ops to avoid:
Duplicates
Low-quality data
Wrong mapping of fields
3.4. Export access
User can export leads or companies
The user can export data from Genesy (e.g., to CSV or integrated tools).User cannot export
The user cannot export data.
When to use:
Allow exports for admins and specific managers who need offline analysis.
Block exports for most users if you want to:
Reduce the risk of data leakage.
Keep better control over what leaves the platform.
4. Campaign configuration (campaigns & identities)
Use Campaign configuration to define what users can do in campaigns and which identities they can use.
4.1. Campaign creation
User can create and edit campaigns
The user can:Create new campaigns.
Edit existing campaigns.
User cannot create or modify campaigns
The user cannot create new campaigns or change existing ones.
When to use:
Allow campaign creation for:
Growth / Marketing / Sales Ops.
Senior users who design flows and cadences.
Restrict creation for:
SDRs/BDRs who should only execute existing campaigns.
External contractors who should not alter your strategy.
4.2. Identities access
User has access to all identities
The user can:Use any sending identity (email / LinkedIn profile, etc.).
See messages associated with all identities.
User has access to specific identities only
The user can use only the identities you assign to them.
When to use:
Give “all identities” to admins or team leads who might send on behalf of several identities.
Limit to specific identities for:
Individual reps (their own mailbox/profile only).
Agencies using restricted identities.
This is especially useful to avoid someone sending emails or messages from the wrong identity.
5. General settings (account & credits)
Use General settings to control access to account configuration and how much each user can spend in credits.
5.1. Account configuration
User can access general account settings
User can access:Global account configuration
Billing details
General parameters
User cannot access general account settings
User has no access to these settings.
When to use:
Restrict this to account owners, admins, or finance.
Avoid giving it to normal users; they typically do not need to see billing or change global settings.
5.2. Credits usage
User can purchase and consume credits
The user can:Buy credits.
Use credits.
User can only consume credits
The user can use credits, but cannot purchase more.User can only consume limited credits
The user can use credits, but only up to a defined limit (configured by an admin/CSM according to your agreement or internal policy).
When to use:
Allow purchase & consume only for:
Admins or owners responsible for budgets.
Use “only consume” for:
Team members who should be able to work normally but not trigger additional spend.
Use “only consume limited credits” for:
Teams where you want to cap usage (e.g., test environments, external teams, or junior users).
Cases where you want hard, per-user limits.
6. Example permission setups (recommended patterns)
You can use the following patterns as a starting point and adapt them to your processes.
6.1. Admin / Owner
List visibility: view all lists
Edit & delete: can edit & delete records
Import: can import new leads/companies
Export: can export leads/companies
Campaign creation: can create and edit campaigns
Identities access: all identities
Account configuration: can access account settings
Credits usage: can purchase and consume credits
Good for: founders, ops leads, technical admins.
6.2. Sales / SDR Manager
List visibility: view all lists
Edit & delete: can edit & delete records (optional, depending on governance)
Import: usually can import (if they own data quality).
Export: can export (for reporting).
Campaign creation: can create and edit campaigns
Identities access: all identities or at least their team’s identities.
Account configuration: cannot access (optional)
Credits usage: usually only consume credits.
6.3. SDR / BDR (internal)
List visibility: only view assigned lists
Edit & delete:
Optional: cannot edit or delete if you want full protection.
Or can edit, but no delete, depending on your process (if the product supports that granularity in future).
Import: cannot import
Export: cannot export
Campaign creation:
Either cannot create (only work with existing campaigns), or
can create and edit if they are senior enough.
Identities access: only their own identity
Account configuration: cannot access
Credits usage: only consume credits or only consume limited credits
6.4. External agency / contractor
List visibility: only assigned lists
Edit & delete: often cannot edit or delete records (or very limited).
Import: cannot import
Export: cannot export (to prevent taking data out).
Campaign creation: optional; in many setups, can create and edit campaigns only for their assigned scope.
Identities access: only specific identities dedicated to them.
Account configuration: cannot access
Credits usage: only consume limited credits
7. Good practices when managing permissions
Start with the minimum:
Give each user only the permissions they truly need to perform their role. You can always add more later.Standardize “role templates” internally:
Decide as a team what a “Sales rep”, “Manager” or “Admin” should be allowed to do, and configure each user accordingly.Review permissions periodically:
When someone changes role, joins, or leaves, review their configuration in Team Members.Protect exports and billing:
Keep export rights and purchase credits rights restricted to a very small group of trusted users.Use list visibility and identities to protect sensitive accounts:
Assign specific lists and identities only to the users who should work them.