Which two features, when used together, allow you to ensure each site can only view and manage devices in their site?

Which two features, when used together, allow you to ensure each site can only view and manage devices in their site?

• A. Account Limitations and Custom Property Editor
• B. Account Limitations and Web Console Settings
• C. Custom Property Editor and License Details
• D. Web Console Settings and DirectLink Accounts

Answer: (A)

The main idea is to control who can see and manage devices by combining who can access the system with how devices are labeled. Account Limitations define which accounts can access the system and what scope they have, effectively restricting a user to a subset of devices. Custom Property Editor lets you assign a site identifier (a custom property) to each device. When you pair these, you tag devices by site and grant each site’s users access only to devices that have the matching site property. So a user at a particular site can view and manage only that site’s devices, and not those from other sites. Without the custom property, you’d have no site tag to filter on; without account limitations, the filter wouldn’t be enforced across users.

The main idea is to control who can see and manage devices by combining who can access the system with how devices are labeled. Account Limitations define which accounts can access the system and what scope they have, effectively restricting a user to a subset of devices. Custom Property Editor lets you assign a site identifier (a custom property) to each device. When you pair these, you tag devices by site and grant each site’s users access only to devices that have the matching site property. So a user at a particular site can view and manage only that site’s devices, and not those from other sites. Without the custom property, you’d have no site tag to filter on; without account limitations, the filter wouldn’t be enforced across users.