Configure Organization Defaults

Most host configuration is best done in Host Groups, but there are several settings you should review at the organization level.

When performing data entry in Foreman, if you don’t limit what is displayed, the default is to show you everything available. For things like domain names and subnets, this is a long list, and most of the entires are not appropriate for a particular organization.

You can manage your organization defaults from the Administer -> Organizations> menu.


Here you can control what user ID’s can see entities in your organization. Alas! Foreman does not support the use of User groups, external or otherwise, which makes it difficult to do authorization via Wolftech.


Most groups have only a few (subnets)[/subnets-in-foreman.html] in which they build linux hosts). Taking the time to pick only the ones you need once at the organization level may save you frustration in having to look at every subnet on campus every time you build a new host.

At your Organization level Administer -> Organizations> you can select from all the sunbets in the system the ones applicable to you, or check the “all subnets” box to get all current and future subnets.

Usually, admins choose to only associate subnets they actually use with their organizations, so that when they create an individual host they don’t have to scroll past a large list of inappropriate subnets in the new host interface.

It is also possible to further filter the subnets available to a hostgroup Configure -> Host Groups . This allows you to enforce business logic like “all our publicly accessible web sites should be in this VLAN/Subnet/Firewall context” or ease data entry by reducing the number of subnetworks displayed in the new host dialogs.


Like subnets, there are many DNS domains in use at NCSU, only some of which are likely to be of interest to any one group.

Tags: foreman
Edit me