Designated administration uses the Institution > Organization > Department hierarchy to allow or restrict administrative access to objects based on their association with a level in the hierarchy. Meaning that an Admin who is given rights to only Departments X and Y can perform administrative tasks, like enabling or disabling features, or create/edit/delete courses, but only for items that exist WITHIN those Departments. A further discussion on the capabilities of Designated Administrators can be found in User Roles, Capabilities, and Limitations.

Designated Administration is OFF by default. When first toggled on, all admins currently in the system are automatically granted institution-level administrative access. To restrict admin access for these users, you must disable their institution-level access first, which removes all lower-level access. Then you can explicitly enable access to the appropriate organizations and/or departments. See Assigning Administrator Access to Organizations or Departments for detailed instructions.

Because captures are published (or not published) to sections, which exist in courses that themselves may reside within an Org or Dept (within the hierarchy), designated administration provides additional toggles that determine which captures an admin can view:

• only those published to sections in their hierarchy
• all published captures
• all unpublished captures

Future Admin users must be given explicit administrative privileges to the hierarchy. While existing Admins are given institution-level access when Designated Administration is FIRST turned on, all NEW admin users have NO administrative access given for any level. You must explicitly provide administrative privileges at the appropriate hierarchical nodes/levels. If you do not, those users will not be able to see courses, sections, or captures.

Once enabled, if you disable the toggle, all Org or Dept administrators retain their lower-level access. If your intent is to return all administrators to institution-level admins, check the box for all admins at the Institution level, then turn Designated Administration off.

To enable Designated Administration

1. Log in as an administrator.
2. Click the Settings icon in the upper-right corner of the screen.
3. From the Settings menu, select Institution Settings.

   General settings appears and Basic Info is selected by default.

4. On the left side of the Institution Settings page, select Roles and Permissions.
5. Click Administrator. 
6. Enable the Designated administration switch (it is disabled by default).
7. READ the confirmation message that appears, so you understand the impacts of the change.
8. If appropriate, click Yes.
9. The sub-toggles for allowing access to captures outside of the hierarchy are enabled. Enable or Disable the sub-toggles as needed. These are described in detail below.

   Designated Administration is now turned on for existing Admins.

See Assigning Administrator Access to Organizations or Departments for details. See User Roles, Capabilities, and Limitations for a discussion of the capabilities of institution-level admins vs. designated (lower-level) admins.

Configuring access to published or unpublished captures

Because captures are published (or not published) to sections, which exist within the hierarchy, designated administration has sub-settings that determine which captures an admin can view: only those published to sections in their hierarchy, all published captures, and/or unpublished captures.

These sub-toggles function as follows:

• If both Create/Access Published Content Across Organizations and Create/Access Unpublished Content Across Organizations are turned OFF, designated admins can only see captures that are published to the sections that reside within their hierarchy. This is the default setting.
• If Create/Access Published Content Across Organizations is turned ON, designated admins can see all published captures, including those published to sections outside of their administrative access hierarchy.
• If Create/Access Unpublished Content Across Organizations is turned ON, but Create/Access Published Content Across Organizations is turned OFF, designated admins can see captures published to the sections in their hierarchy and any captures that have not yet been published. If a capture is published to a section outside of their administrative access hierarchy, they cannot see it.
• If both Create/Access Published Content Across Organizations and Create/Access Unpublished Content Across Organizations are turned ON, designated administrators can see (and control) all captures in the system. They are still, however, limited to publishing those captures only to sections within their hierarchy.
• If Scheduling Captures: Require Organization / Department is ON, designated admins will have access to unpublished content specific to their administrative access hierarchy because it requires newly scheduled captures to always have a hierarchy association, regardless of publishing.