We hope you've been enjoying all the recent Bank Holidays! 🌞 We've been onboarding the first Alloy Apps users and listening to their initial feedback. Lots of positive vibes but there are always ways to improve things, so we're keen to hear your thoughts!

Work is continuing on the Permissions app, with this month's focus being on new features that make user management much simpler and easier to perform. The update took place during the evening of the 29th of May. For a full list of changes, see v2.72 in the Alloy Changelog.

Please note: we are delaying the update of Alloy Mobile by one week. This is just a precautionary measure to make sure it's compatible with a recent foundational change to Alloy's engine.

Manage users in the Permissions app 👤

We've added a new User Management area to the Permissions app! If you're an admin, this provides a view of all the users in your customer project, where you can see all their properties at once. You can filter and sort the columns as needed, making it easy to isolate and group users by email address or membership.

Select a user's  >  button to show their details in a side panel. This provides a way to easily manage their membership of teams, groups and roles. You can also disable or delete the user as needed.

Need to manage users in bulk? Just select one or more users in the left list and then use the bottom toolbar to add or remove them from teams, groups or roles.

Finally, we've added a new Create User wizard to streamline the process of adding new people to your customer project.

New DesignProperty AQS node 🗄️

A new node type has been added to Alloy Query Syntax. This doesn't happen often! Currently, it can only be used via the API, or when editing code in the Advanced Query Editor of the AQS Builder.

The new DesignProperty node lets you filter queried items based on properties of their design. For now, the node has one property: Implements. It can be used in conjunction with a Guc node to filter items based on whether their design does - or doesn't – implement one or more specific interfaces.

    {
  "type": "Equals",
  "children": [
    {
      "type": "DesignProperty",
      "properties": {
        "designPropertyName": "Implements"
       }
    },
    {
      "type": "Guc",
      "properties": {
        "value": ["designInterfaces_MyExampleInterface_67f67"]
      }
    }
  ]
    }

Seasoned API users may be aware of the Design endpoint, which can return a list of designs that implement a single interface (see ReDoc). The new DesignProperty node makes this functionality more available by bringing it to all scenarios that involve AQS. It also improves upon it by letting you negate it and specify multiple interfaces when needed.