OPSWAT has released several exciting new features for the Gears platform. The first is the ability to manage a single account with multiple users. The new multi-user management introduces the following new roles:
- Owner
- Administrator
- Read-Only
Each of these roles can now be managed via the new Account Settings dashboard. This dashboard shows Account Information, Account Security, and Account Management. New users are invited and managed via the Account Management dashboard.
The Owner role will have full access to all of the account resources as well as the ability to fully manage all aspects of the account. The Owner has the ability to invite additional users to the account. These users can be either existing or non-existing Gears account holders, and can be named as an administrator or read-only user.
Administrator will have full access to the account, and will have permissions to modify all aspects of the account; however any changes will be logged in the Event log. The Read-Only user will have limited access to the account. The permissions will include only the ability to view the information available in the account; the user will not be able to make any modifications to the configurations.
These alternate roles allow the account holder to browse between different accounts, switch between accounts, and see changes made in the Event Log.
The additional features revolve around our newly launched API’s. These new API’s will serve as a springboard for OPSWAT to provide broader access to the Gears functionality and allowing easier integration into tools and platforms. The API’s included in this release focus on gathering account and device details on those endpoint devices under management.
The methods included in this release are:
- Account
- Configuration
- Devices
- Device Detail
- Logs
Developers that are integrating the Gears platform via the Gears API should be familiar with the OAuth 2.0 specification and its general requirements. Prior to implementing the API’s, each application will need to be registered and validated. Once confirmed a Consumer Key and Consumer Secret string will be provided, these will be bound to the registered application.
Full documentation and details on these new APIs can be found at the newly launched Developer Portal. Continue to check back as we will be expanding the APIs and supporting documentation quickly over the next few months.
OPSWAT has released several exciting new features for the Gears platform. The first is the ability to manage a single account with multiple users. The new multi-user management introduces the following new roles:
- Owner
- Administrator
- Read-Only
Each of these roles can now be managed via the new Account Settings dashboard. This dashboard shows Account Information, Account Security, and Account Management. New users are invited and managed via the Account Management dashboard.
The Owner role will have full access to all of the account resources as well as the ability to fully manage all aspects of the account. The Owner has the ability to invite additional users to the account. These users can be either existing or non-existing Gears account holders, and can be named as an administrator or read-only user.
Administrator will have full access to the account, and will have permissions to modify all aspects of the account; however any changes will be logged in the Event log. The Read-Only user will have limited access to the account. The permissions will include only the ability to view the information available in the account; the user will not be able to make any modifications to the configurations.
These alternate roles allow the account holder to browse between different accounts, switch between accounts, and see changes made in the Event Log.
The additional features revolve around our newly launched API’s. These new API’s will serve as a springboard for OPSWAT to provide broader access to the Gears functionality and allowing easier integration into tools and platforms. The API’s included in this release focus on gathering account and device details on those endpoint devices under management.
The methods included in this release are:
- Account
- Configuration
- Devices
- Device Detail
- Logs
Developers that are integrating the Gears platform via the Gears API should be familiar with the OAuth 2.0 specification and its general requirements. Prior to implementing the API’s, each application will need to be registered and validated. Once confirmed a Consumer Key and Consumer Secret string will be provided, these will be bound to the registered application.
Full documentation and details on these new APIs can be found at the newly launched Developer Portal. Continue to check back as we will be expanding the APIs and supporting documentation quickly over the next few months.
