{"id":2530,"date":"2022-06-15T05:38:00","date_gmt":"2022-06-15T05:38:00","guid":{"rendered":"https:\/\/www.adminbyrequest.com\/?p=2530"},"modified":"2026-01-25T07:51:50","modified_gmt":"2026-01-25T07:51:50","slug":"new-feature-spotlight-device-owner","status":"publish","type":"post","link":"https:\/\/www.adminbyrequest.com\/en\/blogs\/new-feature-spotlight-device-owner","title":{"rendered":"New Feature Spotlight: Device Owner"},"content":{"rendered":"\n

Introduction<\/h2>\n\n\n\n

At Admin By Request, we believe the best security solutions come well-equipped, but put the power in your hands \u2013 i.e., they have all of the necessary features, but you have the control to use them as you see fit.<\/p>\n\n\n\n

That is essentially how we help our customers balance their security and productivity needs: by providing a range of options and methods both for granting – or restricting – administrative access.<\/p>\n\n\n\n

In larger organizations with thousands of computers, often used by multiple people, you may want to want to restrict the ability for users to gain privileged access to only the predominant user <\/em>of that device \u2013 particularly if your Settings and Sub-Settings for gaining admin rights are on the more lenient side (e.g., you don\u2019t require approval for elevation).<\/p>\n\n\n\n

That\u2019s why, with the release of Admin By Request version 7.4 for Windows, we\u2019ve equipped our solution with another feature that puts the level of restriction in your hands: Device Owner<\/strong>.<\/p>\n\n\n\n

As the name suggest, the feature sets a user as the device owner, and can then be used (if desired) to lock down the device to only that person.<\/p>\n\n\n\n

Feature Overview<\/h2>\n\n\n\n

The first non-administrator that logs in to the device (prior to Device Owner being set) becomes the Device Owner.<\/p>\n\n\n\n

Once a device has an Owner (listed in the Inventory and Reports pages of your User Portal), you then have the ability to configure Settings to allow only the specified Device Owner to use Admin By Request elevation features on that device (i.e., Run as Admin and Admin Session). These settings can be applied to all users across the board (Global Settings), or to certain users and groups (Sub-Settings).<\/p>\n\n\n\n

The Device Owner can be viewed, changed to the currently logged in user, and released altogether so that the next non-administrator that logs in takes up ownership.<\/p>\n\n\n\n

Using the Feature<\/h2>\n\n\n\n

Assigning and Viewing the Device Owner<\/h3>\n\n\n\n

Upon installation of Admin By Request on the endpoint, the first non-administrator who logs in becomes the Device Owner. However, there is a 24-hour period after installation during which the Device Owner will change to reflect each non-administrator who logs in, rather than staying fixed on the first one. The reason for this ‘open’ period is to avoid an incorrect user being set as the Device Owner (such as an IT Admin assisting with setup post-installation).<\/p>\n\n\n\n

After the 24-hour window, the Device Owner is set – unless no non-administrators logged in during the 24-hour window. In this case, the first non-admin who logs in after the 24-hour window is set as the Device Owner.<\/p>\n\n\n\n

Device Owners can be viewed from two locations within your User Portal:<\/p>\n\n\n\n

From the Inventory Page<\/strong><\/p>\n\n\n\n

1. Navigate to the Inventory <\/em>page and select the appropriate device from the list:<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

2. Select the Owner <\/em>item from the left-hand menu (note that if the Device Owner is not the same user currently logged in to the device, you will be able to view both the Logged-On User<\/em> and the Device Owner<\/em> on this page – see screenshot in the Changing the Device Owner<\/em> section, point 2):<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

From the Reports Page<\/strong><\/p>\n\n\n\n

1. Navigate to the Reports <\/em>menu and select User Reports > Device Owners<\/em> from the list:<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

2. Here all Device Owners are listed next to their devices (note the screenshot below is displaying the Owners <\/em>tab):<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

3. Clicking into the Non-Matching Users<\/em> tab displays all of the users who have logged in to the device who are not the Device Owner (note the user details are blurred in the screenshot below):<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Changing the Device Owner<\/h3>\n\n\n\n

Sometimes the Device Owner may not be set to the correct user, or you may need to change the Device Owner due to employee turnover, etc. There are two available methods for doing this:<\/p>\n\n\n\n

1. Get the intended Device Owner (i.e., the user that you want to be the Device Owner) to log in to the device.<\/p>\n\n\n\n

2. In your User Portal, navigate to Inventory > [Device] > Owner<\/em>. From here, select the Make Owner<\/em> button to set the Device Owner to the user that is currently logged on \u2013 replacing the existing Device Owner listed in the bottom section:<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

3. The other method for changing the Device Owner is to clear the property altogether by clicking the Release Ownership<\/em> button in the Unlock Owner<\/em> section. Choosing this option resets the feature so that the next non-administrative user that logs on to the device becomes the Owner. However, if the next non-administrator to log in is the same Device Owner who was just released, they will not be set as the Device Owner. Instead, you need to use the Make Owner<\/em> button (see previous step) to reset this user as the Device Owner (this method can also be used if you select Release Ownership<\/em> by mistake):<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Locking Down the Endpoint to Device Owner<\/h3>\n\n\n\n

The lockdown component of this feature can be used to ensure only the Device Owner can request administrative access on their device, and there are several options available for doing this.<\/p>\n\n\n\n

Global Settings<\/strong><\/p>\n\n\n\n

The first method is to lock down all devices across the board to their owner using Global Settings:<\/p>\n\n\n\n

1. Navigate to Settings<\/em> > Windows Settings<\/em>:<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

2. From the left-hand menu, select Lockdown<\/em>, and on the Lockdown page, select Owner<\/em> from the top tab menu:<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

3. In the Device Owner<\/em> section, set the Lock Device to Owner <\/em>toggle to \u2018ON\u2019, and click the Save<\/em> button (note that a green tick will appear next to the Save button when the action is complete):<\/p>\n\n\n\n

\"\"\/<\/figure>\n\n\n\n

Sub-Settings<\/strong><\/p>\n\n\n\n

Sub-Settings override Global Settings, essentially acting as \u2018exceptions to the rule\u2019. They allow you to apply the lockdown setting to specific users and groups based on who needs what access, rather than to all users (as is the case when using Global Settings).<\/p>\n\n\n\n

Let\u2019s look at a few use cases:<\/p>\n\n\n\n

1. To protect business-critical data and processes, you want to lock down your Management team\u2019s devices so that only they can access them, but all other devices need not be restricted (i.e., can be accessed by any user, regardless of Device Ownership).<\/strong><\/p>\n\n\n\n

    \n
  • To configure this setup, set the Lock Device to Owner<\/em> toggle to \u2018OFF\u2019 in the Global Settings.<\/li>\n\n\n\n
  • In your Sub-Settings, locate the rule you are adjusting \u2013 in this case, the Management<\/em> Sub-Setting rule:<\/li>\n<\/ul>\n\n\n\n
    \"\"\/<\/figure>\n\n\n\n
      \n
    • Navigate to Lockdown<\/em>, go to the Owner<\/em> tab, and toggle the Lock Device to Owner<\/em> toggle to \u2018ON\u2019.<\/li>\n\n\n\n
    • All devices in the Management group (defined in the Sub-Setting Scope<\/em> – see image below) can now only be accessed by their specified Device Owner.<\/li>\n<\/ul>\n\n\n\n
      \"\"\/<\/figure>\n\n\n\n

      2. You want all users to only have access to their own devices, apart from the IT Support team, whom you want to have access to all users’ devices in order to provide IT support when necessary.<\/strong><\/p>\n\n\n\n

      In this case, you would do the opposite to the above:<\/p>\n\n\n\n

        \n
      • In Global Settings, set the Lock Device Owner toggle to \u2018ON\u2019.<\/li>\n\n\n\n
      • In your Sub-Settings, in the IT Support<\/em> Sub-Setting rule, navigate to Lockdown > Owner<\/em> tab and set the Overrule Global Settings<\/em> toggle to \u2018ON\u2019. Then set the Lock Device to Owner<\/em> toggle to \u2018OFF\u2019:<\/li>\n<\/ul>\n\n\n\n
        \"\"\/<\/figure>\n\n\n\n
          \n
        • Users in the IT Support group Scope now have access to all devices, whereas all other users (outside of the Scope) still only have access to their own device (due to the Global Setting).<\/li>\n<\/ul>\n\n\n\n

          Note that Sub-Settings apply in the order they are specified.<\/p>\n\n\n\n

          Summary<\/h2>\n\n\n\n

          Multiple users being able to gain privileged access across your company devices poses a security risk. Device Owner<\/strong>, our latest flexible feature, helps mitigate this risk in a way that accommodates the uniqueness of every organization.<\/p>\n\n\n\n

          Download Admin By Request version 7.4 for Windows today and customize your Privileged Access Management (PAM) experience even more.<\/p>\n","protected":false},"excerpt":{"rendered":"

          Lots of devices with a multitude of users causing security concerns? You can now set a Device Owner for each device, and lockdown the endpoint to that specific user with our latest Windows feature.<\/p>\n","protected":false},"author":2,"featured_media":7829,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[36],"tags":[21,118,96,58,106,119,117,18],"ppma_author":[9],"class_list":["post-2530","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blogs","tag-admin-rights","tag-device-owner","tag-elevation","tag-endpoint","tag-features","tag-lockdown","tag-new-feature","tag-privileges","entry","has-media"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t