Skip to content

[FEATURE] - Device groups and Aliases #89

Closed as duplicate
Closed as duplicate

Description

@mattish91

Description
Set tags after devices are added or some way to "group" devices and make them "searchable". Something more like the "Alias" and "Device Group" options available in Remotely.

The solution I'd like
Easy way to group devices together, for example by using a "family" tag after devices have been added, to reduce the amount of deployment keys.

Alternatives I've considered
Create new deployment keys for each group/set of devices? Seams unpractical and even harder to manage.

Any security aspects of having it like it's setup right now?

Maybe even a env to make them "editable" would be a valuable thing in this case.

Activity

  1. changed the title [-][FEATURE] - Title Here[/-] [+][FEATURE] - Device groups and Aliases[/+] on Feb 2, 2026
  2. bitbound commented on Feb 3, 2026

    @bitbound
    Owner

    Related to #76 and #86 . Tags will be reworked as part of the upcoming permissions story.

    However, a couple notes: You can already modify tags after deployment, and installer keys aren't tied to any specific tags. An installer key can be reused and apply different tags.

    The UI for adjusting tags is under Permissions. You can modify relationships between tags, users, and devices, as well as adjust user roles.

    These will all be separated, and the UI revamped, during the permissions rework.

    Image
  3. mattish91 commented on Feb 3, 2026

    @mattish91
    Author

    Awesome, did not know that, that works great! Any way to show devices with no tags?

  4. bitbound commented on Feb 4, 2026

    @bitbound
    Owner

    @mattish91 Yup! The Devices tab in that screenshot will give you a device-centric view, which will allow you set tags on devices that don't currently have any.

    So far, the plan for the permissions rework is to decouple tags from authorization. Tags will only be used for identification/searching/filtering purposes, and devices groups will be used for authorization/permissions. Unless there's a strong feedback to keep them together, but just improve the UI/UX/functionality.

  5. mattish91 commented on Feb 4, 2026

    @mattish91
    Author

    Ill close this issue as a duplicate of #76 then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions