Objective
This article aims to guide you on how to grant access to the "Monitor > Calls" tab in the Twilio Console. It addresses the common issue of finding the appropriate role that allows users to view call logs without granting full developer access.
Product
Programmable Voice
Environment
legacy Twilio Console
User Account Permission/Role(s) Required
- Developer Role
- Support Role
Procedure
- Identify the Required Access:
- Determine if the user needs access to both call logs and messaging logs.
- Assigning the Developer Role:
- Navigate to the Twilio Console.
- Go to the "Users" section under "Account Settings."
- Select the user you wish to modify.
- Assign the "Developer" role to grant access to call logs. This role allows users to view call logs without full Console access.
- Alternative: Assigning the Support Role:
- If the Developer role is too broad, consider using the "Support" role.
- This role provides access to both Voice and Messaging logs, suitable for users who need to monitor logs without full developer permissions.
- Accessing Subaccounts:
- Ensure the user has the appropriate role assigned for both parent and subaccounts.
- If the user cannot access the logs in a subaccount, verify the role assignment in the subaccount settings.
- Verification:
- After assigning the role, have the user log in to the Twilio Console and verify access to the "Monitor > Calls" tab.
Additional Information
- HIPAA Compliance: If dealing with sensitive data, consider using API access to pull call logs without exposing unnecessary information.
- Account Structure: Consider separating production and staging environments into different accounts for better role management.