Platform Version 4.6.0

[George_Santiago]

@alvarolb

• Each project can now define a set of Project Roles that can be used by any member within a project.
  
  .
• Each developer/admin account can now define a set of Global Roles that can be used by any member within any project. For example, a general purpose read role that can be shared in all projects.
  
• Project member permissions can be now established by roles in addition to custom member permissions, simplifying permissions management. All global roles, project roles, and custom permissions can be established together (if required).

Great! Important functionality. It got much better!

@alvarolb

Each developer/admin account can now define a set of Global Roles that can be used by any member within any project. For example, a general purpose read role that can be shared in all projects.

Will “Developer” users be able to create/enable “Project Member”? If yes, great!
I still think administering the Thinger Server with a “Domain Admin” account to create devices, users, projects… something risky, as we don’t have Two-Factor Authentication (2FA).
I could be wrong, but it would feel safer to operate the Server in production with the “Developer” account that doesn’t allow changing HOST and domain settings.
But like I said, I could be wrong… except for the need to implement a Two-Factor Authentication (2FA).

@alvarolb

• Device resource streams includes now different signals: start, stop, data, and error (on IOTMP devices), in order to keep track of streams.

Could you give more details about this functionality?
I remember that it would be important to change the device statuses to indicate, for example, when the device is disabled. With this, the Administrator could differentiate the status “Disconnected” from “Enabled/Dsabled”. I even mentioned it in this post:

@George_Santiago

I would suggest, if possible:

• It would be interesting for the console of the devices to inform which ones are with “Disabled” status and used a different color, eg gray. Or standardize the columns on the bucket list and endpoints screens, changing the column name from “Enabled” to “State”, and insert a new color to represent “Disabled”. Ex: Connected (green); Disconnected (red); Enabled (Blue); Disabled (Gray).

See the example below:
Wouldn’t it be correct to inform it as Disabled? Can’t users be confused when trying to connect a disabled device because the state says Disconnected?

@alvarolb

Very high loads over websockets could cause a crash under some circumstances.

Is it related to the device’s playload (Arduino-Thinger)?

@alvarolb

• Access Tokens now are limited to the project scope where they are defined.

It was a doubt I had (if I understand this point correctly). It was unclear whether establishing broad permissions for a “Project Member” would cause a security breach. Ex: Allow a “Project Member” to create and delete devices.
Sorry if I misunderstood this point.

@alvarolb

Payload not being sent on IOTMP devices.

Could you give more details on this issue?