Which permission is required to configure HTTP timeout settings?

Which permission is required to configure HTTP timeout settings?

• A. User
• B. Space Admin
• C. System Admin
• D. Auditor

Answer: (C)

Configuring HTTP timeout settings is a system-wide change that affects the entire instance, not just a single space. It governs how long the server waits for a response before ending a request, so adjusting it sits at the global configuration level. System Admins have access to global, server-wide settings and maintenance tasks, making them the appropriate role to modify such parameters. In contrast, a Space Admin only handles settings within one space, not global server parameters; Auditors can view but not change configurations, and regular users lack permissions to alter settings. In some environments, timeout settings may also involve the reverse proxy or web server, which falls under system administration.

Configuring HTTP timeout settings is a system-wide change that affects the entire instance, not just a single space. It governs how long the server waits for a response before ending a request, so adjusting it sits at the global configuration level. System Admins have access to global, server-wide settings and maintenance tasks, making them the appropriate role to modify such parameters. In contrast, a Space Admin only handles settings within one space, not global server parameters; Auditors can view but not change configurations, and regular users lack permissions to alter settings. In some environments, timeout settings may also involve the reverse proxy or web server, which falls under system administration.