Understanding how to manage user access in Account Engagement (formerly Pardot) is crucial for maintaining data security and ensuring the right level of access for each team member. Here’s a breakdown of five key areas that are essential when configuring and auditing access in the platform:
1. User Roles
– Assign roles based on the principle of least privilege to minimize security risks.
– Utilize default roles or create custom roles to match your organization’s specific needs.
– Regularly review and update roles to accommodate changes in responsibilities.
2. User Groups
– Organize users into groups for easier management and to streamline sharing of marketing assets.
– Use groups to control access to folders and prospect lists, ensuring users only see what they need.
– Periodically audit group memberships to keep them aligned with team changes.
3. Folder Permissions
– Set up folder permissions to control who can view, edit, or delete marketing materials.
– Leverage view-only permissions for users who need access but should not alter content.
– Review folder structures and permissions settings regularly for consistency and security.
4. Email Sending and Approval
– Implement email sending restrictions to prevent unauthorized email distribution.
– Set up approval processes to ensure emails are reviewed for quality and compliance before sending.
– Train users on the importance of compliance with sending policies to protect your company’s reputation.
5. Audit Trail and Monitoring
– Use the audit trail feature to track changes and identify any unauthorized or suspicious activity.
– Monitor login history to detect irregular access patterns or failed login attempts.
– Schedule regular audits to assure continuous compliance and to identify areas that may require attention.
By focusing on these areas, you can maintain a secure and well-organized Account Engagement environment that aligns with your organization’s governance policies and protects the integrity of your marketing efforts.
You can read it here: https://sfdc.blog/PsEVn
Source from salesforceben(dot)com