Various configuation setting tabs will be available if current user is allowed to view configuration settings:
!Working with Configurations^configuration-settings.png!
Most of the configuration settings are inheritable with nearest non-empty setting in the hierarchy taking effect. Taking configuration schedule for example, assume below configuration hierarchy:
{code}
root
project1
qa
{code}
If configuration _root/project1_ and _root/project1/qa_ do not define their own schedules, while configuration _root_ defines a schedule which triggers every 5 minutes, the configuration _root/project1/qa_ will inherit schedule defined in configuration _root_ and consequently be triggered every 5 minutes. If a schedule is defined in _root/project1_, that schedule will be used for _root/project1/qa_ instead.
{info}Configuration settings can only be edited by administrators.{info}
!Working with Configurations^configuration-settings.png!
Most of the configuration settings are inheritable with nearest non-empty setting in the hierarchy taking effect. Taking configuration schedule for example, assume below configuration hierarchy:
{code}
root
project1
qa
{code}
If configuration _root/project1_ and _root/project1/qa_ do not define their own schedules, while configuration _root_ defines a schedule which triggers every 5 minutes, the configuration _root/project1/qa_ will inherit schedule defined in configuration _root_ and consequently be triggered every 5 minutes. If a schedule is defined in _root/project1_, that schedule will be used for _root/project1/qa_ instead.
{info}Configuration settings can only be edited by administrators.{info}