Security Changes from Version 2

adTempus 3 introduces security inheritance to the security model. Users upgrading from previous versions of adTempus may have permissions individually assigned to jobs and other objects due to the limitations of the earlier security model. For ease of administration, users will in most cases want to remove object-level permissions in favor of inherited permissions. For example, if all your jobs have the same security settings, earlier versions of adTempus required you to make those settings on each job. With security inheritance, you can make those settings at the root job level and have all jobs inherit them.

Therefore you may need to remove the existing explicit permissions from the individual objects, so that they can inherit all of their security settings. Rather than edit each object individually, you can modify a higher level of the security hierarchy and tell adTempus to remove the non-inherited permissions on each lower level.

For example, if you want all jobs to have the same security settings, edit the settings for the root group (the "Jobs" node in the server tree). After setting the permissions you want your jobs to inherit, check the "Remove explicit permissions on all child objects" box. This will remove all permissions that have been set on individual groups and jobs, forcing them to use only the settings you have defined at the root level. If you now need to tailor the security of certain group and jobs, you can then edit them to override the inherited security.