Skip to main content

Overview

Role-Based Access Control (RBAC) lets you define exactly what each user in your organization can see and do. Instead of granting blanket access to everyone, you assign roles that carry specific permissions — keeping sensitive data protected and workflows clean. Navigate to Settings > Roles to manage roles and permissions.
Role-based access control showing permission categories and checkboxes

Default Roles

Pingtree comes with three built-in roles that cover the most common team structures. These roles cannot be deleted, but their permissions can be reviewed at any time.
RoleDescriptionAccess Level
AdminFull access to all platform features and settingsUnrestricted
ManagerAccess to campaign management, reports, and user oversightBroad, excluding org-level settings
UserStandard access to assigned campaigns and basic reportingLimited to assigned resources
Tip: The Admin role has full access by default and bypasses all permission checks. Assign Admin sparingly — only to team members who genuinely need full platform control.

Creating a Custom Role

If the default roles don’t match your team’s structure, create a custom role with exactly the permissions you need.
  1. Go to Settings > Roles.
  2. Click + New Role.
  3. Enter a Role Name and an optional Description.
  4. Toggle on the permissions this role should have (see Permission Categories below).
  5. Click Save.
The new role is immediately available to assign to users.

Permission Categories

Permissions are grouped by platform area. Each category contains individual access keys that control specific actions.
CategoryWhat It Covers
CampaignsView, create, edit, and delete campaigns
SourcesManage traffic sources (Custom Sources, Marketing Partners, Media Channels)
DistributionConfigure buyers, routing rules, and distribution logic
ReportsAccess lead reports, revenue reports, and analytics dashboards
SettingsModify organization settings, SMTP, and platform configuration
UsersInvite, edit, and manage users in the organization
BillingView and manage billing records and payment methods
IntegrationsConfigure third-party integrations
DomainsAdd and manage custom domains
FunnelsBuild and manage landing page funnels
Creative LibraryUpload and manage creative assets
SupportAccess and manage support tickets
Within each category, permissions follow a common pattern:
Permission KeyWhat It Allows
viewRead-only access to the feature
createAbility to add new records
editAbility to modify existing records
deleteAbility to remove records
exportAbility to export data

Assigning Roles to Users

  1. Go to Settings > Users or navigate to the user’s profile.
  2. Click Edit on the user you want to update.
  3. Select the desired role from the Role dropdown.
  4. Click Save.
The user’s permissions update immediately — no logout required.

Viewing and Editing Role Permissions

  1. Go to Settings > Roles.
  2. Click on any role to open its permission editor.
  3. Toggle individual permissions on or off.
  4. Click Save Changes.
Note: Changes to a role affect all users currently assigned that role. If you need to change permissions for just one person, use a user-level override instead (see below).

User-Level Permission Overrides

In some cases, a user needs slightly different access than their assigned role provides. Rather than creating a new role, you can override permissions at the user level.
  1. Open the user’s profile from Settings > Users.
  2. Click Permission Overrides.
  3. Toggle any permissions that should differ from the user’s role.
  4. Save the overrides.
Overrides are additive or restrictive on top of the base role — they do not replace it entirely.

Role Settings Reference

FieldDescription
NameThe display name of the role
DescriptionA short explanation of who the role is designed for
Is Custom RoleWhether this role was created by your organization
Is DefaultWhether this role is assigned to new users automatically
Is AdminWhether this role carries full administrative access
Is ActiveWhether this role can currently be assigned to users
Access KeysThe specific permission flags enabled for this role

Best Practices

  • Keep the number of custom roles small and named clearly — too many roles become hard to manage.
  • Use descriptive names that reflect the team function (e.g., “Campaign Manager”, “Finance Viewer”, “Affiliate Partner”).
  • Review role assignments periodically, especially after team changes.
  • Use user-level overrides sparingly — they can make access audits harder to follow.