Genesys Cloud provides outbound dialing roles and permissions that enable granular access control across campaign management, contact administration, and compliance functions. The platform offers three primary role levels—Outbound Administrator, Outbound Admin, and Outbound Agent—each with distinct permission scopes tailored to organizational hierarchies. The Outbound Administrator role grants comprehensive permissions including campaign and sequence management, contact and contact list administration with filtering capabilities, DNC (Do-Not-Call) list management, event log viewing, response set and rule set configuration, schedule creation, outbound settings editing, and wrap-up code mapping. All permissions support full CRUD (Create, Read, Update, Delete) operations. The Outbound Admin role encompasses additional administrative functions beyond the Administrator role, including attempt limit management, audit log viewing, callable time set configuration, and expanded campaign functions such as creation, deletion, editing, recycling, searching, starting, and stopping. This role maintains full CRUD capabilities across contact management, contact lists, contact list filters, DNC entries and lists, response sets, rule sets, schedules, and wrap-up code mappings. Outbound settings can be edited and viewed, and audit logs are accessible for compliance and monitoring purposes. The Outbound Agent role provides limited permissions for agent-level operations, enabling users to view and edit contacts within the Outbound Contact section and add contacts to do-not-call lists. These capabilities support core outbound dialing operations and contact management workflows. Permission changes take effect within minutes of assignment, enabling organizations to align access control with operational needs. For division-configured organizations, outbound administrators require division-specific permissions to perform campaign-related actions. Administrators should reference comprehensive Roles and permissions documentation for detailed feature permission specifications and division-specific configuration requirements.