Credentials Profiles

Expected Behavior

I would like to be able to configure some connection profiles for various domains, various devices, etc.. then i'd like to organize all of my connections by location rather than by credentials.

Current Behavior

Currently, I can only organize devices into groupings of domains and groupings of routers/switches, etc that have specific credentials behavior.

Possible Solution

A possible solution would be to have central credentials profiles and/or even variables that can be assigned to different fields so that they can be updated centrally in batch without having to configure the groupings that allow credentials cascading.

Steps to Reproduce (for bugs)

Context

Trying to group servers by function like 'Domain Controllers' or 'file servers' rather than by domain. Often i'm working on things that I need to work on all servers on all domains of a specific type.

Your Environment

• Version used:
• Operating System and version (e.g. Windows 10 1709 x64):

The issue names no files, tests, or entry points. Start by locating the existing domain/device grouping and credential-cascading behavior, then clarify the profile model, assignment rules, and how connections should be organized before defining completion criteria.