Environment
U-M GPT, U-M Maizey
Issue
How to enable / disable debugging log access in U-M GPT or a U-M Maizey app.
Resolution
While the Debugging Log functions essentially the same way in U-M GPT and Maizey, who can enable it and how it’s enabled are different:
- U-M GPT: Users can enable or disable the Debugging Log in the U-M GPT interface and it only logs their interactions. However, even if it’s enabled, only conversations using an agentic model such as GPT-5.6 Sol (Agentic) are logged. A banner displays to indicate if the selected model supports logging.
- U-M Maizey: Only Maizey Project Admins can enable or disable the Debugging Log on an app. All user interactions with the app are logged. A banner displays informing users that logging is enabled.
U-M GPT
Enable Debugging Log
- Click the three dots and select Manage Debugging.
- Select the time period for which to enable the Debugging Log.
- Click Grant Access.
Conversations will be logged until the selected timeframe expires or access is revoked.
Disable Debugging Log
- Click the three dots and select Manage Debugging.
- Click Revoke Access.
U-M Maizey
Only Maizey Project Admins can enable or disable the Debugging Log on an app. All user interactions with the app are logged.
Enable Debugging Log
- Locate your app in the Maizey Apps listing.
- Click the three dots and select Configure App. The App Details page opens.
- For Agentic Chat Apps, click Manage Debugging Access. For Legacy Chat Apps, click Update for the Debugging Log Access setting.
- Select a time period for which to enable the Debugging Log.
- Click Grant Access.
Disable Debugging Log
- Locate your app in the Maizey Apps listing.
- Click the three dots and select Configure App. The App Details page opens.
- For Agentic Chat Apps, click Manage Debugging Access. For Legacy Chat Apps, click Update for the Debugging Log Access setting.
- Click Revoke Access.
Additional Information
Need additional information or assistance? Contact the ITS Service Center.